Create a new permission to define specific actions or capabilities in your RBAC system. Permissions can be assigned directly to API keys or included in roles.
Use hierarchical naming patterns like documents.read
, admin.users.delete
, or billing.invoices.create
for clear organization.
Important: Permission names must be unique within the workspace. Once created, permissions are immediately available for assignment.
Required Permissions
Your root key must have the following permission:
rbac.*.create_permission
Unkey uses API keys (root keys) for authentication. These keys authorize access to management operations in the API. To authenticate, include your root key in the Authorization header of each request:
Authorization: Bearer unkey_123
Root keys have specific permissions attached to them, controlling what operations they can perform. Key permissions follow a hierarchical structure with patterns like resource.resource_id.action
(e.g., apis.*.create_key
, apis.*.read_api
).
Security best practices:
Permission created successfully
The response is of type object
.