Documentation Hierarchy for multiple business units with multiple project technical projects

Cornelius Dickson_woh7nb

Hi Team,

We are initiating a trial run for Confluence documentation. Our institution is keen on adhering to the best practices for managing technical documents across various projects, each managed by distinct Business Units. We aim to centrally monitor the quality of documentation and enforce granular-level control over access to pages and namespaces.

Could you please provide a guide that will assist us in accomplishing this objective?

Kristian Klima_gtcuat

Hi @Cornelius Dickson and welcome.

For space access control, the best way is to create user groups and assign individual users to those groups.

You can set up individual user groups' permissions individually for specific spaces.

Example: Group A has full access rights to Space 1 and Space 2, read only access to Space 3 and no access to Space 4. It's literally mix and match.

On top of that, you can grant individual users their own level of access per space irrespective of their group membership. To continue on the example above, Joe Doe from Group A, which has no access to Space 4, can be granted full rights in Space 4. Obviously, those can be removed at any time.

 

For even more granularity, you can restrict individual pages to specific users (can view, view and edit, no access).

The overall policies would be determined by assigning Admin rights to individual (or groups). Admins would, as per your policies, assign users to groups and groups to spaces etc.

 

For quality control, there are apps in the Marketplace such as Scroll Content Quality for Confluence (free app) which allows you to set up your rules per space and run reports per page and per space.

There are other apps too (search for quality control) I just listed the one we're using.