Skip to content

Draft: Updated Instructions for namespace association to group

Patrick Hynes requested to merge namespace-claim-update into main

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Why

As part of customers getting setup on SaaS, there is a need to claim a namespace to be used. The issue, this MR tries to address is, that when I followed the documentation today with a customer. The fact that the user is expected to create their top level namespace (a group) so they can link their subscription to that namespace, is not explicitly stated. When we followed the existing documentation "Link the subscription to a group" it produced a list of namespaces but only the customers username was present.

I then assumed we should go to the customers gitlab.com page and create an empty group based on their desired namespace. Once done, the desired namespace appeared in the drop down within the customer portal.

What is changed

I have edited the instructions on this page to capture this detail

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 Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • 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
    • 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
Edited by Patrick Hynes

Merge request reports