Answer
ArgoCD RBAC controls what authenticated users and groups can do within ArgoCD—viewing, syncing, creating, or deleting Applications, and managing clusters, repos, and projects. It's separate from Kubernetes RBAC (which governs cluster resource access) and is defined in the argocd-rbac-cm ConfigMap using policy rules and roles.
# argocd-rbac-cm
data:
policy.default: role:readonlyReal-world example Developers get a role that can view and sync their team's apps but not delete clusters or edit other teams' apps.