All 29 RBAC questions
More in RBAC
What is a local account and when would you use one? How do you manage RBAC declaratively under GitOps? How do you restrict which repositories a project can use? How do you prevent a team from deploying to namespaces they don't own? How do AppProjects and RBAC work together for multi-tenancy? How do you grant fine-grained permissions like sync but not delete? How do you manage RBAC for API/automation accounts (project roles and tokens)? How do you troubleshoot 'permission denied' errors in ArgoCD? How does the scopes setting affect group mapping? How do project roles and tokens enable least-privilege automation?
Advertisement
Back to results for “Applications”
ArgoCD › RBAC

What permissions are needed to manage ApplicationSets?

Intermediate

Answer

The applicationsets resource in RBAC controls who can create/update/delete ApplicationSets. Because an ApplicationSet can generate many apps, this is a powerful permission usually reserved for platform admins, separate from ordinary application sync rights.
p, role:platform, applicationsets, *, '*/*', allow
Real-world example Only platform admins can edit ApplicationSets, since one change can spawn or remove many Applications.

Common follow-ups: Why guard ApplicationSet permissions tightly? | Which resource governs them?

Applications Multi-cluster RBAC
All 29 RBAC questions