## Problem to solve Our current messaging when a user links a SAML identity is confusing to new users. We should improve the language so a user understands what it means to link their GitLab account to SAML. | SSO zero state | GitLab sign in to connect | Signed in warning | Success | | ------ | ------ | ------ | ------ | |  |  |  |  | ### Intended users Anyone in a SAML enabled group! ## User experience goal Users understand: * What it means to link a SAML identity * That they need to log in * When they need to create a new account ## Proposal - The set up process is the awkward part. - Documentation fix? - Banner: You have followed an SSO link, if you have a Gitlab account you want to link to this account, Sign in with your gitlab account and click authorize. - Log in SSO panel: by linking your gitlab account (_____) to your SSO/IDP(URL) #### [Figma working file](https://www.figma.com/file/1qJsJrvT3vqn5qGqrRnmFv/271631-Saml-linking-experience?node-id=1%3A55) #### Proposed Updated Text | | SSO zero state | GitLab sign in to connect | Signed in warning | Success | | ------ | ------ | ------ | ------ | ------ | | updated text | _To access `GROUP NAME` you need to sign in with your organization's SSO credentials_ | Connect your GitLab account to your organization's SSO credentials | _Clicking Authorize will transfer ownership of your GitLab account to your Organization_ | _Your organization's SSO has been connected to your GitLab account_ | |Occurence in UI |  |  |  |  | | updated in UI |  |  |  |  | ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> Please run the package-and-qa job to ensure all existing SAML tests are fine.