You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/organizations/roles-and-permissions.mdx
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,7 +91,7 @@ You cannot delete a role that is still assigned to members of an organization. C
91
91
92
92
## Permissions
93
93
94
-
Permissions grant users privileged access to resources and operations, like creating and deleting. Clerk supports two types of permissions: **System** and **Feature**.
94
+
Permissions grant users privileged access to resources and operations, like creating and deleting. Clerk supports two types of permissions: **System** and **Custom**.
95
95
96
96
> [!IMPORTANT]
97
97
> In the Clerk Dashboard, permissions appear in the format `<feature>:<permission>`. However, the `org:` prefix is automatically applied under the hood for all organization-scoped permissions. This means that when checking permissions in your code, always include the full key with the prefix (`org:<feature>:<permission>`).
@@ -116,16 +116,16 @@ Clerk's system permissions consist of the following:
116
116
You can assign these system permissions to any role.
117
117
118
118
> [!WARNING]
119
-
> System permissions aren't included in [session claims](/docs/guides/sessions/session-tokens#default-claims). To check permissions on the server-side, you must [create feature permissions](#feature-permissions).
119
+
> System permissions aren't included in [session claims](/docs/guides/sessions/session-tokens#default-claims). To check permissions on the server-side, you must [create custom permissions](#custom-permissions).
120
120
121
-
### Feature permissions
121
+
### Custom permissions
122
122
123
123
> [!WARNING]
124
-
> Feature permissions require a [paid plan](/pricing){{ target: '_blank' }} and the Enhanced B2B SaaS Add-on for production use, but free to use in development mode so that you can try out what works for you. See the [pricing](/pricing){{ target: '_blank' }} page for more information.
124
+
> Custom permissions require a [paid plan](/pricing){{ target: '_blank' }} and the Enhanced B2B SaaS Add-on for production use, but free to use in development mode so that you can try out what works for you. See the [pricing](/pricing){{ target: '_blank' }} page for more information.
125
125
126
126
Custom permissions let you define fine-tuned access control within your organization. Each permission is tied to a feature, and can be assigned to one or more roles. To create a custom permission, you must first create a role (e.g. **sales**) and a feature within that role (e.g. **invoices**). Once both exist, you can define specific permissions (e.g. **create**) related to that feature.
127
127
128
-
To create a new custom permission:
128
+
To create a new permission:
129
129
130
130
1. In the Clerk Dashboard, navigate to [**Roles & Permissions**](https://dashboard.clerk.com/last-active?path=organizations-settings/roles).
131
131
1.[Create a new role](#custom-roles) or use an existing role from the list.
0 commit comments