> For the complete documentation index, see [llms.txt](https://wiki.datadike.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.datadike.com/pam/administration/identities.md).

# Users and identities

| Page                                                                                                                    | What it covers                                                                                                                                                                               |
| ----------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Users and groups](https://wiki.datadike.com/pam/administration/identities/users-and-groups.md)                         | Register the people who use the solution, group them, and control activation, expiry, and authentication requirements.                                                                       |
| [Roles and permissions](https://wiki.datadike.com/pam/administration/identities/roles.md)                               | What a user may do inside the console, how organization roles differ from system roles, and how multi-tenancy scopes them.                                                                   |
| [LDAP and Active Directory](https://wiki.datadike.com/pam/administration/identities/ldap-and-ad.md)                     | Authenticate console users against an LDAP or Active Directory server and provision their user records from directory attributes, including the group membership that drives authorizations. |
| [Single sign-on](https://wiki.datadike.com/pam/administration/identities/sso.md)                                        | Delegate console login to a corporate identity provider over SAML2, OIDC, OAuth2, CAS, or Slack, and map the provider's attributes onto user records here.                                   |
| [Single sign-on with Microsoft Entra ID](https://wiki.datadike.com/pam/administration/identities/sso-entra-id.md)       | Let users sign in to the console with their Microsoft work account, by registering the solution in Microsoft Entra ID and connecting it over OIDC.                                           |
| [Single sign-on with Google Workspace](https://wiki.datadike.com/pam/administration/identities/sso-google-workspace.md) | Let users sign in to the console with their Google Workspace account, through a custom SAML app in the Google Admin console and the SAML2 method here.                                       |
| [Multi-factor authentication](https://wiki.datadike.com/pam/administration/identities/mfa.md)                           | Require a second authentication factor for console access — globally, or per user — how a user enrols an authenticator app, and how to reset a factor someone has lost.                      |
