Answer
ArgoCD supports SSO via OIDC (directly or through its bundled Dex connector for LDAP, SAML, GitHub, etc.). Users log in with their identity provider; group claims from the token are mapped to ArgoCD roles in the RBAC policy via `g, <group>, <role>` lines, centralizing access control with corporate identity.
g, "my-org:platform-team", role:admin
g, "my-org:developers", role:devReal-world example Engineers log in with corporate SSO, and their IdP group memberships automatically grant the right ArgoCD roles.