gitlab policy change re SSO-linked accounts

gistfile1.txt

Date: Tue, 11 Jul 2023 12:13:53 -0500 (CDT)
From: GitLab <security@gitlab.com>
Subject: [Action Required] Review GitLab Emails Before Lock
To: (personal email, primary on my GitLab account)
Reply-To: security@gitlab.com
Message-ID: (redacted)

We want to let you know that we recently changed the way Enterprise Users <https://docs.gitlab.com/ee/user/enterprise_user/>
are defined <https://about.gitlab.com/handbook/support/workflows/gitlab-com_overview.html#enterprise-users> to ensure that
members can be managed by valid enterprise admins and bolster security for your organization.

As part of that work, for any user designated as an Enterprise User, the primary email address will only be changeable to
an email matching your group’s verified domain(s).

Please also note that future work is planned to apply this restriction to secondary emails as well and no further notice
will be sent.

You are receiving this email because you are a member of a paid group with a SSO login tied to that group, which means
you are likely to be designated an Enterprise User. You will be designated an Enterprise User if the group has already
verified the matching domain, or does so in the future.

If you are designated an Enterprise User, you will receive a notification email stating this change, and the account is
owned by your organization.

This change will be effective August 1, 2023 or later.

Before August 1, 2023, we recommend that you:
- move any personal contributions (such as projects
 <https://docs.gitlab.com/ee/user/project/settings/#transfer-a-project-to-another-namespace>) to a+separate account
 reserved for personal use
- ensure that your account’s emails <https://gitlab.com/-/profile/emails> are organizational emails.

If you do not have any personal emails or contributions on your GitLab user account, then no action is required.

Kind regards,
GitLab Security

issue ticket

https://gitlab.com/gitlab-org/gitlab/-/issues/416117