Confluence
Overview
Monitor and analyze Confluence collaboration data including spaces, pages, users, and permissions. Gain insights into knowledge management effectiveness, content organization, and access patterns. Track documentation quality, identify knowledge gaps, and ensure proper governance across your organization's collaborative workspace.
Configurations
| Configuration | Description |
|---|---|
| Blueprint Account Name | A human-readable name for your account that will be used to identify this account across the application. |
| Confluence URL | The base URL of your Confluence instance (e.g., https://yourcompany.atlassian.net). |
| Your Atlassian account email address. | |
| Token | A Confluence API token for authentication. You can generate this in your Atlassian account under API tokens. |
| Data Crawl Frequency | The frequency at which Kscope will crawl your Confluence instance for updates and changes. |
Permissions
The Confluence blueprint requires an API Token which you can create by clicking here. Please ensure that you use the "Create API token" option to create a simple token (not the scoped one) and give the API token a descriptive label like "Kscope Crawler".
When creating the API token, note that simple API tokens inherit your user permissions. Ensure your account has read access to the spaces and content you want to monitor.
Required Permissions:
| Permission | Why it's needed |
|---|---|
| Read access to Spaces | Access and read space information, settings, and permissions |
| Read access to Content | Access pages, blogposts, comments, attachments, and their metadata |
| Read access to Users | Read user profiles and group membership information |
Important Notes:
- API tokens inherit the permissions of the user who created them
- The token works with Basic Authentication using your email address and the token
- Ensure your user account has access to all spaces and content you want Kscope to monitor
- API tokens do not expire but can be revoked at any time
- Space permissions and page author visibility require a Jira blueprint to be configured as well, since user information is resolved through the Atlassian account
For more details on Confluence API authentication, refer to: Atlassian API Token Documentation
Schema Model
| Resources | Source Entity | Normalized Entity | Description |
|---|---|---|---|
| Confluence Instance | confluence.ConfluenceData | Confluence | Root entity representing the Confluence instance |
| Space | confluence.space.Space | Space | A Confluence space container |
| Space Icon | confluence.space.SpaceIcon | SpaceIcon | Icon associated with a space |
| Page | confluence.page.Page | Page | A Confluence page or blogpost |
| Page Version | confluence.page.PageVersion | PageVersion | Version history of a page |
| Page Body | confluence.page.PageBody | PageBody | The body content of a page |
| Page Content | confluence.page.PageContent | PageContent | Content in specific format (storage, view) |
| User | confluence.user.User | User | A Confluence user account |
| User Avatar | confluence.user.UserAvatar | UserAvatar | User profile picture |
| Group | confluence.user.Group | Group | A Confluence user group |
| Label | confluence.label.Label | Label | A label/tag attached to content |
| Permission | confluence.permission.Permission | Permission | Content-level permission |
| Space Permission | confluence.permission.SpacePermission | SpacePermission | Space-level permission |
Use Cases
Knowledge Management
- Track active vs. stale documentation
- Identify high-value content based on views and updates
- Monitor documentation coverage across teams and projects
Access Control & Security
- Audit space and page permissions
- Identify overly permissive or restrictive access
- Track external collaborators and their access levels
Collaboration Analytics
- Analyze content creation and update patterns
- Identify key contributors and content owners
- Track label usage for content organization
Compliance & Governance
- Ensure documentation meets compliance requirements
- Track permission changes and access patterns
- Monitor content retention and archival
Filterable Resources
The following resources can be filtered during configuration to focus on specific subsets:
- Spaces: Filter by space key or name
- Pages: Filter by specific pages or page hierarchies
- Users: Filter by user account or group
- Labels: Filter content by specific labels