Common Use Cases
Real-world scenarios where Content Formatting Macros transforms how teams use Confluence.
Use Case 1 - IT Runbook with Tabs
Scenario
An IT operations team maintains runbooks for 20+ services in Confluence. Each runbook has the same sections (Overview, Procedures, Escalation, Reference), but they're all formatted differently because different engineers wrote them. Finding the right section in a long runbook requires too much scrolling.
Solution
Standardize every runbook on a shared template using tab macros:
- Tab 1: Overview - Background macro (light blue), service description, Alert macro (current status), Buttons macro (links to monitoring dashboard, Jira board)
- Tab 2: Procedures - Numbered steps, Background macro (yellow) for critical sections, Alert macros for warnings
- Tab 3: Escalation - User Profile macros for L1/L2/L3 contacts, Conditional Show (admin-only internal notes)
- Tab 4: Reference - Advanced Expand macros for collapsible reference tables, JSON Viewer for API response examples
Macros Used
Create Custom Tabs, Background, Alert, Buttons, User Profile, Conditional Show, Advanced Expand, JSON Viewer, Status Macro
Outcome
- Runbook sections are instantly accessible via tabs - no scrolling through irrelevant content
- All runbooks follow the same structure regardless of who wrote them
- Escalation contacts are always visible in one place
- Admin notes are hidden from non-admin readers viewing the runbook
Use Case 2 - HR Policy Hub with Conditional Visibility
Scenario
An HR team maintains a Policy Hub in Confluence. Some policies are for all employees; others are manager-only (compensation bands, performance improvement process). Currently, managers are emailed the manager-only policies separately, creating version control problems.
Solution
Build a single Policy Hub page using conditional visibility:
- All-employee policies: published normally in tabs (by policy category)
- Manager-only sections: wrapped in Conditional Show macro, condition: group =
hr-managers - Sensitive data tables (salary bands): wrapped in Conditional Show macro, condition: group =
hr-leadership - An Alert (Info type) at the top explains that additional content is visible based on role
Macros Used
Tab Label Content Mapper (policies tagged with labels by category), Conditional Show, Alert
Outcome
- One page, one source of truth - no more emailing separate documents
- Managers see exactly what they need without a separate page
- Leadership-only data is hidden from managers
- Version control is solved - updating one page updates for all audiences simultaneously
- Confluence Page Restrictions still protect the page from non-HR access at the page level
Use Case 3 - Product Release Notes with Status and Progress
Scenario
A product team publishes release notes in Confluence for each sprint. Stakeholders want to see what's in the current release at a glance - what's done, what's in testing, and what's been pushed to the next sprint.
Solution
Create a release notes page template with status indicators:
- Interactive Banner at the top: "Sprint 47 Release Notes - Shipping November 15"
- Countdown Timer in the banner subtitle: "Shipping in X days"
- A Status Macro per feature row in a table (Done, In Testing, Pushed)
- Progress Bar showing overall sprint completion percentage
- Create Custom Tabs with tabs: This Sprint | Next Sprint | Shipped | Known Issues
- Alert (Warning) for any known blocking issues
Macros Used
Interactive Banner, Countdown Timer, Status Macro, Progress Bar, Create Custom Tabs, Alert
Outcome
- Stakeholders get a visual, at-a-glance view of release status
- The countdown builds anticipation and sets clear timeline expectations
- Status badges replace written "Done/In Progress" text with scannable visual cues
- The Known Issues tab is easy to find - no hunting through long pages
Use Case 4 - Team Wiki with Dynamic Tabs
Scenario
An engineering team has a Confluence space with dozens of sub-pages: team processes, architecture docs, runbooks, meeting notes. The team home page has manual links to these pages, but the list goes stale - people add pages but forget to update the home page links.
Solution
Replace the manual link list with Tab Parent Content Mapper tabs:
- Organize child pages into logical parent pages (e.g., "Processes", "Architecture", "Runbooks")
- On the team home page, use Tab Parent Content Mapper for each major section
- Each mapper pulls tabs from the relevant parent's child pages
- Add a manual "Quick Links" section using Buttons macros for the most-visited pages
- Use User Profile macros in a sidebar card for the team's on-call and team lead contacts
Macros Used
Tab Parent Content Mapper, Buttons, User Profile, Advanced Cards (for featured resources)
Outcome
- The home page never goes stale - tabs auto-update when pages are added or renamed
- New team members can explore all team content from one organized hub
- On-call and team lead contacts are always visible and up to date
- Reducing manual home page maintenance saves time and eliminates broken links
Use Case 5 - Event Countdown Announcement
Scenario
A company's internal comms team wants to build excitement for an upcoming all-hands event. They want a Confluence page that functions as a living announcement - with a countdown, event details, registration link, and agenda - that updates automatically as the event approaches.
Solution
Build a dedicated event page:
- Interactive Banner: Full-width banner with event branding, headline "Annual All-Hands 2025", and a "Register Now" Button
- Countdown Timer (Block style): Prominently placed below the banner, counting down to the event date
- Create Custom Tabs with tabs: Event Details | Agenda | Speakers | FAQ
- Background macros: Color-coded sections within the Agenda tab (morning sessions blue, afternoon sessions green)
- Advanced Cards: Speaker cards with photo, name, title, and session description
- Conditional Show: Admin-only tab with internal logistics notes (visible to event-organizers group only)
Macros Used
Interactive Banner, Buttons, Countdown Timer, Create Custom Tabs, Background, Advanced Cards, Conditional Show
Outcome
- The countdown creates real-time urgency visible every time someone views the page
- All event information is in one place with a clear tabbed structure
- Speaker cards make the agenda visually engaging
- Internal organizer notes are on the same page but invisible to general attendees