Admin: user management in Cirrus - start here

Cirrus Assessment Support Team -

User management in Cirrus

Adding users, removing users and setting the correct roles for your users is very easy in the Cirrus Platform:

Manual administration of users

To manually add, edit or remove users go to Admin > Users where you can select which action to take:


  1. Search - use this box to search name, username or userID
  2. Search hierarchy - this opens a modal window to search for groups of users
  3. Add new user, Delete and Import users buttons
  4. Click on the row of any user to open their profile.
  5. Use the checkboxes to remove/add specific roles in your results.

Your permissions as and admin and the permissions you can set for users: 

There are two things that determine which users you see and can add and also which permissions you can grant them(!):

  1. Your type of role or access level: this defines what type of other users you can add or edit. See 'Access levels for user management in Cirrus'. This means that for example a System Admin in Cirrus can deputise the user management for groups within the hierarchy to Admins.
  2. Your access to groups to administer: in your user-profile on the hierarchy tab it is determined via check-boxes which groups you can administer (this inherits down).
  3. Not only has this been setup for your admin account, it also determines which permission you can grant the users you create:


Important: Key things to keep in mind when creating users

What a user can see and do is determined by:

And additionally it is always good to remember: 

  • Content needs to be live / published to be used / seen
  • Content gets locked when used by another user or in an assessment for example

User Import

Cirrus Assessment offers the option to Import users via an Excel file.

Creating a user does not trigger an email in Cirrus. Customers can use their own systems / channels for this. If you want to help develop this contact us at

Tip: you can send a link to the users with the cirrus password reset link of your environment. This will force them to create a new password. Do not use this if you have an integration in place.

Bulk Actions in User Management

Bulk actions in user management work differently from bulk actions on items in the Library: there is no button to update a selection of users or filter options to select a specific hierarchy yet. Most customers do this 1) via their integration with Cirrus or 2) using the user import to update the group membership or role of users.

Because the users are in the trash can (and can be restored), the import function will state "synchronized" upon these kinds of updates.

Users with the right to access Admin > Trash Can (usually this the System Administrators role only) are able to restore the users, at which point they will appear again under Admin > Users.

There is no option in the platform to remove multiple users from a hierarchy at once. This indeed means deleting the hierarchy for each user individually or contacting

Deactivating or deleting users

When a user should no longer have access to Cirrus the principal rule should be: do not delete, de-activate (archive). Cirrus offers several options in this case, in order of preferred approach these are:

  1. On the user's profile check the options Disable Cirrus login and Disable password reset.
  2. Assigning users to a Role without any access to the application. If you have a list you can achieve that in bulk by re-importing them as it will update their role.
  3. Deleting a user - this moves it to quarantaine the trash can. However: if the trash can is emptied after 30 days, the user data will be lost.
  4. Alternatively you can assign a new password and email address to the users. Changing their e-mail will disable the ability to reset the user's password and subsequent login via the reset password link on the login page. Replacing users' email with a mail address you monitor will allow you to see if/when they try to get access.

If you use an integration / single sign on we recommend taking steps at the identity provider level. Currently there are no manual bulk actions in place for these actions, except for assigning the no-access role via the user import.

Enabling or disabling password reset for users

Password reset by users themselves - It depends on a users role and profile settings if a user is able to reset their own password:
  • Candidates cannot login and change their profile / passwords via the interface. On the login page candidates might offered 'Can't login?' link which access the option to have a reset password email being sent to the candidates email address. Please note: Always contact your exam provider about the correct procedure - Cirrus does not have direct access to your account.
  • Authors, Teacher and other users can go their profile after logging in and change their password. Alternatively they can also use the 'Can't login?' link on the login page.

Admin: Disable password reset option on the user profile.

User administrators of your environment can decide to set the option "Disable password reset:" on the user profile. This usually set by customers using an integration for user management and not part of the import via Excel. Using this will disable both resetting the password via the User Interface and remove the 'Can't login' link on the login page.

Alternatively some customers set a generic (no-reply) email address for all users. This will disable the ability to reset the user's password and subsequent login via the resetpassword link on the login page.

Restricting login access to certain IPs

User administrators of your environment can decide to allow users to only login from certain locations or better said: certain IP addresses. This can be set in the user's profile:

  • Go to Admin > Users > open a user
  • Allow login via these IP addresses: by default this field is empty - which means there is no restriction to log in from a specific address. If you enter an IP address or IP range, the user can only log in from this IP or IP range:
    • You can add multiple IP addresses: they should be separated by a comma.
    • You can add an IP range by using a dash (for example x.xx.20.123-x.xx.20.130)
    • Empty = All IP addresses allowed.


When a user tries to login from outside this IP, he or she will be denied access and see a message stating "Sorry, but you don’t have permission to log in from this IP or IP range":


Using the API for user management.

Most larger customers use an integration with their Student Tracking System, Learner Managemen System, CRM or IdP for user management. The following information is relevant in this case:

Feel free to contact us at if you have any questions.

Comments 0

Cirrus uses Zendesk to provide our Help Center services. Check out Zendesk's Terms of Service and Privacy Policy, as they govern your use of these services.

Powered by Zendesk