Restrict who can edit shared Capable templates and images
Shared Capable templates, diagrams, images and other global assets live in the Capable Asset Store space, so its Confluence space permissions decide who can change them. To restrict editing, a site administrator clears Add and Delete under Pages for the people who should only use the library, and leaves View on.
#Before you start
You need | Why |
|---|---|
A Confluence site administrator | The Permissions tab in Global settings only shows to site administrators. |
Groups that should keep editing | Decide who curates the library before you change anything. |
#Steps
Open Global settings for Capable in Confluence administration. You can also select Open Global Settings in the General section of your Capable settings.
Select the Permissions tab, then Manage in Confluence on the Asset access card. It opens the Capable Asset Store space permissions.
Find the groups and people listed under Pages. In Confluence, Add is what allows editing. There is no separate edit permission.
Clear Add and Delete for anyone who should not change shared assets. Leave View so they can still use them on pages.
Do not change the permissions of the Capable app itself.
#Lock down one asset instead
To protect a single template or image rather than the whole library, use Restrictions on that asset: right-click it in the catalogue, or open it and use the Restrictions section in the details panel.
#If it does not work
Indexing, AI generation, page copy or Sites deploys stop working quietly: the Capable app's own permissions on the space were removed. Put them back.
Somebody can no longer use a template at all: check they still have View on the space.
You cannot see the Permissions tab: it only shows to site administrators, and only when an installed capability has shared assets.
#Related
Everyone can use the library. Fewer people can change it.
