EaseLog has three roles. A user's role decides what they can do. Which environments they can see is a separate setting. See Giving a User Access to Environments.

Figure 1. The Users & Roles page showing the user table with Name, Email Address, Role and Status, the All, Admin and Viewer filter chips, and the Invite New User, Delete and Deactivate actions.

The three roles

Role For Admin (Primary Owner) The account owner. Admin Administrators who manage connections, schedules and users. Viewer People who read audit data and dashboards without changing anything.

Primary Owner cannot be assigned

When you invite a user, the Role dropdown offers Admin and Viewer only.

Figure 2. The Invite New User panel, showing Name, Email Address, the Role dropdown, and the Assigned and Unassigned Environments lists used to grant per environment access.

Admin (Primary Owner) does not appear, because it belongs to the account owner rather than being a role you hand out. You can create as many Admin users as you need, and they can do the administrative work.

Choosing between Admin and Viewer

Give Admin to someone who needs to connect or edit environments, change sync schedules, retry failed chunks, or invite and manage other users.

Give Viewer to someone whose job is to read: compliance colleagues, auditors, analysts, anyone investigating what happened without needing to change how EaseLog runs.

Viewer is the right default for most people. Audit data is most useful when plenty of people can consult it, and safest when few people can alter the setup that produces it.

Filtering the user list

The Users & Roles page has All, Admin and Viewer chips above the table. Use them to see who holds which role. The Role column shows it per user, and Status shows whether the account is active.

Changing someone's role

Roles are not fixed at invitation. You can change a user's role afterwards from the Users & Roles page.

Note

A role applies across the whole of EaseLog. There is no way to make somebody an Admin for one environment and a Viewer for another. If you need to limit what somebody sees, limit their environments instead.