With ReadyView, you can add role-based access to limit what ReadyView users have access to. This can vary from who can view which networks in an organization to who can reboot a switch. This article walks you through creating and assigning roles and permissions within ReadyView.
Things to note:
By default, all users are placed into the Everyone role. Like any other role, you can change what it has access to — by default, every permission is enabled.
Limit the Everyone role first. Everyone starts with every permission, so every member can do everything until you change it. Before you invite people or turn on single sign-on, edit Everyone to keep only what every member should be able to do, for example with the View Only template, and grant more through other roles.
Users can be added to multiple roles. If a user belongs to two roles where one has a permission disabled and another has it enabled, the user will ultimately have access — the most permissive setting wins.
Roles are ranked from the top down. A member can edit, delete, and assign only the roles at or below the highest role they hold. Drag a rank number, or use the arrows, to change a role's rank.
Only permissions you hold yourself can be granted to, or removed from, a role.
Creating Roles:
- Navigate to: Administration -> Organization -> Roles
- Press Create Role
- Enter a name for the role you wish to create
- Optionally pick a template to start from: Admin, Network Admin, Technician or View Only
- Adjust the permissions: tick individual permissions, use a section's checkbox to grant or clear the whole section, or search for a permission by name
- Once completed press Save
To change a role later, including Everyone, press Edit next to it.
Assigning Roles to Users:
- Navigate to: Administration -> Organization -> Roles
- On the role you would like to add users to, press Assign Members
- Then press the + button
- Select users and then press Save
- Next press the Close button
You can also give people roles when you invite them under Administration -> Organization -> Team. They get those roles when they join.
Limiting what Roles have access to what networks:
- Navigate to the network you wish to limit access to by role
- Go to Settings -> Admins & Users
- Turn on the Private toggle
- Press Add Roles
- Select the roles you want to have access to the network and press Save
- Press the Save button at the bottom
Add at least one role before you make a site private. With no permitted roles, nobody in your organization could open it.
Roles and single sign-on:
If your organization uses single sign-on, your identity provider can assign roles too. See Single Sign-On (SSO) with SAML in ReadyView.
- People who join through single sign-on get the Everyone role. While Everyone allows anything, ReadyView shows a warning with a Review roles link under Administration -> Organization -> Settings -> SAML Configuration
- Each time someone signs in, ReadyView applies the roles named in their
roleattribute and removes roles it no longer sends. Only roles that exist in your organization are applied - Roles you assign in ReadyView are never changed by single sign-on
Troubleshooting:
- "Permission required": none of the member's roles includes that permission. Add it to one of their roles, or assign them a role that has it
- You can't edit, delete or assign a role: the role ranks above your highest role
- A permission can't be selected: you can grant or remove only the permissions you hold yourself
- A member can't open a site: the site is private and none of the member's roles is permitted. Add one of their roles under Settings -> Admins & Users
- A member can do more than expected: one of their roles allows it, often Everyone. If any of a member's roles allows something, they can do it