1. Audit 1: Manually Managed Roles
   Identify active and inactive users with manually managed roles that should be reviewed or removed.
2. Audit 2: Manually Managed Person Records
   Identify active and inactive users with manually managed person records, and align them with district integration files.
3. Audit 3: Users with Clevr Login Access
   Identify users who log in directly with a Clevr account (username/password) instead of through Single Sign-On (SSO), and limit exceptions where necessary.

Audit 1: Manually Managed Roles

List A: Active users with a manually managed role

• Status: Active

• Manually Managed Role: Checked

• Role is not: Location, Clevr Admin
  
  

List B: Inactive users with a manually managed role

• Status: Inactive

• Manually Managed Role: Checked

• Role is not: Location, Clevr Admin
  
  

Steps to Review & Clean Up:

1. Click on a user’s name to open their account details.

2. Locate the Roles / Locations card.

3. Click Edit to remove the Manually Managed Role setting.

Note: Removing this setting will also remove the user’s current manually managed Location and Role access. Confirm the change before saving.

Audit 2: Manually Managed Person Records

List A: Active users with a manually managed person record

• Status: Active

• Manually Managed Person: Checked

• Role is not: Location, Clevr Admin
  
  

List B: Inactive users with a manually managed person record

• Status: Inactive

• Manually Managed Person: Checked

• Role is not: Location, Clevr Admin
  
  

Steps to Review & Clean Up:

1. Click on a person’s name in the list to open their details.

2. Click Edit to remove the Manually Managed Person setting.
   
   

Important: Removing this setting will sync the person record with the integration files provided by your District.

• If the person is included in the file, their record will be updated accordingly.

• If the person is not included, their status will be set to Inactive.

Audit 3: Users with Clevr Login Access

This audit identifies users who log in using a Clevr username and password instead of Single Sign-On (SSO).

Recommended Action:

• Review this list carefully.

• Ensure only valid exceptions (e.g., test accounts or specific admin users) are allowed to retain Clevr login credentials.

• Whenever possible, configure all users to authenticate through SSO for security and consistency.

Allow Clevr Login can also be set at the role level.  If checkbox is greyed out and cannot be unchecked, then the setting has been applied to the role and would need to be modified at the Role level (Configuration module)