truenas · micjohnson777 · Jun 23, 2025 · Jun 23, 2025 · Jun 23, 2025 · Sep 25, 2025
@@ -108,13 +108,13 @@ After setting up the truenas_admin user from one of the scenarios documented abo
 {{< trueimage src="/images/SCALE/Login/LoginScreenSCALE.png" alt="TrueNAS Login Screen" id="TrueNAS Login Screen" >}}
 
 To modify user credentials, go to **Credentials > Users**, click anywhere on the user row, then click **Edit**.
-For more information, see [Managing Users]({{< ref "ManageLocalUsersScale" >}}).
+For more information, see [Managing Users]({{< ref "ManageUsers" >}}).
 
 ### Logging In as Root
 If logging in with the root user credentials, enter root as the user and the root password.
 {{< include file="/static/includes/CreateAdminDisableRoot.md" >}}
 
-Follow the directions in [Managing Users]({{< ref "ManageLocalUsersScale" >}}) to create an administration user with all required settings.
+Follow the directions in [Managing Users]({{< ref "ManageUsers" >}}) to create an administration user with all required settings.
 For environments requiring specific configurations, such as non-AD environments or those using LDAP, ensure that your admin user is properly set up to manage all aspects of the system.
 
 ### Creating an Administrator Account at First Log in
@@ -125,7 +125,7 @@ One allows you to log in as root or you can create the administration account.
 
 Select either the **Administrative user** or **Root user (not recommended)** option, then enter the password to use with that user.
 
-If you choose **Root user (not recommended)** as the TrueNAS authentication method, go to the **Credentials > Users** screen and [create the admin account]({{< ref "ManageLocalUsersSCALE" >}}) immediately after you enter the UI.
+If you choose **Root user (not recommended)** as the TrueNAS authentication method, go to the **Credentials > Users** screen and [create the admin account]({{< ref "ManageUsers" >}}) immediately after you enter the UI.
 Enter the admin user name and password, make sure the password is enabled, and click **Save**.
 After setting up the admin user, click on the root user and then click **Edit**. Disable the root user password and then click **Save**.
 This brings the system into compliance with FIPS system security-hardening standards.

@@ -42,7 +42,7 @@ To add non-SMB share users or edit users, go to **Credentials > Users** to add o
 Click **Add** to create a new or as many new user accounts as you need.
 
 Enter the values in each required field, verify **SMB User** is selected for SMB share users, then click **Save**.
-For more information on the fields and adding users, see [Creating User Accounts]({{< ref "ManageLocalUsersScale" >}}).
+For more information on the fields and adding users, see [Creating User Accounts]({{< ref "ManageUsers" >}}).
 
 By default, all new users are members of a built-in group called **builtin_users**.
 You can use a group to grant access to all users on the server or add more groups to fine-tune permissions for large numbers of users.

@@ -38,7 +38,7 @@ Adminstrator passwords can be changed on the **Edit User** screen or, if current
 
 ## Configuring Administrative Privileges
 
-[Create a new administrator]({{< ref "managelocalusersscale/#creating-an-administrator-user-account" >}}) account or select an existing account to grant administrative privileges.
+[Create a new administrator]({{< ref "manageusers/#creating-an-administrator-user-account" >}}) account or select an existing account to grant administrative privileges.
 Note the primary group assigned to that user.
 
 {{< include file="/static/includes/AddAdminGroup.md" >}}
@@ -52,7 +52,7 @@ Administrative users who need to execute root-level commands to complete a task
 For best security, enable only the required commands to perform the task and require password authentication, unless the task or app prevents it.
 Disable sudo permissions when the task completes and you no longer need them.
 
-**Allowed sudo commands**, **Allow all sudo commands**, **Allowed sudo commands with no password**, and **Allow all sudo commands with no password** grant limited root-like permissions using the sudo command.
+**Allowed sudo commands**, **Allow all sudo commands**, **Allowed sudo commands with no password**, and **Allow all sudo commands with no password**, on the **Add Group** and **Edit Group** screens, grant limited root-like permissions using the sudo command.
 Use **Allowed sudo commands** or **Allowed sudo commands with no password** to list specific sudo commands to allow.
 Enter each command as an absolute path to the ELF (Executable and Linkable Format) executable file, for example, */usr/bin/nano*.
 <file>/usr/bin/</file> is the default location for commands.
@@ -93,6 +93,8 @@ To enable SSH access to the system as an admin user (or root user), you must fir
 
 Now you must verify the user configuration options to allow SSH access.
 
+### Using the Root User in SSH 
+
 If you want to SSH into the system as the root: 
 
 1. Go to **Credentials > Users** and click the root user, then click <span class="iconify" data-icon="mdi:pencil"></span> (**Edit**).
@@ -101,6 +103,8 @@ If you want to SSH into the system as the root:
 
 3. Click **Save**.
 
+### Allowing an Admin User to Enter Commands in SSH
+
 To allow an admin user to issue commands in an SSH session:
 
 1. Go to **Credentials > Users**, click the admin user, then click <span class="iconify" data-icon="mdi:pencil"></span> (**Edit**).

@@ -11,7 +11,7 @@ keywords:
 ---
 
 TrueNAS offers groups as an efficient way to manage permissions for many similar user accounts.
-See [Users]({{< ref "ManageLocalUsersSCALE" >}}) for managing users.
+See [Users]({{< ref "ManageUsers" >}}) for managing users.
 The interface lets you manage UNIX-style groups.
 If the network uses a directory service, import the existing account information using the instructions in [Active Directory]({{< ref "/SCALE/SCALEUIReference/Credentials/DirectoryServices" >}}).