Docs: Compliance info needs to be split by audience
Right now, the Compliance information (https://docs.gitlab.com/ee/administration/compliance.html) is under "Set up your organization." The primary purpose of the content in this section of the docs is to:
- Help users set up namespaces, groups, projects, and members, and
- To give the members the roles they need to do their job.
The primary purpose of the Compliance information is to make your instance, group, or project compliant.
As a company, we think of the compliance features as one set of features.
However, as a user, you either:
- Are an administrator on a self-managed instance, and have access to the Admin Area, where you can configure compliance features
- Are a user on a self-managed instance, and you can take advantage of some compliance features
- Are an "admin" for your company on GitLab.com, and you can take advantage of some compliance features
Proposal
- Admin content should be separate from non-admin content.
- GitLab.com content should be separate from self-managed content.
Pages can be things like: Make your instance compliant, Make your project compliant, Make all projects in your group compliant
- Make your instance compliant would go in the Administer section of the docs.
- Make your project (or the projects in your group) compliant would go under Organize work with projects. (I think Compliance used to be under there.)
The list of audit event types is auto-generated, so potentially we could generate two different pages--one for instance, one for group/project?
Edited by Suzanne Selhorn