camunda · leiicamundi · Mar 26, 2026 · Mar 27, 2026 · Mar 31, 2026 · Apr 6, 2026
diff --git a/docs/self-managed/concepts/multi-region/img/dual-region.jpg b/docs/self-managed/concepts/multi-region/img/dual-region.jpg
diff --git a/docs/self-managed/deployment/containers/cloud-providers/amazon/aws-ecs.md b/docs/self-managed/deployment/containers/cloud-providers/amazon/aws-ecs.md
@@ -253,7 +253,7 @@ The base terraform documentation for this module can be found [alongside the rep
 `camunda.tf` contains the module invocations with an example base configuration for the Orchestration Cluster and Connectors:
 
 - Aurora PostgreSQL configuration with the [AWS JDBC Wrapper](https://github.com/aws/aws-advanced-jdbc-wrapper) that comes as part of the Camunda distribution
-- Basic authentication Identity setup
+- Basic authentication Admin setup
   - Admin user with random password
   - Connectors user with random password configured and pre-configured for Connectors to consume to connect to the Orchestration Cluster
 

diff --git a/docs/self-managed/deployment/helm/install/production/img/architecture.png b/docs/self-managed/deployment/helm/install/production/img/architecture.png
diff --git a/docs/self-managed/deployment/helm/operational-tasks/dual-region-ops.md b/docs/self-managed/deployment/helm/operational-tasks/dual-region-ops.md
@@ -86,7 +86,7 @@ For the failback procedure, the recreated region must not include any active Cam
 
 :::info
 
-In the following examples, direct API calls are used because authentication methods may vary depending on your embedded Identity configuration.
+In the following examples, direct API calls are used because authentication methods may vary depending on your Admin configuration.
 
 The **Management API** (default port `9600`) is not secured by default.
 
@@ -145,7 +145,7 @@ echo "You have lost $CLUSTER_RECREATED, $CLUSTER_SURVIVING is still alive"
   </TabItem>
 </Tabs>
 
-The `camunda-zeebe-x` pod represents the new architecture that contains the Orchestration Cluster and its components. It includes the former Zeebe Gateway, Operate, Tasklist, the new embedded Identity, and the new Camunda Exporter.
+The `camunda-zeebe-x` pod represents the new architecture that contains the Orchestration Cluster and its components. It includes the former Zeebe Gateway, Operate, Tasklist, the new embedded Admin, and the new Camunda Exporter.
 
 <div style={{textAlign: 'center'}}>
   <img src={OC} alt="Orchestration Cluster" style={{border: 'none', width: '60%', transform: 'scale(1.3)'}} />

diff --git a/docs/self-managed/deployment/helm/operational-tasks/img/10.jpg b/docs/self-managed/deployment/helm/operational-tasks/img/10.jpg
diff --git a/docs/self-managed/deployment/helm/operational-tasks/img/11.jpg b/docs/self-managed/deployment/helm/operational-tasks/img/11.jpg
diff --git a/docs/self-managed/deployment/helm/operational-tasks/img/12.jpg b/docs/self-managed/deployment/helm/operational-tasks/img/12.jpg
diff --git a/docs/self-managed/deployment/helm/operational-tasks/img/13.jpg b/docs/self-managed/deployment/helm/operational-tasks/img/13.jpg
diff --git a/docs/self-managed/deployment/helm/operational-tasks/img/14.jpg b/docs/self-managed/deployment/helm/operational-tasks/img/14.jpg
diff --git a/docs/self-managed/deployment/helm/operational-tasks/img/15.jpg b/docs/self-managed/deployment/helm/operational-tasks/img/15.jpg
diff --git a/docs/self-managed/deployment/helm/operational-tasks/img/4.jpg b/docs/self-managed/deployment/helm/operational-tasks/img/4.jpg
diff --git a/docs/self-managed/deployment/helm/operational-tasks/img/5.jpg b/docs/self-managed/deployment/helm/operational-tasks/img/5.jpg
diff --git a/docs/self-managed/deployment/helm/operational-tasks/img/6.jpg b/docs/self-managed/deployment/helm/operational-tasks/img/6.jpg
diff --git a/docs/self-managed/deployment/helm/operational-tasks/img/8.jpg b/docs/self-managed/deployment/helm/operational-tasks/img/8.jpg
diff --git a/docs/self-managed/deployment/helm/operational-tasks/img/9.jpg b/docs/self-managed/deployment/helm/operational-tasks/img/9.jpg
diff --git a/docs/self-managed/deployment/helm/operational-tasks/img/oc-pod.jpg b/docs/self-managed/deployment/helm/operational-tasks/img/oc-pod.jpg
diff --git a/...eployment/manual/assets/manual-single.png → ...eployment/manual/assets/manual-single.png b/...eployment/manual/assets/manual-single.png → ...eployment/manual/assets/manual-single.png
diff --git a/docs/self-managed/deployment/manual/install.md b/docs/self-managed/deployment/manual/install.md
@@ -118,7 +118,7 @@ Set the secondary storage type value to `elasticsearch` or `opensearch` for this
 If your security settings require authentication for the secondary storage, configure both `username` and `password`.
 Omit these fields if authentication is not required.
 
-The following configuration defines how the Orchestration Cluster connects to document-store secondary storage (Elasticsearch or OpenSearch). This applies to the included Operate, Tasklist, Identity, and Camunda Exporter.
+The following configuration defines how the Orchestration Cluster connects to document-store secondary storage (Elasticsearch or OpenSearch). This applies to the included Operate, Tasklist, Admin, and Camunda Exporter.
 
 For detailed configuration options, see the [Orchestration Cluster configuration](/self-managed/components/orchestration-cluster/core-settings/overview.md)
 
@@ -278,7 +278,7 @@ Once you've downloaded the Orchestration Cluster distribution, extract it into a
 3. Update the configuration in `config/application.yaml`, or export the environment variables.
 4. Navigate to `bin` folder.
 5. Run `camunda.sh` (Linux/macOS) or `camunda.bat` (Windows).
-6. Open [http://localhost:8080](http://localhost:8080). On first access, you’ll be asked to create an admin user unless [Identity](/self-managed/components/orchestration-cluster/core-settings/configuration/properties.md) is configured with OIDC or a similar option.
+6. Open [http://localhost:8080](http://localhost:8080). On first access, you'll be asked to create an admin user unless [Admin](/self-managed/components/orchestration-cluster/core-settings/configuration/properties.md) is configured with OIDC or a similar option.
 
 :::note
 Camunda 8 components without a valid license may display **Non-Production License** in the navigation bar and issue warnings in the logs. These warnings don’t affect startup or functionality, except that Web Modeler is limited to five users. To obtain a license, visit the [Camunda Enterprise page](https://camunda.com/platform/camunda-platform-enterprise-contact/).

diff --git a/docs/self-managed/reference-architecture/img/k8s-cluster-view-managing.jpg b/docs/self-managed/reference-architecture/img/k8s-cluster-view-managing.jpg
diff --git a/docs/self-managed/reference-architecture/img/k8s-cluster-view-orchestration.jpg b/docs/self-managed/reference-architecture/img/k8s-cluster-view-orchestration.jpg
diff --git a/docs/self-managed/reference-architecture/img/management-cluster.jpg b/docs/self-managed/reference-architecture/img/management-cluster.jpg
diff --git a/docs/self-managed/reference-architecture/img/manual-ha.jpg b/docs/self-managed/reference-architecture/img/manual-ha.jpg
diff --git a/docs/self-managed/reference-architecture/img/manual-single.jpg b/docs/self-managed/reference-architecture/img/manual-single.jpg
diff --git a/docs/self-managed/reference-architecture/img/orchestration-cluster.jpg b/docs/self-managed/reference-architecture/img/orchestration-cluster.jpg