User Journey Documentation for Authentication and Authorization

Problem to solve

• Fragmented documentation: Authentication and authorization documentation is spread across multiple pages making it difficult to find comprehensive information.
• Technical vs user-centric: Most of the documentation is technically focused. It misses the user experience and properly setting up access in context of what they are trying to achieve.
• Onboarding friction: New users struggle to identify the best way to set up their access controls in GitLab, often leading to misconfiguration down the road.

Proposal

1. Journey Mapping: @ipelaez1 has the jobs to be done and workflow for end to end. This could be relevant to our navigation structure and how this fits in with greater journey such as setting up groups and projects
2. Documentation Architecture
   • Identify parent nodes for both authentication and authorization topics as it pertains to the user (not GitLab)
   • Identify auth related topics nested in sub-pages that should be standalone or married to larger auth topics
   • Revisit the left navigation structure
   • New card journey

Examples

• https://developer.salesforce.com/docs/atlas.en-us.securityImplGuide.meta/securityImplGuide/security_sharing_setup.htm
• https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html
• https://docs.stripe.com/get-started
• https://help.okta.com/en-us/content/topics/security/org-security.htm