Common Use Cases

Five practical scenarios showing how teams use Reports, Charts, Templates,CQL & Export for Confluence to solve real reporting challenges.

---

1. Content Audit - Track Stale Pages

Audience: Space Admins, Documentation Leads, Governance Teams

Purpose: Identify pages that have not been updated recently so they can be reviewed, refreshed, or archived. Keeps your Confluence knowledge base accurate and trustworthy.

Recommended View: Table

CQL Example:

type = page AND lastmodified <= now("-60d") AND space = "DOCS" ORDER BY lastmodified ASC

Suggested Columns:

• Page Title (Link block → title / _links.webui)
• Space (Basic block → space.name)
• Last Modified (Basic block → version.when)
• Last Modifier (Basic block → version.by.displayName)
• Created (Basic block → history.createdDate)

How to Use: 1.Apply the CQL above (adjust space key and date window as needed). ORDER BY lastmodified ASC lists the oldest pages first. 2.Load version and history expansions. 3.Add columns as listed above. 4.Export as CSV to share with the team for review and cleanup assignments.

---

2. Team Directory - Grid View with User Profiles

Audience: HR, Team Leads, All Employees

Purpose: Create a visual team directory that shows profile photos, names, roles, and links to each person's profile page - all from Confluence page metadata.

Recommended View: Grid

CQL Example:

type = page AND label = "team-profile" AND space = "TEAM"

Suggested Columns:

• Profile Photo (Image block → history.createdBy.profilePicture.path)
• Name (Link block → title / _links.webui)
• Role (Basic block → metadata.labels.results[0].name)
• Space (Basic block → space.name)

How to Use: 1.Ask each team member to create their own profile page and tag it with the label team-profile. 2.Apply the CQL above (adjust space key as needed). 3.Load history and metadata expansions. 4.Set Report Type to Grid. 5.Add Image block as the first column for visual profile cards. 6.Save and publish on the team's Confluence space homepage.

---

3. Activity Dashboard - Charts of Page Creation and Updates

Audience: Managers, Admins, Team Leads

Purpose: Visualize how documentation activity has changed over time - track content growth, update cadence, and identify spikes or gaps in team activity.

Recommended View: Charts (Line + Bar)

CQL Example (for line chart - content created over time):

type = page AND space = "ENG" AND created >= "2026-01-01"

CQL Example (for bar chart - pages per space):

type = page AND lastmodified >= now("-30d")

Chart Configuration:

How to Use: 1.Set Data Source to Custom CQL - use one of the queries above. 2.Set Report Type to Bar Chart or Pie Chart. 3.Add the Group By field (space.name or type) as the first column. The saved chart groups by this column. 4.Set Aggregation to Count. 5.Review in Live Preview and save. 6.Embed multiple chart macros on a dashboard page for a full activity overview.

---

4. Governance & Compliance Report - Ownership Tracking

Audience: Compliance Officers, Space Admins, Legal Teams

Purpose: Identify who owns each page - original creator vs. last modifier - and flag pages that lack clear ownership or have not been reviewed recently.

Recommended View: Table

CQL Example:

type = page AND space = "LEGAL" AND status = "current"

Suggested Columns:

• Page Title (Link block → title / _links.webui)
• Original Creator (Basic block → history.createdBy.displayName)
• Last Modifier (Basic block → version.by.displayName)
• Last Modified Date (Basic block → version.when)
• Created Date (Basic block → history.createdDate)
• Space (Basic block → space.name)

How to Use:

1. Apply the CQL above (adjust space key as needed).
2. Load history and version expansions.
3. Add columns as listed above.
4. Apply a filter: Last Modified Date <= (a date 90 days ago) to flag stale pages.
5. Export as CSV for compliance review and ownership assignment.

Tip: Use the "Owner vs Last Editor" pre-built template in the Templates tab - it configures this report in one click.

---

5. Executive Summary - Paragraph View Digest

Audience: Executives, Senior Leadership, Non-Technical Stakeholders

Purpose: Generate a readable, narrative-style weekly digest of recent documentation activity - showing what changed, who changed it, and when - in plain English rather than a data table.

Recommended View: Paragraph

CQL Example:

type = page AND lastmodified >= now("-7d") ORDER BY lastmodified DESC

Column Configuration (Paragraph view - sentences):

How to Use:

1. Apply the CQL above.
2. Load version expansion.
3. Set Report Type to Paragraph.
4. Add columns as shown in the table above - use Text block with Prefix/Suffix for natural language.
5. Set Result Limit to 25–50 for a focused digest.
6. Save on a weekly digest or leadership update page.