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)

4

Controls:

  • Who can login

  • Who can create spaces

  • Admin rights

Best Practice: Always assign permissions to groups, never individuals.

Space Permissions (Department Access)

4

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

ToolBest ForNot Ideal For
ConfluenceTeam collaboration documentationPublic documentation portals
NotionPersonal/team notesLarge enterprises governance
SharePointCorporate file storageTechnical knowledge base
GitBookPublic developer docsInternal workflows

Conclusion:
Use Confluence when knowledge changes frequently and many teams collaborate.

4. Confluence Macros Every Team Should Use

4

Essential Macros

MacroPurpose
Page TreeAuto navigation
Table of ContentsLong documents
StatusWorkflow visibility
Excerpt IncludeReusable documentation
Children DisplayAuto-generated sections
PanelHighlight 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 TypeWho Edits
PoliciesRestricted
RunbooksTeam editable
GuidesOpen 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

💼 Professional Support Available

If you are facing issues in real projects related to enterprise backend development or workflow automation, I provide paid consulting, production debugging, project support, and focused trainings.

Technologies covered include Java, Spring Boot, PL/SQL, Azure, CMS and workflow automation (jBPM, Camunda BPM, RHPAM, Flowable).

📧 Contact: ishikhanirankari@gmail.com | info@realtechnologiesindia.com

🌐 Website: IT Trainings | Digital metal podium     


Comments

Post a Comment

Popular posts from this blog

OOPs Concepts in Java | English | Object Oriented Programming Explained

Image
🔹OOPS (Object Oriented Programming System) in Java Object-Oriented Programming (OOPS) is a programming paradigm that uses classes and objects to design software. It simplifies development and maintenance by applying key concepts: 📌 Class: Class   is a user-defined data type which defines its properties and its functions. Class is the only logical representation of the data. For example, Human beings in an organisation is a class like Employee. The age, name, department, salary etc. of a human being/employee are its properties, and the jobs performed by the employees in an organisation are known as functions.  The class does not occupy any memory space till the time an object is instantiated. A class is a user-defined data type that defines properties and functions. For example: Class: Employee Properties: name, age, salary Functions: work(), attendMeeting() A class does not occupy memory until an object is created. ...
Read more

Scopes of Signal in jBPM

Image
💡 Introduction Signals in jBPM 7 are a core part of event-driven workflow design. They allow asynchronous communication between process instances, making it possible to start , interrupt , or coordinate processes without direct linking. However, signals can have different scopes , which define how far the signal travels and who receives it . Let’s explore the four available scopes in detail: 🔹 Process Scope 🔹 Default Scope 🔹 External Scope 🔹 Project Instance Scope 🧩 1️⃣ Process Scope 📘 Definition Process scope signals are local to a single process instance or its child subprocesses . They are not visible outside that instance hierarchy. 📋 Use Case Used for communication inside the same process , like triggering subprocesses or event sub-processes. 🖼️ Process Scope Example Below is an example of a simple process-scoped signal. Only this process (or its subprocess) will catch this signal. ⚙️ 2️⃣ Default Scope 📘 Definition The default scope ...
Read more

jBPM Installation Guide: Step by Step Setup

  jBPM Installation Guide – Step by Step for Beginners If you are starting with jBPM (Java Business Process Management) , the first step is to set up your environment. In this guide, we’ll walk through how to install jBPM, configure it, and run your first business process. 🔎 What is jBPM? Before we dive into installation, a quick recap: jBPM is an open-source Business Process Management (BPM) suite , written in Java, that allows you to model, execute, and monitor workflows using BPMN 2.0 standards. It can run standalone , embedded in applications , or deployed on a Java EE server . 🖥️ Prerequisites Before installing jBPM, make sure you have: Java JDK 11 or later (Java 17 is commonly used) Maven 3.x (for building and managing dependencies) Git (optional, if you want to clone sample projects) A Database (H2, MySQL, PostgreSQL, or Oracle) – jBPM ships with H2 for testing At least 4GB RAM (8GB recommended for Workbench & KIE Server) 📦 Download ...
Read more