Updating User Information, Access Level, Enrollment and Rights
The Update User window is used to update User Data, Enrollment, and Rights for a project. Global Admin users can update any user within the organization and can access the Update User option from the My Project page.
You must be a Global Admin at the Organization Access Level to Update User Data.
Update a User
- Sign in to CloudNine Review. On the My Projects page, select Users - Update User from the top menu bar.

- The Update User - Select a user - window opens. Use the drop-down to select the User email to update.

Once selected, the Update User Data Window opens.
Update User Data
(1) Select User: Drop-down list of users within the organization.
(2) User Data: The User Data screen allows you to update:
- Contact Information: Add or update a user's contact information. The User Name and Email should match.
- Doc View List Size: Increase or decrease the number of records listed on the page. The default is 25 records.
- Session Timeout: Automatically logs the user out of CloudNine Review after the configured inactivity period (default: 20 minutes).
- Organization Access Level: Sets the user's access level at the organization level. There are three Access levels:
- Global Admin: The highest level of access in the organization. Global Admin users can access all projects, add/update users, monitor all project activity through the Organization Discovery Queue, and access reports.
- Reviewer: The lowest access level in the organization. Reviewers can access only projects to which they are enrolled; the Project Access Level defaults to Project Reviewer. Project Reviewers can only access Review Sets if enabled. If not enabled, a reviewer can access the project database but not search. A reviewer can create a new project and load data into the project. The reviewer is assigned as the Project Admin and can enroll additional users.
- User: The most common Organization level. Users will only see projects to which they are enrolled. The project access level will default to Project User. A project user will have access to the project database, including search. Users can create new projects and load data into the project. The user is a ProjectAdmin for any projects they create and can enroll additional users.
- Project-level enrollment and rights can be changed by the Project Admin or a Global Admin.
- Referred By: Optional field that can be used for tracking purposes.
- FTPAccess: Enabled by default, allows the user to upload data to CloudNine Review.
- User Disabled: Disables a user from logging in to CloudNine Review.
- MFA Enabled: Selected by default, requires users to use multi-factor authentication when logging in to CloudNine Review.
(3) Enrollment: Enroll / Unenroll users to projects within the Organization. A Global Admin can enroll/unenroll users to any project in the organization. To enroll/unenroll users in a project, you must be a Project Admin.

(4) Rights: Global and Project Admins can specify a user's Access Level and Rights in the Project. Any user who creates a new project and uploads data into it is the Project Admin for the project. When a user is enrolled in a project, the Project Access Level is determined by their Organization Access Level, but can be changed for each project. In addition, specific rights can be added/removed at the project level.

- Project Access Level: There are three access levels for a project.
- Project Admin: Can update project maintenance, enroll users, and assign rights.
- Project User: Has access to the project with the rights given.
- Project Reviewer: Only has access to review sets when they are enabled. If not enabled, has access to the full database but not search.
- Rights: The table below describes the rights available for each section.
- All Rights: Gives the user all rights described in the table below. The Project Admin who creates the project and loads data will have All Rights assigned.
| Rights | Description |
| Document Rights | |
| Create Global Fields | The user can add fields to the database that are visible to all users. |
| Edit Global Fields | Users can change global fields. |
| Bulk Tag Documents |
Users can group tag document records. |
| Annotate Tag Documents | Ability to redact and annotate documents in the project. |
| Download Documents (default selection) | Ability to download all versions of the document. |
| Print Documents (default selection) | The user can print (image) the current document. |
| Reporting Rights | |
| Audit Log Report | The user can access the Audit log report. |
| Index Report | Access to the metadata index report. |
| Searching Rights | |
| Full Text Searching | The user can search the document text. |
| Exporting Rights | |
| Export Documents | Access to the Self-Service Production tool. |
| Bulk Redaction | Can perform bulk redaction on PII and search term hits. |
| Filter - View Rights | Located on the Filter tab on the Rights screen. View Rights allows you to hide document versions from users. |
| Hide Image Tab | The user cannot see the Images. |
| Hide Native Tab | The user cannot see Native files. |
| Hide Text Tab | Text is not available to the user. |
| Hide HTML Tab | The HTML tab is not available to the user. |
- Filter: In addition to setting View Rights, a Filter can be implemented to specify the documents the user can see. For example, you may want the user to only access document records within a specific date range. This is useful when you have a third party, such as an expert witness, and you wish to provide them access to the project, with limits on the documents they can see.

(5) Fields: You can also choose the System, Metadata, and Global fields that a user can see, filter, and search.

(6) IP Restrictions: Enter the IP addresses from which the user is allowed to access CloudNine Review. You can add an unlimited number of IP addresses.
