[Doc] New native nav

documentation/docs/admin/manage-users/add_users.md

@@ -4,14 +4,10 @@ Adding users with basic authentication (username and password stored in PMM) fro
 
 If your organization uses LDAP, OAuth, SAML, or other authentication methods, users are managed through your external authentication system. See [available authentication methods](edit_users.md#available-authentication-methods) for more information.
 
-!!! note "Authentication methods"
-
-![!](../../images/PMM-manage-users.png)
-
 To add a new user in PMM:
 {.power-number}
 
-1. On the **Users** tab, click **New user**.
+1. Go to **Users and access** tab, click **New user**.
 2. On the **Add new user** dialog box, enter the following:
     - **Name** - Full name of the user
     - **Email** - Email address or username (if this is an existing Grafana user)
@@ -20,6 +16,8 @@ To add a new user in PMM:
 
 3. Click **Create user**.
 
+![!](../../images/PMM-manage-users.png)
+
 The new user can now log in to PMM using the username and password you created.
 
 ## Assign user roles

documentation/docs/admin/manage-users/delete_users.md

@@ -3,6 +3,6 @@
 You can delete a user in PMM as follows:
 {.power-number}
 
-1. Go to **PMM Administration > Users and access > Users** tab
+1. Go to **Users and access > Users** tab.
 2. Click the **Edit user** icon next to the user you want to delete.
 3. Click **Delete user**.

documentation/docs/admin/manage-users/edit_users.md

@@ -10,11 +10,13 @@ You can edit users by changing the information or settings for an individual use
 You can grant or revoke admin access to a user as follows:
 {.power-number}
 
-1. On the **Users** tab, click the user account you want to edit.
+1. Go to **Users and access**.
 
-2. To grant or revoke the privileges, click the user. User information dialog box opens.
+2. Locate the user account you want to update and click the Edit (pencil) icon. 
 
-3. In the **Permissions** section, click **Change** and then select **Yes/No**, depending on whether you want to provide admin access or not.
+3. In the **User information** dialog, scroll to **Permissions** section and click **Change**
+
+4. Choose **Yes/No**, depending on whether you want to provide admin access or not.
 
 4. Click **Change**.
 
@@ -27,13 +29,15 @@ You can change the organization role assigned to your user account.
 To change the role:
 {.power-number}
 
-1. On the **Users** tab, click the user for whom you want to change the role.
+1. On the **Users and access**, click the user for whom you want to change the role.
+
+2. Locate the user account you want to update and click the Edit (pencil) icon. 
 
-2. In the **Organizations** section, click **Change role**.
+3. In the **Organizations** section, click **Change role**.
 
-3. Select the role from the drop-down and click **Save**.
+4. Select the role from the drop-down and click **Save**.
 
-The following are the privileges for the various *roles*:
+Here are the privileges for the various *roles*:
 
 - **Admin** - Managing data sources, teams, and users within an organization
 

documentation/docs/admin/manage-users/index.md

@@ -1,12 +1,28 @@
-# About user management in PMM
+# User management in PMM
 
-A user refers to any individual who can log in to PMM. Each user is assigned a specific role that is associated with permissions. Permissions determine the tasks a user can perform in the system. For instance, the Admin role confers permissions that allow an authorized administrator to create and delete user profiles. 
+User management controls who can access PMM and what actions they can perform. Every user who logs into PMM has a specific role assigned, which determines their permissions.
 
-The following topics are covered as part of access control:
+User management defines who can access PMM and what actions they are allowed to perform:
+- **Users**: Individual accounts that can log in to PMM with unique credentials.
 
-- [Add users](add_users.md)
-- [Edit users](edit_users.md)
-- [Delete users](delete_users.md)
+- **Roles**: Predefined permission sets that determine what users can do. The Admin role, for example, allows creating and deleting user profiles, while other roles may have more limited permissions.
+
+- **Permissions**: Specific actions or tasks that a role authorizes. Permissions are role-based—users inherit all permissions associated with their assigned role.
+
+## User management tasks
+
+This section covers the following user management operations:
+
+- [Add users](add_users.md): Create new user accounts and assign roles
+- [Edit users](edit_users.md): Modify user profiles and change assigned roles
+- [Delete users](delete_users.md): Remove user accounts from the system
+
+!!! note
+    Only users with the Admin role can perform user management tasks.
+
+## Understanding roles and permissions
+
+User capabilities depend entirely on the role assigned to them. For a comprehensive overview of available roles and their associated permissions, see [Access control in PMM](../roles/access-control/intro.md).
 
 ## Next steps
 

documentation/docs/admin/roles/access-control/assign_roles.md

@@ -3,8 +3,8 @@
 To assign access roles to users:
 {.power-number}
 
-1. From the [main menu](../../../reference/ui/ui_components.md), go to **PMM Configuration > Settings > Advanced Settings** and enable the **Access Roles** option.
-2. Go to **Administration > Users and access > Users**.
+1. From the [main menu](../../../reference/ui/ui_components.md), go to **Configuration > Settings > Advanced Settings** and enable the **Access control** option.
+2. Go to **Users and access > Users**.
 3. Click on the user you want to assign roles to.
 4. From the **Roles** drop-down select the appropriate roles.
 5. Verify the assigned roles appear in the **Access Role** column.

documentation/docs/admin/roles/access-control/create_roles.md

@@ -13,13 +13,13 @@ Roles are essential components of PMM's access control system. They allow you to
 To create access roles in PMM:
 {.power-number}
 
-1. From the [main menu](../../../reference/ui/ui_components.md), go to **PMM Configuration > Settings > Advanced Settings** and enable the **Access control** option.
-2. Go to **Administration > Users and access > Access Roles**.
+1. From the [main menu](../../../reference/ui/ui_components.md), go to **Configuration > Settings > Advanced Settings** and enable the **Access control** option.
+2. Go to **Users and access > Access Roles**.
 
     ![PMM Access Control - Create role](../../../images/lbac/PMM_access_control_create_role.png)
 
 3. Click **Create**.
-4. On the **Create role** page, enter the Role name and Role description.
+4. On the **Create role** page, enter a role name and description.
 5. Configure metrics access by setting label selectors:
     - select a Label (e.g., "service_name", "environment")
     - choose an Operator (e.g., "=", "!=", "=~")
@@ -29,6 +29,6 @@ To create access roles in PMM:
 
     For information on how the Prometheus selectors work, see [Prometheus selectors](https://prometheus.io/docs/prometheus/latest/querying/basics/#time-series-selectors).
 
-6. Review your selections, then click **Create** to finalize the role.
+6. Review your selections, then click **Create role** to finish creating the role.
 
 

documentation/docs/admin/roles/access-control/enable_access_control.md

@@ -37,8 +37,8 @@ Choose your preferred method to enable this feature:
     {.power-number}
 
     1. Log in to PMM with an administrator account.
-    2. From the main menu, go to **PMM Configuration > Settings > Advanced Settings > Access Control**.
-    3. Toggle the <i class="uil uil-toggle-off"></i> toggle.
+    2. From the main menu, go to **Configuration > Settings > Advanced Settings**.
+    3. Toggle the <i class="uil uil-toggle-off"></i>  **Access Control** toggle.
     4. Click **Apply changes** to save your settings.
 
 ## After enabling access control

documentation/docs/admin/roles/access-control/intro.md

@@ -36,10 +36,10 @@ Here's how LBAC works:
 To implement label-based access control in PMM:
 {.power-number}
 
-1. [Enable access control](enable_access_control.md) in your PMM settings
-2. Learn about the [labels available for filtering](labels.md)
-3. [Create access roles](create_roles.md) based on your organizational needs
-4. Review common [use cases and examples](use_cases.md) for inspiration
+1. [Enable access control](enable_access_control.md) in your PMM settings.
+2. Learn about the [labels available for filtering](labels.md).
+3. [Create access roles](create_roles.md) based on your organizational needs.
+4. Review common [use cases and examples](use_cases.md) for inspiration.
 
 !!! tip "Best practice"
     Start with broader access controls and refine them over time as you understand your organization's specific needs. Test LBAC behavior in both dashboards and QAN to ensure proper access control.

documentation/docs/admin/roles/access-control/labels.md

@@ -37,16 +37,13 @@ You can add standard or custom labels while adding a service to monitoring in PM
     To set the labels via the user interface:
     {.power-number}
 
-    1. From the **Main** menu, go to **PMM Configuration > PMM Services > Add Service**.
+    1. From the main menu, go to **Inventory > Add Service**.
 
     2. Select the service you want to monitor.
 
     3. Complete the required connection details. 
 
-    4. Enter standard labels via the input section `Labels`.
-
-    5. Enter custom labels via section `Custom labels`.
-
+    4. In the **Labels** section, enter standard and custom labels.
     ![PMM Inventory - Add Service](../../../images/lbac/PMM_access_control_add_labels_services.png)
 
 === "Using pmm-admin"
@@ -58,7 +55,7 @@ PMM allows modifying certain standard labels after a service is created:
 
 - `environment`
 - `cluster`
--  `replication_set`
+- `replication_set`
 - `external_group`
 
 For other standard labels that cannot be modified directly, you must remove the service and re-add it with the desired labels.

documentation/docs/admin/roles/access-control/manage_roles.md

@@ -7,39 +7,40 @@ You can manage roles in PMM by editing or deleting a role.
 To edit access roles:
 {.power-number}
 
-1. From [main menu](../../../reference/ui/ui_components.md), go to **PMM Configuration > Settings > Advanced Settings** and enable the **Access Roles** option.
+1. From the [main menu](../../../reference/ui/ui_components.md), go to **Configuration > Settings > Advanced Settings** then enable **Access control**.
 
-2. Go to **Administration > Users and access > Access Roles**.
+2. Go to **Users and access > Access roles**.
 
-3. On the role you want to edit, click the **ellipsis (three vertical dots) > edit role** in the **Options** column. The **Edit** role page opens.
+3. In the **Options** column, click the ellipsis (three vertical dots) next to the role you want to edit, then select **Edit** to open the **Edit role** page:
 
     ![PMM Access Control - Edit role](../../../images/lbac/PMM_access_control_edit_role.png)
 
 4. Make the required changes to the role.
 
-5. Click **Save Changes**.
+5. Click **Save changes**.
 
 ## Set a role as default
 
-When a user signs in to PMM for the first time and the user has no role assigned, the user is automatically assigned the *Default* role. For administrators, the default role provides a convenient way to configure default permissions for new users.
+When a user signs in to PMM for the first time and the user has no role assigned, the user is automatically assigned the **Default** role. For administrators, the default role provides a convenient way to configure default permissions for new users.
 
 To set a role as default, do the following:
 {.power-number}
 
-1. From [main menu](../../../reference/ui/ui_components.md), go to **PMM Configuration > Settings > Advanced Settings** and enable the **Access Roles** option.
+1. From [main menu](../../../reference/ui/ui_components.md), go to **Configuration > Settings > Advanced Settings** and enable the **Access control** option.
 
-2. Go to **Administration > Users and access > Access Roles**.
+2. Go to **Users and access > Access roles**.
 
-3. On the role you want to set as default, click the **ellipsis (three vertical dots) → set as default** in the **Options** column.
+3. On the **Options** column, click the ellipsis (three vertical dots) next to the role you want to set, then select **Set as default**.
 
 
 ## Remove roles
 
 To remove access roles, do the following:
 {.power-number}
 
-1. From [main menu](../../../reference/ui/ui_components.md), go to **PMM Configuration > Settings > Advanced Settings** and enable the **Access Roles** option.
-
-2. On the role you want to remove, click the **ellipsis (three vertical dots) > Delete** in the **Options** column. Delete role pop-up opens.
+1. From [main menu](../../../reference/ui/ui_components.md), go to **Configuration > Settings > Advanced Settings** and enable the **Access control** option.
 
-3. Click **Confirm** and delete the role.
+2. Go to **Users and access > Access roles**.
+
+3. In the **Options** column, click the ellipsis (three vertical dots) next to the role you want to remove, then select **Delete**. 
+4. Click **Confirm and delete role**.

documentation/docs/api/authentication.md

@@ -35,15 +35,14 @@ PMM uses Grafana service account tokens for authentication. These tokens are ran
 Here's how to generate a service account token:
 {.power-number}
 
-1. Log into PMM.
-2. From the side menu, click **Administration > Users and access**.
-3. Click on the **Service accounts** card.
+1. Log in to PMM.
+2. From the side menu, click **Users and access > Service accounts**.
 4. Click **Add service account**. Specify a unique name for your service account, select a role from the drop-down menu, and click **Create** to display your newly created service account.
 5. Click **Add service account token**.
 6. In the pop-up dialog, provide a name for the new service token, or leave the field empty to generate an automatic name.
 7. Optionally, set an expiration date for the service account token. PMM cannot automatically rotate expired tokens, which means and you will need to manually [update the PMM-agent configuration file](../use/commands/pmm-agent.md) with a new service account token. Permanent tokens, on the other hand, remain valid indefinitely unless specifically revoked.
-8. Click **Generate Token**. A pop-up window will display the new token, which usually has a *glsa_* prefix.
-9. Copy your service token to the clipboard and store it securely.
+8. Click **Generate token**. A pop-up window will display the new token, which usually has a *glsa_* prefix.
+9. Click **Copy your service token to the clipboard** and store it securely.
 Now you can use your new service token for authentication in PMM API calls or in your [pmm-agent configuration](../use/commands/pmm-agent.md).
 
 ## Authenticate

documentation/docs/configure-pmm/percona_platform/account-info.md

@@ -11,15 +11,5 @@
     **Need help?** Contact [Percona Support](https://www.percona.com/services/support) for migration assistance.
 
 
-When you connect your PMM instances to Percona Platform with a customer account, PMM reveals two new tabs on the main menu, where you can check all the information available for your customer accounts: **Entitlements** and **Support tickets**:
+When you connect your PMM instances to Percona Platform with a customer account, PMM reveals two new tabs on the main menu, where you can check all the information available for your customer accounts: **Entitlements** and **Support tickets**.
 
-![CustomerTickets](../../images/CustomerTickets.png)
-
-![CustomerEntitlements](../../images/CustomerEntitlements.png)
-
-
-When you connect your PMM instances to Percona Platform with a customer account, PMM  reveals two new tabs on the main menu, where you can check all the information available for your customer accounts:  **Entitlements** and **Support tickets**:
-
-![CustomerTickets](../../images/CustomerTickets.png)
-
-![CustomerEntitlements](../../images/CustomerEntitlements.png)

documentation/docs/configure-pmm/percona_platform/check_percona_platform.md

@@ -19,7 +19,7 @@ For security reasons, access tokens expire after 30 minutes. Make sure to paste
 To connect your PMM Server to Percona Platform:
 {.power-number}
 
-1. In PMM, go to **PMM Configuration > Settings > Percona Platform** tab to fill in the **Connect PMM to Percona Portal** form: ![Percona_Platform_Login](../../images/PMM_Settings_Percona_Platform_Login.png)
+1. In PMM, go to **Configuration > Settings > Percona Platform** tab to fill in the **Connect PMM to Percona Portal** form: ![Percona_Platform_Login](../../images/PMM_Settings_Percona_Platform_Login.png)
 
 2. The **PMM Server ID** field is automatically populated with the ID identified for your PMM instance. Enter the name of your PMM instance and click **Get token** to go to Percona Platform Portal and generate your access token.
 3. Log into Percona Platform using your Percona Account (if you don't have an active current session).

documentation/docs/discover-pmm/why-pmm.md

@@ -2,13 +2,13 @@
 
 Percona Monitoring and Management (PMM) delivers:
 
-* **Comprehensive monitoring** of MySQL, MariaDB, MongoDB, and PostgreSQL databases.
-* **Built-in advisors and alerts** that work offline with no subscription required. Proactively detect security threats, performance issues, and configuration problems.
-* **Query performance insights** to identify and optimize slow queries for improved system efficiency.
+* **Comprehensive monitoring** of MySQL, MariaDB, MongoDB, and PostgreSQL databases
+* **Built-in advisors and alerts** that work offline with no subscription required. Proactively detect security threats, performance issues, and configuration problems
+* **Query performance insights** to identify and optimize slow queries for improved system efficiency
 * **Database-specific features** tailored for deep monitoring of different database engines
-* **Built-in security** with SSL encryption and robust authentication.
-* **Flexible customization** through custom dashboards, metrics, and exporters.
+* **Built-in security** with SSL encryption and robust authentication
+* **Flexible customization** through custom dashboards, metrics, and exporters
 * **Centralized management** of multiple database instances across different hosts
-* **Active community support** with regular updates and improvements.
+* **Active community support** with regular updates and improvements
 
-![!PMM Home Screen](../images/Home_screen.jpg)
+    ![!PMM Home Screen](../images/Home_screen.png)

documentation/docs/images/lbac/PMM_access_control_select_role

@@ -0,0 +1,12 @@
+# Assign access roles to users
+
+To assign access roles to users:
+{.power-number}
+
+1. From the [main menu](../../../reference/ui/ui_components.md), go to **Configuration > Settings > Advanced Settings** and enable the **Access control** option.
+2. Go to **Users and access > Users**.
+3. Click on the user you want to assign roles to.
+4. From the **Access Role** drop-down select the appropriate roles.
+5. Verify the assigned roles appear in the **Access Role** column.
+
+![PMM Access Control - Assign role](../../images/lbac/PMM_access_control_select_role.png)

documentation/docs/install-pmm/install-pmm-client/connect-database/mysql/mysql.md

@@ -666,7 +666,6 @@ Once the service is confirmed as active, verify that metrics are being properly
 - [Running custom MySQL queries in PMM][BLOG_CUSTOM_QUERIES_MYSQL]
 
 [DASH_MYSQLUSERDETAILS]: ../../../../reference//dashboards/dashboard-mysql-user-details.md
-[DASH_PXCGALERACLUSTER]: ../../../../reference/dashboards/dashboard-pxc-galera-cluster-summary.md
 [LOGROTATE]: https://linux.die.net/man/8/logrotate
 [PERCONA_SERVER_MYSQL]: https://www.percona.com/software/mysql-database/percona-server
 [PERCONA_XTRADB_CLUSTER]: https://www.percona.com/software/mysql-database/percona-xtradb-cluster

documentation/docs/install-pmm/install-pmm-server/deployment-options/aws/configure_aws.md

@@ -81,7 +81,7 @@ sudo ufw --force enable
 After the initial setup, create additional user accounts in PMM for your team members. Follow the principle of least privilege when assigning user roles.
 {.power-number}
 
-1. Go to **Administration > Users and access > Users**.
+1. Go to **Users and access > Users**.
 2. Click **New user** and configure the user with an appropriate role:
 
     - **Admin**: Full system access

documentation/docs/install-pmm/install-pmm-server/deployment-options/aws/deploy_aws.md

@@ -65,15 +65,13 @@ Once your instance status shows "Running" and passes all status checks in the AW
 
 3. Change the default credentials then use the new ones to log in to the PMM Server home page. You will reuse these credentials when configuring PMM Clients on other hosts.
 
-    ![PMM Home Dashboard](../../../../images/PMM_Home_Dashboard.png)
-
 ## Configure PMM Server and IP settings
 After initial access, configure your PMM Server's security groups and IP addressing.
 
 ### SSH access
 For SSH access instructions, see [Connecting to Your Linux Instance Using SSH](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html).
 
-Replace the user name `ec2-user` with `admin`. You can also add SSH keys later through the **PMM Configuration > Settings > SSH Key** page.
+Replace the user name `ec2-user` with `admin`. You can also add SSH keys later through the **Configuration > Settings > SSH Key** page.
 
 ## Next steps