Permissions & Access
Who Can Do What
| Role | Can Do |
|---|---|
| Space Admin | Install the app (site admin required) |
| Page Author (edit permission) | Insert, configure, and publish any macro on pages they can edit |
| Page Viewer (read permission) | View rendered macros; conditional visibility is evaluated per viewer's groups |
Installing the App
Only a Confluence site administrator can install apps from the Atlassian Marketplace. Space admins without site admin rights cannot install the app themselves - they must request installation from a site admin.
Inserting Macros
All Confluence users with page edit permission can insert and configure any Content Formatting macro. There is no per-macro permission control - access is governed by standard Confluence page edit permissions.
Conditional Show / Hide
For conditional visibility macros to work correctly:
- The Confluence group names used in the macro config must exactly match existing group names in Confluence Admin → Groups
- Group membership is managed by Confluence administrators in the standard Confluence user management interface
- The app does not create, manage, or sync groups - it reads existing Confluence group membership at render time
Attachment Center
The Attachment Management Center requires:
- Space Admin role to enable the feature per-space (Space Settings → Content Formatting Macros → Attachment Center)
- Space Admin role to perform bulk delete operations
- Standard Confluence attachment permissions apply to all operations
Important: Conditional Visibility Is Not a Security Boundary
Conditional Show and Conditional Hide macros change what is displayed in the browser. They do not restrict access to the underlying page content.
Users with page-read permission can still access all content via the Confluence REST API, page exports, or the Confluence mobile app - regardless of conditional macro settings.
For truly sensitive content, use Confluence Page Restrictions to limit read access at the page level.