Skip to main content
Modifying user permissions

Granting or restricting individual user access to areas and features of the CHR

Updated today

🎞️ View video tutorial: Configuring user permissions and roles

When new users are added to the CHR, they receive permissions from their role(s). However, you can modify each user's permissions individually to be distinct from their role permissions.

For example, if only one of your staff creates and manages Qnaires, you can grant just that staff member permission to edit Qnaires, even though it differs from their role's permissions.

📌 Note: Role permissions and user-specific permissions are additive. For example, if a user has permission to create Qnaires from a user-specific permission, but their role is updated to remove the create Qnaires permission, the user can still create Qnaires because of their user-specific permission.

📌 Note: If you are using role-based access control, you must modify a user's permissions via the role. Refer to Managing user roles (role-based access control) for more information.

Steps

1. From the main menu, click Settings > Account information. The User Management window opens.

2. In the Active members list, click Edit (pencil icon) beside the user you want to modify permissions for. The user's settings window opens.

3. Click the Permissions tab. Beside each of the user's permissions, you can see if the permission is a user-specific permission or granted by a role. In this example, the Archive patients permission is a user-specific permission so it's labelled as granted by Individual. The other permissions are granted by the Physician role.

4. Select the checkbox beside a permission you want to grant, or clear the checkbox for any user-specific permissions you want to remove. For more information about each permission, refer to User permissions.

💡 Tip: You can also change the roles a user is in from their Roles tab.

5. When you're done, click Submit.

6. When prompted, enter your CHR password and click Submit.

Updated November 4, 2024

Did this answer your question?