From fb01d8e96aae4606b880531450b10c757cfa2491 Mon Sep 17 00:00:00 2001 From: "gcp-cherry-pick-bot[bot]" <98988430+gcp-cherry-pick-bot[bot]@users.noreply.github.com> Date: Wed, 30 Apr 2025 15:44:44 +0200 Subject: [PATCH] website/docs: initial permissions: fix usage of term admin (cherry-pick #14300) (#14302) Co-authored-by: Dominic R fix usage of term admin (#14300) --- .../docs/users-sources/access-control/initial_permissions.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/users-sources/access-control/initial_permissions.mdx b/website/docs/users-sources/access-control/initial_permissions.mdx index 68bac85e6a..c0f0e39ac9 100644 --- a/website/docs/users-sources/access-control/initial_permissions.mdx +++ b/website/docs/users-sources/access-control/initial_permissions.mdx @@ -9,7 +9,7 @@ Initial permissions automatically assigns [object-level permissions](./permissio The purpose of initial permissions is to assign a specific user (or role) a set of pre-selected permissions that are required for them to accomplish their tasks. -An authentik Admin creates an initial permissions object (a set of selected permissions) and then associates it with either: 1. An individual user. 2. A role - in which case everyone in a group with that role will have the same initial permissions. +An authentik administrator creates an initial permissions object (a set of selected permissions) and then associates it with either: 1) an individual user 2) a role - in which case everyone in a group with that role will have the same initial permissions. ## Common use cases