Confluence Authority Series — Part 1
From Permissions to Real Knowledge Base Architecture in Atlassian Confluence
This updated guide doesn’t just explain access control —
it teaches how companies actually build structured documentation systems using Confluence.
You’ll learn:
Permission hierarchy
Documentation structure (Spaces → Pages → Child Pages)
Collaboration best practices
Macros teams actually use
Confluence + Jira knowledge base workflow
When Confluence is the right tool (and when it isn’t)
1. The Golden Rule — How Confluence Access Works
Access always flows top → down:
Global Permission → Space Permission → Page Restriction
If blocked at higher level → lower level cannot grant access.
Global Permissions (Entry Gate)
Controls:
Who can login
Who can create spaces
Admin rights
Best Practice: Always assign permissions to groups, never individuals.
Space Permissions (Department Access)
Spaces represent departments/projects:
HR
Engineering
Client Projects
Page Restrictions (Confidential Data)
Used for:
Salaries
Contracts
Architecture diagrams
Page restriction only removes access — never grants it.
2. Designing Proper Documentation Hierarchy
Most companies fail here — not in permissions.
Recommended Structure
SPACE: Engineering
├── 01_Getting_Started
│ ├── Setup Guide
│ ├── Local Run
│ └── Coding Standards
├── 02_Architecture
│ ├── System Overview
│ ├── Database Design
│ └── Integrations
├── 03_Operations
│ ├── Deployment
│ ├── Monitoring
│ └── Incident Runbook
Key Rule
Spaces organize ownership
Pages organize knowledge
Child pages organize workflow
Common Mistake
People create 200 pages at root → search becomes useless.
3. Confluence vs Other Documentation Tools — When to Use What
| Tool | Best For | Not Ideal For |
|---|---|---|
| Confluence | Team collaboration documentation | Public documentation portals |
| Notion | Personal/team notes | Large enterprises governance |
| SharePoint | Corporate file storage | Technical knowledge base |
| GitBook | Public developer docs | Internal workflows |
Conclusion:
Use Confluence when knowledge changes frequently and many teams collaborate.
4. Confluence Macros Every Team Should Use
Essential Macros
| Macro | Purpose |
|---|---|
| Page Tree | Auto navigation |
| Table of Contents | Long documents |
| Status | Workflow visibility |
| Excerpt Include | Reusable documentation |
| Children Display | Auto-generated sections |
| Panel | Highlight warnings |
Macros convert pages into structured applications — not static documents.
5. Creating a Real Knowledge Base (Confluence + Jira)
Typical Support Workflow:
1 User raises ticket in Jira
2 Issue linked to KB article
3 Support resolves issue
4 Article updated for future reuse
Result → ticket volume drops over time.
Enterprise Pattern
Incident → Root Cause → Document → Reuse → No repeat issue
6. Page Permissions & Collaboration Best Practices
Always Use Groups
Bad:
Give edit to Rahul, Amit, Priya
Good:
space-eng-editors group
Ownership Rule
Each space must have:
1 business owner
1 technical owner
Editing Model
| Content Type | Who Edits |
|---|---|
| Policies | Restricted |
| Runbooks | Team editable |
| Guides | Open edit |
7. Admin Troubleshooting Superpower
When user says “I cannot see page”:
1 Check Global access
2 Check Space permission
3 Check Page restriction
Never start at page level.
Recommendation Section (Production Setup Guide)
Folder & Naming Standard
SPACE KEY: ENG, HR, OPS
PAGE PREFIX: ENG-ARCH-, OPS-RUN-
GROUPS: space-ENG-editors
Governance Rules
✔ Monthly permission audit
✔ No personal ownership pages
✔ Archive outdated content quarterly
✔ Every page must have owner
High-Quality Team Setup
Engineering → Open edit
HR → Restricted edit
Operations → Runbook controlled edit
Management → View only
What You Achieved After This Guide
You now know how to:
Secure Confluence properly
Structure documentation logically
Build reusable knowledge base
Reduce support tickets
Prevent permission chaos
Next Part
Part 2 — Jira Service Management Series
💼 Need Help with Camunda, Jira, or Enterprise Workflows?
I help teams solve real production issues and build scalable systems.
Services I offer:• Camunda & BPMN workflow design and debugging • Jira / Confluence setup and optimization • Java, Spring Boot & microservices architecture • Production issue troubleshooting
🔗 View Services: https://shikhanirankari.blogspot.com/p/professional-services.html
📩 Email: ishikhanirankari@gmail.com | info@realtechnologiesindia.com
✔ Available for quick consulting calls and project-based support✔ Response within 24 hours
🎥 Learn IT with Shikha on YouTube
Prefer learning through videos? Watch practical tutorials on Kafka, Camunda, Alfresco, Java, Spring Boot, Microservices and Enterprise Architecture.▶ Subscribe to Learn IT with Shikha on YouTube
Comments
Post a Comment