Skip to content

Update GitLab Learn login steps

Diana Logan requested to merge dianalogan-master-patch-12396 into master

Why is this change being made?

Update step 1. of https://about.gitlab.com/handbook/people-group/learning-and-development/gitlab-learn/user/#first-time-login-to-gitlab-learn to match the login options shown on the screen, and to clarify that non-team members can use their GitLab.com account or sign up with an email address.

This community contributor issue shows that we could make it clearer: #13376 (closed)

Step 1 instructions now:

GitLab team members should choose LogIn with GitLab Team Members SSO via Okta. Non-team members should choose LogIn with Email and Password.

GitLab Learn login screen now:

image

Step 1 instructions proposed:

  1. GitLab team members should choose GitLab Internal Team Member SSO via Okta. Non-team members should choose Login using your credentials. Non-team members can use their GitLab.com login, or sign up to GitLab Learn using an email address.

Proposed instructions match the UI text and add that either GitLab.com or and email address can be used.

Author Checklist

  • Provided a concise title for the 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.
  • Assign reviewers for this change to the correct DRI(s)
    • 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 in 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.
  • 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 Diana Logan

Merge request reports

Loading