Clarify Group::Auth and Group::Workspace

Problem

Currently, there is confusion between ownership of certain concepts within the GitLab product between ~"group::access" and ~"group::workspace". This issue is a place for all of us to collaborate on where the distinction between Access and Workspace lies.

Note that I titled this with "group::Auth" because I think once we clarify this ownership, it's a good time to officially change the ~"group::access" name.

Access (Auth)

• User provisioning / deprovisioning(including SAML, LDAP, OAuth, SCIM)
• Inviting new users to GitLab (not 100% sold on this one)
• User lifecycle management
• Credential Inventory
• OAuth Identity Provider
• Authentication (verify who you are)
• Authorization (verify what you have access to)
• Roles & Permissions (fine grained permissions, RBAC)
• Service Accounts
• Password Policy
• Group Access Tokens
• Personal Access Tokens
• Project Access Tokens
• IP Allow List
• Admin Experience with respect to user and token management
• Enterprise Users - verify domain, verify users. Structuring these users into Groups/Projects belongs to ~"group::workspace"
• User Management
• when admin creates a user, it belongs to ~"group::authentication and authorization"

Workspace

• Inheritance
• Namespace (eventual "Workspace")
• Groups
• Sub-Groups
• Projects
• Sharing groups, sub-groups, and projects and the inheritance that happens when they are shared
• Admin experience with respect to group and project assignment
• User Profile
• when a group owner adds a member to a group, it belongs to ~"group::workspace"
• Topics

~"group::fulfillment"

-Licensing

Notes

1. I noticed that Users is under Workspace here. I think it should be moved under Auth.

Gray Areas

1. User Email Address Attribute - gitlab-org&6537