Skip to content

Commit b9b77e0

Browse files
Updates for the authorization concepts and user guide
1 parent 13efe4b commit b9b77e0

File tree

6 files changed

+74
-59
lines changed

6 files changed

+74
-59
lines changed

docs/components/concepts/access-control/authorizations.md

Lines changed: 59 additions & 50 deletions
Large diffs are not rendered by default.

docs/components/identity/authorization.md

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,14 +4,16 @@ title: Authorizations
44
description: "Learn how to manage authorizations to an orchestration cluster."
55
---
66

7-
An authorization grants permissions to an **owner** to perform actions on a specific **resource**.
7+
An authorization grants an **owner** access to a **resource** and defines the specific **permissions** they have.
88

9-
- The **owner** is the entity that receives permissions, such as a [user](user.md), [group](group.md), [role](role.md), [client](client.md), or [mapping rule](./mapping-rules/manage-mapping-rules.md).
10-
- The **resource** is the object that the permissions apply to, like a process definition or a decision instance.
9+
- The **owner** is the entity that receives permissions, like [user](user.md), [group](group.md), [role](role.md), [client](client.md), or [mapping rule](./mapping-rules/manage-mapping-rules.md).
10+
- The **resource** is the object that the permissions apply to, like process definition, decision definition, or system. See the full list of [available resources](/components/concepts/access-control/authorizations.md#available-resources).
1111

12-
Each authorization specifies which actions (e.g., `READ`, `UPDATE`, `DELETE`) the owner is allowed to perform on the resource.
12+
Each authorization specifies which permissions (e.g., `READ`, `UPDATE`, `DELETE`) the owner has on the resource.
1313

14-
To learn more about authorizations, see [authorizations](/components/concepts/access-control/authorizations.md).
14+
:::tip
15+
To learn more, see the [authorization concepts](/components/concepts/access-control/authorizations.md).
16+
:::
1517

1618
## Create an authorization
1719

@@ -22,7 +24,7 @@ To create a new authorization:
2224
3. Provide the following information:
2325
- **Owner type**: The entity to which you want to assign permissions, such as a User, Group, Role, Client, or Mapping rule.
2426
- **Owner ID**: The unique ID of the owner.
25-
- **Resource type**: The selected resource type from the list of [available resources](/components/concepts/access-control/authorizations.md#available-resources).
27+
- **Resource type**: The selected resource type.
2628
- **Resource ID**: The ID of the resource. Use `*` to grant permissions for all resources of the selected type.
2729
4. Select the permissions you want to grant.
2830
5. Click **Create authorization**.
@@ -31,6 +33,10 @@ The authorization is created, and the owner is granted the specified permissions
3133

3234
![identity-create-authorization-tab](./img/create-authorization-tab.png)
3335

36+
## Update an authorization
37+
38+
Authorizations cannot be updated after they are created. To edit an authorization, you must first [delete](#delete-an-authorization) the existing one and then create a new authorization with the updated permissions.
39+
3440
## Delete an authorization
3541

3642
To delete an authorization:
96.8 KB
Loading

docs/components/identity/mapping-rules/assign-mapping-rules-to-tenants.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ import TabItem from "@theme/TabItem";
1111
Mapping rules grant access to a tenant based on access token claim values. This guide details how to assign, update, or remove these rules.
1212

1313
:::tip
14-
To learn more about mapping rules and tenants, see the [mapping rules documentation](manage-mapping-rules.md) and [tenant management documentation](/self-managed/components/orchestration-cluster/identity/manage-tenants.md).
14+
To learn more about mapping rules and tenants, see the [mapping rules](manage-mapping-rules.md) and [tenant management](/self-managed/components/orchestration-cluster/identity/manage-tenants.md) user guides.
1515
:::
1616

1717
1. Log in to the Identity UI and go to the **Tenants** tab.

docs/components/identity/mapping-rules/manage-mapping-rules.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ import TabItem from "@theme/TabItem";
1111
In this guide, you will learn how to manage mapping rules in Identity and how to control the Camunda entities related to them.
1212

1313
:::tip
14-
To learn more about the concept of mapping rules, see the [mapping rules documentation](../../concepts/access-control/mapping-rules.md).
14+
To learn more, see the [mapping rules concepts](../../concepts/access-control/mapping-rules.md).
1515
:::
1616

1717
You can manage mapping rules from the **Mapping rules** tab in Identity.

docs/components/identity/mapping-rules/mapping-rules-authorizations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ import TabItem from "@theme/TabItem";
1111
This guide explains how to assign users, groups, roles or clients permission to manage specific mapping rules. To learn how to create mapping rules themselves, see [Manage mapping rules](manage-mapping-rules.md).
1212

1313
:::tip
14-
To learn more about the concept of mapping rules, see the [mapping rules documentation](../../concepts/access-control/mapping-rules.md).
14+
To learn more, see the [mapping rules concepts](../../concepts/access-control/mapping-rules.md).
1515
:::
1616

1717
1. Log in to the Identity UI and navigate to the **Authorizations** tab.

0 commit comments

Comments
 (0)