Apply suggestions from code review

Author: georgios-goulos

docs/apis-tools/orchestration-cluster-api-rest/orchestration-cluster-api-rest-authentication.md

@@ -19,7 +19,7 @@ This page explains how to authenticate requests to the Orchestration Cluster RES
 | SaaS                                                                              | OIDC-based Auth        | ❌                      | ❌                 | ✅ (required)           |
 
 :::info Authentication vs. authorization
-Authentication establishes who is calling the Orchestration Cluster REST API (for example, using basic authentication or an OIDC access token). Authorization determines what that caller can do, based on authorizations configured in Identity.
+Authentication establishes who is calling the Orchestration Cluster REST API (for example, using basic authentication or an OIDC access token). Authorization determines what that caller can do, based on authorizations configured in Admin.
 
 To learn more about authorization resources, permissions, and precedence (including user task permissions), see [Orchestration Cluster authorization](../../components/concepts/access-control/authorizations.md).
 :::

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

@@ -41,10 +41,10 @@ Understanding which identity is required for a given action helps you apply the
 
 In production setups, both the Orchestration Cluster Admin and the Management Identity can integrate with an external OIDC IdP (such as Entra ID) for unified user management, single sign-on (SSO), and consistent security policies.
 
-| Identity type                  | Description                                                                                                                                          | Default IdP              | External IdP support                  |
-| :----------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------- | :------------------------------------ |
+| Identity type               | Description                                                                                                                                          | Default IdP              | External IdP support                  |
+| :-------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------- | :------------------------------------ |
 | Orchestration Cluster Admin | Built-in user management with support for external IdP integration via OIDC. Connects to enterprise IdPs such as Microsoft Entra ID, Okta, and more. | Built-in user management | OIDC integration with enterprise IdPs |
-| Management Identity            | Uses Keycloak by default, but can be configured with an external IdP via OIDC.                                                                       | Keycloak                 | OIDC integration with external IdPs   |
+| Management Identity         | Uses Keycloak by default, but can be configured with an external IdP via OIDC.                                                                       | Keycloak                 | OIDC integration with external IdPs   |
 
 ## Authentication vs. authorization
 
@@ -61,10 +61,10 @@ Authorization determines what an authenticated user or client is allowed to acce
 
 For example, a user's authorizations allow them to access Operate, view running or completed process instances, start new process instances, or claim and complete user tasks in Tasklist and through the Orchestration Cluster REST API.
 
-| Identity type                  | Authorization model              | Description                                                                                                                                                                      | Management interface                   |
-| :----------------------------- | :------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------- |
-| Orchestration Cluster Admin | Fine-grained permissions         | Controls access to applications, APIs, and runtime resources through specific permissions for each resource type and action (for example, `PROCESS_DEFINITION` and `USER_TASK`). | Camunda Admin UI or API               |
-| Management Identity            | Role-based access control (RBAC) | Uses predefined roles and permissions for users and groups to manage Console, Web Modeler, and Optimize.                                                                         | Keycloak admin console or external IdP |
+| Identity type               | Authorization model              | Description                                                                                                                                                                      | Management interface                   |
+| :-------------------------- | :------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------- |
+| Orchestration Cluster Admin | Fine-grained permissions         | Controls access to applications, APIs, and runtime resources through specific permissions for each resource type and action (for example, `PROCESS_DEFINITION` and `USER_TASK`). | Camunda Admin UI or API                |
+| Management Identity         | Role-based access control (RBAC) | Uses predefined roles and permissions for users and groups to manage Console, Web Modeler, and Optimize.                                                                         | Keycloak admin console or external IdP |
 
 ### How authentication and authorization work together
 

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

@@ -229,7 +229,8 @@ Users need specific permissions to access Orchestration Cluster web components:
 - UI access: Resource type `Component` and a resource key identifying the component:
   - `operate` for Operate access
   - `tasklist` for Tasklist access
-  - `identity` for Admin access
+  - `admin` for Admin access
+  - `identity` for Admin access (deprecated - please use `admin` instead)
   - `*` for access to all components
 - Without these permissions, users cannot access the components.
 
@@ -251,6 +252,7 @@ After switching from Tasklist V1 to Tasklist V2, user task access restrictions n
 This section describes authorization for domain resources (such as process and decision definitions), not access to UI components or APIs. Users need additional permissions to access specific resources within web components:
 
 - Process-related: Resource type `Process Definition`
+
   - `READ_PROCESS_DEFINITION` to view process models
   - `CREATE_PROCESS_INSTANCE` to start new processes
   - `UPDATE_PROCESS_INSTANCE` to update running instances

docs/components/concepts/access-control/connect-to-identity-provider.md

@@ -19,7 +19,7 @@ Connecting Camunda 8 to an external IdP allows you to:
 
 Self-Managed deployments only support external IdP integration using **OpenID Connect (OIDC)** (for example, Keycloak, Auth0, Okta, EntraID via OIDC).
 
