Add ADR for organization sign in changes

Peter Hegmanrequested to merge
adr-organization-sign-in into main

Why is this change being made?

Since the original proposal for organization sign in there has been a lot of discussion in https://gitlab.com/gitlab-org/gitlab/-/issues/577327 and we have decided to change how the flow works. See https://gitlab.com/gitlab-org/gitlab/-/issues/577327#note_2887041345 specifically.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct
    • The when to get approval handbook section explains when DRI approval is required
    • The who can approve handbook section explains how to identify the DRI
    • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
    • The approver may merge the MR. If they approve but don't merge, you can merge.
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Division: If the update affects your division, share the MR in your division Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Commits

  • Add ADR for organization sign in

Document decision to not use branded organization sign in pages and instead use a cookie to route to the correct organization/cell

Edited by Peter Hegman

Merge request reports