Set an image as a page cover
Writes the Confluence cover-picture properties for both the published and draft page at position 50. Refused unless the caller has update permission on the page.
#Where you do it
Task | Where |
|---|---|
Open the image library | Confluence space or global apps menu → 'Capable Images' (standalone) or 'Capable' (Suite) |
Create a folder | Images library → Space images or Global images → new folder control |
Rename or delete a folder | Folder context menu in the library navigation |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Global settings → Capabilities | Confluence admin → Apps → Capable → Settings → Capabilities | - |
Global settings → Asset access (Permissi | Capable settings → Asset access | - |
Global settings → Egress | Capable settings → Egress | - |
#Worth knowing
Deleting a folder does not delete or relocate the images inside it. One delete is issued for the folder record and nothing else. No cascade, no orphan sweep, no warning.
Deleting an image gives no warning that pages reference it. The 'Used on Pages' count is only shown on the image detail page, never in the delete path.
There is no images-only permission setting. All Capable global assets share one Confluence custom-content type in one space, so the Asset access tab governs them together, and only by editing CAPABLEASSETSTORE space permissions in Confluence.
Capable cannot change who may edit global images.
An anonymous or unlicensed reader can see a referenced image or a gallery, but never the library macro, the library page contents, or the settings page. The space page and global page grant unlicensed and anonymous access but fall back to a static visitor notice instead of the library; the global settings page grants none and requires being logged in.
The Global images section disappears entirely if the CAPABLEASSETSTORE space is missing or unreadable, and a failed creation is remembered for the rest of the session rather than retried.
#Related
How it actually behaves.
