Roles and Permissions

The following enables you to define roles that determine which functions in WonderSuite can be accessed. Each user can only access the features of the role awarded to them.

To define roles and permissions:

1. Click the Account Settings button that appears in the top-right corner.
2. Select Users & Activity → Manage Roles. A list of all the roles that have been created is displayed.
3. To add a new role, click the + Add Role option.
4. Mark the checkboxes of the permissions to be awarded to this role. The permissions are divided into the following groups: Account Settings, Audit Logs, WonderSuite, WonderBuild, and WonderFence. Expand a group to see its permissions.
5. Where a capability offers both, Edit is listed with View nested underneath it. Marking Edit marks View with it, and View then cannot be cleared on its own — editing implies seeing. To give a role read-only access, clear the Edit checkbox and leave View marked. Marking a group's top-level - all permission marks everything under it; clearing one child afterwards leaves the rest of the group marked.
6. Application access is not set here — it belongs to groups. See Groups, or the Share with Groups field on the application itself.

• Admin — The administrator role has all permissions. An administrator can invite other people to the platform and can assign each a role that determines their permissions.

About application access: an application that has not been given to any group is visible to everyone in the project — that is how applications that predate access control, and newly created ones, stay reachable. Giving it to a group is what limits it: from that point on, only that group's members can see it, plus account administrators, who always see every application. The list of applications you can assign is limited to the ones you can see yourself, and saving never changes assignments outside that list. Applications you cannot see are also not shown to you anywhere else in the platform.