-You can integrate an IdP with both the Identity (for the Orchestration Cluster) and Management Identity (for Web Modeler, Console, and Optimize).
+You can integrate an IdP with both Admin (for the Orchestration Cluster) and Management Identity (for Web Modeler, Console, and Optimize).
 
 - [Connect Orchestration Cluster Admin to an identity provider](/self-managed/components/orchestration-cluster/admin/connect-external-identity-provider.md)
 - [Connect Management Identity to an identity provider](../../../../self-managed/components/management-identity/configuration/connect-to-an-oidc-provider/)

docs/components/concepts/batch-operations.md

@@ -72,7 +72,7 @@ To suspend, resume, or cancel an operation, you only need the relevant batch ope
 The system stores authorization claims with the batch operation and uses them throughout its lifecycle.
 
 :::info
-Read more about [authorizations](/components/concepts/access-control/authorizations.md) and [how to create them in the Identity UI](/components/admin/authorization.md).
+Read more about [authorizations](/components/concepts/access-control/authorizations.md) and [how to create them in the Admin UI](/components/admin/authorization.md).
 :::
 
 ## Next steps

docs/components/concepts/multi-tenancy.md

@@ -24,7 +24,7 @@ Multi-tenancy provides cost efficiency by allowing multiple tenants to share the
 
 ## Efficient administration
 
-Administrators can manage all tenants centrally using [Identity](../admin/tenant.md).
+Administrators can manage all tenants centrally using [Admin](../admin/tenant.md).
 This unified management interface simplifies monitoring, configuration, and maintenance tasks across tenant environments.
 
 :::note
@@ -43,6 +43,7 @@ When a user deploys a process model or starts a process instance, the system val
 For example, assume a user belongs to `Tenant A` but not `Tenant B`:
 
 1. **Deploying a process model**
+
    - If the user deploys to `Tenant A`, the Orchestration Cluster verifies the assignment. If valid, the model is deployed and all related process instances belong to `Tenant A`.
    - If the user deploys to `Tenant B`, the deployment fails because the user lacks access to that tenant.
 

docs/components/console/manage-organization/manage-users.md

@@ -23,7 +23,7 @@ The following roles are additionally available, providing dedicated rights for s
 - **Modeler**: Access to Web Modeler for creating and collaborating on projects, except permissions to deploy and run processes. Read-only access to Console.
 - **Analyst**: Includes Modeler permissions and has full access to Optimize to build process dashboards and reports.
 
-Starting with version 8.8, user access to clusters is managed independently. To control what a user can access, define their authorizations in the cluster's Identity. Learn more [here](/components/admin/authorization.md).
+Starting with version 8.8, user access to clusters is managed independently. To control what a user can access, define their authorizations in the cluster's Admin. Learn more [here](/components/admin/authorization.md).
 
 If cluster authorizations are disabled, the user will have full access to the cluster and its components.
 
@@ -37,7 +37,7 @@ People who do not yet have a Camunda 8 account can also be invited to an organiz
 
 Resource authorizations control a user's access to specific resources. To create, update, or delete a user's resource authorizations, select the user's row in the users table.
 
-As of 8.8, authorizations for Orchestration Cluster applications (Zeebe, Operate, and Tasklist) are managed as part of the Orchestration Cluster and configured in [Identity](/self-managed/components/orchestration-cluster/admin/overview.md).
+As of 8.8, authorizations for Orchestration Cluster applications (Zeebe, Operate, and Tasklist) are managed as part of the Orchestration Cluster and configured in [Admin](/self-managed/components/orchestration-cluster/admin/overview.md).
 
 ### Creation
 

docs/components/operate/overview/access-control.md

@@ -7,7 +7,7 @@ description: "Grant users access to work with Operate."
 If authorization control is enabled for your Orchestration Cluster, users require the following authorizations to work with Operate.
 
 :::note
-You can assign these [in the Identity UI](components/admin/authorization.md#create-an-authorization). See [the introduction to authorizations](components/concepts/access-control/authorizations.md#available-resources) for a list of all available authorizations.
+You can assign these [in the Admin UI](components/admin/authorization.md#create-an-authorization). See [the introduction to authorizations](components/concepts/access-control/authorizations.md#available-resources) for a list of all available authorizations.
 :::
 
 ## Mandatory authorizations

docs/components/tasklist/userguide/access-control.md

@@ -7,7 +7,7 @@ description: "Grant users access to work with Tasklist."
 If authorization control is enabled for your Orchestration Cluster, users require the following authorizations to work with Tasklist.
 
 :::note
-You can assign these [in the Identity UI](components/admin/authorization.md#create-an-authorization). See [the introduction to authorizations](components/concepts/access-control/authorizations.md#available-resources) for a list of all available authorizations.
+You can assign these [in the Admin UI](components/admin/authorization.md#create-an-authorization). See [the introduction to authorizations](components/concepts/access-control/authorizations.md#available-resources) for a list of all available authorizations.
 :::
 
 ## Mandatory authorizations

docs/reference/announcements-release-notes/880/880-announcements.md

@@ -930,7 +930,7 @@ See [Microsoft AKS](/self-managed/deployment/helm/cloud-providers/azure/microsof
 
 With the 8.8 release, Camunda announces the removal of tenant-providing interceptors.
 
-It is superseded by built-in [tenant management](/components/admin/tenant.md).
+It is superseded by built-in [tenant management](/versioned_docs/version-8.8/components/identity/tenant.md).
 
 </div>
 </div>