Delete permission
Remove a permission from your workspace. This also removes the permission from all API keys and roles.
Important: This operation cannot be undone and immediately affects all API keys and roles that had this permission assigned.
Required Permissions
Your root key must have the following permission:
rbac.*.delete_permission
Authorizations
Unkey uses bearer tokens for authentication. Public integrations use root keys, while the dashboard proxy uses short-lived JWTs. To authenticate, include the token in the Authorization header of each request:
Root keys have specific permissions attached to them, controlling what operations they can perform. Legacy permissions use tuple strings like api.*.create_key; resource permissions use Unkey Resource Names plus actions, like unkey:v1:ws_123:keyspaces/*#create_key.
Security best practices:
- Keep root keys secure and never expose them in client-side code
- Use different root keys for different environments
- Rotate keys periodically, especially after team member departures
- Create keys with minimal necessary permissions following least privilege principle
- Monitor key usage with audit logs.
Body
Specifies which permission to permanently delete from your workspace.
This can be a permission ID or a permission slug.
WARNING: Deleting a permission has immediate and irreversible consequences:
- All API keys with this permission will lose that access immediately
- All roles containing this permission will have it removed
- Any verification requests checking for this permission will fail
- This action cannot be undone
Before deletion, ensure you:
- Have updated any keys or roles that depend on this permission
- Have migrated to alternative permissions if needed
- Have notified affected users about the access changes
1 - 128^[a-zA-Z0-9_:\-\.\*]+$"perm_1234567890abcdef"
Response
Permission deleted successfully