 The Enterprise IT environment is usually complex, full of products and technologies from different providers, systems and different applications. Today, I want to show you one example of how GitLab can play well with others. Enterprise IT environments are all different because they are designed to serve different purposes. Nevertheless, there are technologies that are pretty mature and transversal to these environments, such as identity and access management tools. In this story, I am assistant administrator, a wizard who is in charge of maintaining and configuring the environment. And I want to reuse my Enterprise directory to authenticate my users in GitLab. After all, I already have them here. Then, I can use GitLab LDAP integration to sign in. But there is something I am not happy about here, and it's this register tab. Based on my identity plan, employees must use LDAP credentials, and standard authentication is reserved for local logins in a few accounts, so this register option is not needed in this case. Luckily, in GitLab, I can quickly modify the sign-up settings. I can disable it and also activate sending a confirmation email on sign-up. Good, now the register option is gone, and the users will use LDAP to login. And now, consider this. We have three new employees that joined the data management department, and we need them to be added to GitLab data management group as well. So, because I am a great wizard or system administrator, I configured the directory a long time ago. I already have this group created here. Look, here it is, data management. In GitLab, the data management group is called GitLab data experts. I select it, and in settings, enable LDAP synchronization. This will give me the ability to quickly sync anyone from my LDAP with GitLab, and grant them the right permissions. In this case, anyone from LDAP data management group will get developer permission level for all the projects within this GitLab group. I notice it is syncing now, and there you go. The new employees were added to the data management group in GitLab as developers, the permission level I configured. And its membership to this group is managed using LDAP. I can add more synchronizations if I need it. This will be up to my identity governance and access management program. Quick takeaways. If the employees leave the company, they will be disabled from LDAP. Therefore, we will automatically lose any access to GitLab. GitLab plays well with others, plays well with identity and access management tools, making it ready to be plugged into IT enterprise environments. Stay tuned, and let's continue learning at GitLab.