Supported Integrations
Native Confluence Integration
Content Formatting Macros is built as a native Confluence Cloud app and integrates deeply with Confluence's built-in data model. It does not require any external service connections, API keys, or third-party accounts.
Confluence Features Used by Each Macro
Page Hierarchy (Child Pages)
Used by: Tab Parent Content Mapper
The Tab Parent Content Mapper reads the Confluence page hierarchy to populate tabs from child pages. It uses the Confluence Content API to:
- Retrieve all child pages of a specified parent page
- Read each child page's title (used as the tab label)
- Fetch and render each child page's body content inside the tab
- Respect the page tree sort order configured in Confluence
Confluence permission model: If a viewer does not have read permission on a child page, that tab is not rendered for them. The mapper respects all standard Confluence page restrictions.
Labels
Used by: Tab Label Content Mapper
The Tab Label Content Mapper looks up all pages tagged with the label name you entered in the macro configuration. Each matching page becomes its own tab - the tab title is the page title and the tab content is the page body. It integrates with:
- Confluence's label system (labels applied to pages via the page footer or editor)
- Space-scoped filtering (restricts results to a specific space or all accessible spaces)
Confluence permission model: Only pages the current viewer has read permission to access are returned - pages they cannot see are silently excluded from the tab list.
Spaces
Used by: Tab Label Content Mapper, Tab Page Mapper, Attachment Management Center
Macros can be scoped to specific Confluence spaces. The Attachment Management Center operates on a per-space basis and requires Space Admin access to enable.
Users & Groups (Conditional Visibility)
Used by: Conditional Show, Conditional Hide
The conditional visibility macros integrate with Confluence's user and group system:
| Data Used | Source | How Used |
|---|---|---|
| Confluence user identity | Confluence session | Match against individually selected users |
| Confluence group membership | Confluence Groups API | Match against selected groups |
What the app does NOT do:
- The app does not sync, create, or modify Confluence groups
- The app does not access Atlassian Access, external identity providers, or SSO directory data
- Group membership is read at render time from Confluence's built-in groups - no caching between page loads
Confluence permission model: Group names in the macro configuration must exactly match existing Confluence groups. The app reads group membership via Confluence's standard permissions model.
User Profiles
Used by: User Profile Macro
The User Profile macro reads Confluence user profile data:
| Field | Source |
|---|---|
| Display name | Confluence user profile |
| Avatar / profile photo | Confluence user profile |
| Job title | Confluence user profile (optional field) |
| Department | Confluence user profile (optional field) |
| Location | Confluence user profile (optional field) |
| Email address | Confluence user profile (shown only if configured to display) |
Profile fields are populated by each user in their own Confluence profile settings. Fields not filled in by the user will be blank in the macro display. The app does not pull data from external HR systems or directories.
Attachments
Used by: Attachment Management Center
The Attachment Management Center integrates with Confluence's attachment storage system:
| Capability | Confluence API Used |
|---|---|
| List all attachments in a space | Confluence Content API (attachments endpoint) |
| Filter by file type, date, uploader | Client-side filtering of API results |
| Apply labels to attachments | Confluence Labels API |
| Delete attachments | Confluence Attachments API (delete) |
| Detect orphaned files | Compare attachment list against page content references |
Permissions required: Space Admin role to enable the Attachment Center per-space; standard Confluence attachment permissions apply to all read and delete operations.
Confluence Permission Model Integration
Content Formatting Macros fully respects Confluence's permission model at every layer:
| Permission Layer | How the App Honors It |
|---|---|
| Page restrictions | Tab mapper macros only show tabs for pages the viewer can read |
| Space permissions | Attachment Center requires Space Admin role; conditional macros read space roles from Confluence |
| Site administration | App installation requires Confluence site admin role |
| Group membership | Conditional Show/Hide reads group membership from Confluence at render time |
| Anonymous access | Conditional visibility evaluates login status correctly for anonymous (not-logged-in) viewers |
What Content Formatting Macros Does NOT Integrate With
| System | Status |
|---|---|
| Jira (issues, boards, sprints) | No direct integration - use Confluence's built-in Jira macros for Jira data |
| External databases | No |
| External identity providers (Okta, Azure AD) | No - reads Confluence group membership only |
| Confluence Data Center | Not supported |
| Confluence Server | Not supported |
| Third-party storage (S3, GDrive) | No |