From 80444d60f98bb94a98e96d642a84b0a1bea042ea Mon Sep 17 00:00:00 2001 From: Ieva Date: Tue, 4 Apr 2023 14:22:02 +0100 Subject: [PATCH] Docs: define RBAC n/a for a scope (#65782) * define n/a scope * Update docs/sources/administration/roles-and-permissions/access-control/custom-role-actions-scopes/index.md Co-authored-by: Christopher Moyer <35463610+chri2547@users.noreply.github.com> * linting --------- Co-authored-by: Christopher Moyer <35463610+chri2547@users.noreply.github.com> --- .../access-control/custom-role-actions-scopes/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/sources/administration/roles-and-permissions/access-control/custom-role-actions-scopes/index.md b/docs/sources/administration/roles-and-permissions/access-control/custom-role-actions-scopes/index.md index 33c22c8a913..5176af499f4 100644 --- a/docs/sources/administration/roles-and-permissions/access-control/custom-role-actions-scopes/index.md +++ b/docs/sources/administration/roles-and-permissions/access-control/custom-role-actions-scopes/index.md @@ -207,3 +207,4 @@ The following list contains role-based access control scopes. | `settings:*` | Restrict an action to a subset of settings. For example, `settings:*` matches all settings, `settings:auth.saml:*` matches all SAML settings, and `settings:auth.saml:enabled` matches the enable property on the SAML settings. | | `teams:*`
`teams:id:*` | Restrict an action to a set of teams from an organization. For example, `teams:*` matches any team and `teams:id:1` matches the team whose ID is `1`. | | `users:*`
`users:id:*` | Restrict an action to a set of users from an organization. For example, `users:*` matches any user and `users:id:1` matches the user whose ID is `1`. | +| `n/a` | `n/a` means not applicable. If an action has `n/a` specified for the scope, then the action does not require a scope. For example, the `teams:create` action does not require a scope and allows users to create teams. |