Commit aaf8005c authored by Mario Mora's avatar Mario Mora Committed by Mike Jang

Docs: Additional visibility for use of email during SCIM provisioning

parent 68336cd2
...@@ -202,6 +202,10 @@ Upon the next sync, the user is deprovisioned, which means that the user is remo ...@@ -202,6 +202,10 @@ Upon the next sync, the user is deprovisioned, which means that the user is remo
NOTE: NOTE:
Deprovisioning does not delete the user account. Deprovisioning does not delete the user account.
During the synchronization process, all of your users get GitLab accounts, welcoming them
to their respective groups, with an invitation email. When implementing SCIM provisioning,
you may want to warn your security-conscious employees about this email.
```mermaid ```mermaid
graph TD graph TD
A[Remove User from SCIM app] -->|IdP sends request to GitLab| B(GitLab: Is the user part of the group?) A[Remove User from SCIM app] -->|IdP sends request to GitLab| B(GitLab: Is the user part of the group?)
...@@ -209,10 +213,6 @@ graph TD ...@@ -209,10 +213,6 @@ graph TD
B -->|Yes| D[GitLab removes user from GitLab group] B -->|Yes| D[GitLab removes user from GitLab group]
``` ```
During the synchronization process, all of your users get GitLab accounts, welcoming them
to their respective groups, with an invitation email. When implementing SCIM provisioning,
you may want to warn your security-conscious employees about this email.
## Troubleshooting ## Troubleshooting
This section contains possible solutions for problems you might encounter. This section contains possible solutions for problems you might encounter.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment