RBAC
Role‑based access control ensures that only the right people can view patch data, plan jobs, and execute changes.
Use this guide to explore example roles and access patterns for Patch Management.
Example Roles
Typical patterns include:
| Role name | Permissions | Responsibility |
|---|---|---|
| Patch Viewer | Can view patch data and reports | Customer |
| Patch Operator | Can create and run jobs in non-production environments | Cloudaware |
| Patch Administrator | Can run jobs in production and manage configuration | Cloudaware |
| Approver/CAB | Can approve or reject change requests linked to patch jobs | Customer |
You can map these roles to identity provider groups via SSO.
Principles
When designing RBAC:
- Use least privilege — grant only the permissions each role needs.
- Separate duties between planning, approval, and execution where required.
- Review access regularly, especially for production‑level permissions.