Prerequisites & planning
Plan these items before rolling Classifier out to authors. Misaligned groups are the most common source of blocked saves.
Roles
| Role | Responsibility |
|---|---|
| Confluence administrator | Global classification scheme, rollup rules, restriction mode, license |
| Space administrator | Optional space restriction, default classification, allowed list |
| Security / IAM | Create and maintain Confluence groups matching classifications |
| Authors | Classify content and confirm rollup on save |
Confluence groups
Classifier enforces access through Confluence groups only on classified pages.
For each classification combination you will use for restrictions:
- Decide the group naming rule (prefix, separators, lowercase — configured in rollup/permission settings).
- Create the group in Confluence with the exact derived name.
- Assign users to groups according to your clearance process.
:::tip Create groups for every classification you expect on pages before pilot users publish classified content. Saves fail if the banner group does not exist. :::
Choose a restriction mode early
| Mode | Best for |
|---|---|
| Selective restriction (default) | Collaboration spaces — many viewers, paragraph-level hiding |
| Most restrictive | Each page fully gated by its banner group |
| Classification-restricted space | Program/mission spaces — space access and classification group required |
See Restriction approach and Permissions overview.
Templates
Pre-built JSON templates ship with the project (DoD, NATO, UK, Canada, Australia, ISO, business). You can import one as a starting point and customize.
Template files live in the repository under test-templates/ and src/main/resources/templates/.
License
Production use requires a valid plugin license. Invalid licenses block configuration saves and classification operations. Check license status in the admin UI.