-
AFTER IT has added the user to AD and DUO (and done a push, or wait 24 hours as per above), Gitlab IT Onboarding Owner (Denis K) would do next steps.
-
Go to the Gitlab Group as noted in the Ticket (they usually have this wrong in the template, sometimes it is right, ETPM will always confirm where to add them)
-
Click Manage -> Members -> Invite Members
-
Invite comes up – fill out the email and then click the name (VERY IMPORTANT) that comes up underneath the email field:
-
Change Role and click Invite
-
The user should receive Invite in email. Send this reply to them on the IT.Ticket email:
We’ve sent the Direct Invite to you for your group, it will come from Gitlab. Look for the email in Outlook and if you don't see it check the Barracuda Networks gateway. You can also check Outlook Junk folder. You MUST find this email and click on it to get the right access. Otherwise, you'll only be Guest access to your subgroup.
If you have difficulty signing in with SSO, this probably means you are Use Case 2 (you have an existing Gitlab account and need to merge them). Please follow the Gitlab Onboarding Wiki Use Case 2 steps here EXACTLY AS WRITTEN to merge the accounts. You can't skip steps.
Your Team Wiki under the left-hand navigation bar Plan subheading, should point you to the right resources to understand how to use the system and any team info shared. If your team has NOT created a Wiki, you can go to the Edifecs Main Wiki to find instructions on how we typically manage the dev process.
Lastly, if you need Gitlab Support, post to the GLU Teams Channel and if you still need help, create an account using your Edifecs email (MUST) GitLab Support Site. You will be able to filter by YOUR requests, or all Organizational requests. CC ETPM (April Drake) on the Support tickets.