Changes from demo session info

Author: mpfuster

advocacy_docs/supported-open-source/warehousepg/wem/get-started.mdx

@@ -45,12 +45,12 @@ Use the following guide to locate specific tools and their corresponding documen
 | Logs | [Auditing system logs](monitoring/logs/) |
 | Monitoring | [Validating database responsiveness](monitoring/monitoring/) |
 | Alerts | [Managing alerts](monitoring/alerts/) |
-| User Management | [Provisioning user accounts](system-access/user-management/)
+| Management | [Provisioning user accounts](system-access/management/)
 
 
 ## Understanding user roles and permissions
 
-WEM utilizes Role-Based Access Control (RBAC). After the initial bootstrap, all user management and password updates are handled exclusively via the User Management panel in the UI. A user's assigned role determines which panels and actions are visible.
+WEM utilizes Role-Based Access Control (RBAC). After the initial bootstrap, all user management and password updates are handled exclusively via the **Management** panel in the UI. A user's assigned role determines which panels and actions are visible.
 
 | Role | Description | Access scope |
 | :--- | :--- | :--- |
@@ -94,7 +94,7 @@ Once you have installed WEM, you can fine-tune how WEM connects to your cluster
 1. **Method 1: Use the WEM settings tab**
 
     Administrators can modify most operational parameters directly through the browser:
-    1. Navigate to **User Management** > **Settings**.
+    1. Navigate to **Management** > **Settings**.
     1. Update fields such as **Prometheus URL** or **Backup History Database Path**.
     1. Save to apply changes immediately.
 

advocacy_docs/supported-open-source/warehousepg/wem/monitoring/monitoring.mdx

@@ -9,12 +9,12 @@ The **Monitoring** panel on the left sidebar provides proactive verification of
 
 ### Performing proactive health checks: Canary checks
 
-Canary checks are recurring, automated scripts that simulate real-world operations to verify the end-to-end integrity of the system. You can configure these tests on the [User Management panel](../system-access/user-management).
+Canary checks are recurring, automated scripts that simulate real-world operations to verify the end-to-end integrity of the system. You can configure these tests on the [Management panel](../system-access/management).
 
 Use the **Canary Checks** tab to verify that the database can successfully execute core operations.
 - **Assess overall probe health:** Review the header metrics to get an instant snapshot of system integrity. Compare the **Successful** count against the **Total Checks** count to identify if a specific subset of your monitoring is failing.
 - **Verify scheduler activity:** Check the status of the scheduler to ensure it is running. This confirms that the WarehousePG Enterprise Manager (WEM) engine is actively triggering your background probes. If the scheduler is stopped, your health data will become stale and you will lose proactive visibility.
-- **Run health checks on demand:** Trigger an immediate execution of any check in the list to verify a fix or test real-time connectivity. While you must go to the [User Management panel](../system-access/user-management) to create or edit a check, the **Monitoring** panel allows you to run and stop them at any time to get an instant status update.
+- **Run health checks on demand:** Trigger an immediate execution of any check in the list to verify a fix or test real-time connectivity. While you must go to the [Management panel](../system-access/management) to create or edit a check, the **Monitoring** panel allows you to run and stop them at any time to get an instant status update.
 - **Benchmark execution speed:** Monitor the **Average Duration** metric to establish a baseline for expected responsiveness. A sudden spike in this metric, even if checks are still successful, serves as an early warning of resource saturation or network latency.
 - **Investigate specific check failures:** Audit the **Health Checks** table to isolate the root cause of a failure. By checking which specific probe is non-passing, you can determine if the issue is a total service outage or a localized subsystem failure.
 

advocacy_docs/supported-open-source/warehousepg/wem/overview/known_issues.mdx

@@ -8,12 +8,14 @@ These are the currently known issues and limitations identified in the Warehouse
 
 ### Deployment & infrastructure
 
+- Each WEM deployment is designed to manage and monitor only one WarehousePG (WHPG) cluster. Managing multiple clusters requires separate, dedicated WEM installations for each.
 - WEM cannot be installed on Red Hat Enterprise Linux 7. Note that this restriction applies only to the host running the WEM application; WEM is fully capable of monitoring WHPG clusters running on RHEL 7 nodes.
 [PTT-703]: #
 - Running WHPG and WEM on the same host using the same database is not supported. WEM writes its application state into the `observability` database; sharing this environment can lead to configuration conflicts and upgrade complexity.
 [PTT-714]: # 
 - The maximum Postgres connection pool size is currently hardcoded to 5. There is currently no mechanism to scale or configure this limit via environment variables.
 
+
 ### Backup management
 
 [PTT-723]: #

advocacy_docs/supported-open-source/warehousepg/wem/system-access/index.mdx

@@ -3,13 +3,13 @@ title: Managing system access
 navTitle: Managing system access
 description: Use WarehousePG Enterprise Manager to establish safety protocols, manage user credentials, and enforce role-based access controls.
 navigation:
-- user-management
+- management
 - access-management
 ---
 
 Establish safety protocols and manage access to sensitive data to protect the integrity of the cluster.
 
 
-- [Provisioning user accounts:](user-management) The **User Management** panel allows you to create database roles and manage credentials through a centralized interface.
+- [Provisioning user accounts:](management) The **Management** panel allows you to create database roles and manage credentials through a centralized interface.
 
 - [Defining access policies:](access-management) Use the **Access Management** panel to enforce role-based permissions and security controls at the schema and table level.

…pg/wem/system-access/user-management.mdx …housepg/wem/system-access/management.mdxadvocacy_docs/supported-open-source/warehousepg/wem/system-access/user-management.mdx renamed to advocacy_docs/supported-open-source/warehousepg/wem/system-access/management.mdx advocacy_docs/supported-open-source/warehousepg/wem/system-access/user-management.mdx renamed to advocacy_docs/supported-open-source/warehousepg/wem/system-access/management.mdx

@@ -1,11 +1,11 @@
 ---
 title: Provisioning user accounts
 navTitle: Provisioning user accounts
-description: Use the User Management panel to manage user accounts, define role-based access controls, and configure system-wide settings for WarehousePG Enterprise Manager.
+description: Use the Management panel to manage user accounts, define role-based access controls, and configure system-wide settings for WarehousePG Enterprise Manager.
 deepToC: true
 ---
 
-The **User Management** panel on the left sidebar is the central administrative hub for WarehousePG Enterprise Manager (WEM). Use these actions to oversee account security, define permission tiers, and configure system-wide integration settings.
+The **Management** panel on the left sidebar is the central administrative hub for WarehousePG Enterprise Manager (WEM). Use these actions to oversee account security, define permission tiers, and configure system-wide integration settings.
 
 !!! Important
     Access to this panel is restricted to users with the **Admin** role privilege.