Confluence groups

Classifier does not maintain its own user directory. Access is enforced by Confluence groups whose names match your configured naming rules.

Why groups matter

When an author saves a classified page:

1. Classifier calculates the page banner.
2. It converts the banner to a group name (prefix, separators, case).
3. It verifies the group exists in Confluence.
4. It sets page View/Edit restrictions to include that group.

If the group is missing, save is blocked.

Creating groups

Work with your IAM or security team:

1. Export or note your configured group prefix and separator from rollup rules.
2. For each classification combination you will use, compute the expected group name from a sample banner.
3. Create groups in Confluence administration → Groups.
4. Assign users based on your clearance process.

Validation

• The admin and space configuration UIs can validate that expected groups exist.
• On save, the plugin validates the banner group specifically.

:::tip Pilot with one space and two or three classifications. Confirm group names with a test save before rolling out the full scheme. :::

Space group prefix

Space admins can add a space group prefix so the same banner maps to different groups in different spaces. See Space settings.

Policy

Classifier uses group-only permissions on classified pages — individual user grants are avoided for consistency and auditability.

Next step

Space settings → or start classifying content