Skip to content

Clarify the conditions for Enterprise Users

Why is this change being made?

The original formatting of the Enterprise User section did not make it abundantly obvious that only one of the conditions needed to be meet. In order to address this, I have:

  1. Added some verbiage to explicitly state that only one of the two conditions needs to be met
  2. Adjusted formatting slightly to make the conditional more obvious at-a-glance

This will hopefully help folks who tend to skim (that's me!) when working quickly, so that they're less likely to get stuck on definitions.

Author Checklist

  • 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
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Edited by John Gaughan

Merge request reports