Roles and Permissions
Organization Administrators
Every organization in webmate has at least one organization administrator (“org admin”). Organization administrators are able to
- create and delete projects,
- invite new users to webmate,
- make other users project administrators,
- create new roles (see below),
- add or remove users to projects,
- and assign roles to users for a project.
Being an org admin says nothing about what a user can do within a particular project. Administrative permissions and project permissions are independent. In particular, an administrator who wants to act as a regular webmate user in one or more projects must be added to these projects explicitly and be assigned proper project roles. Organization admins are no “god users” (However, being an org admin enables a user to assign those roles to themselves, at will).
A user can determine whether they are an organization administrator by examining the top navigation bar. If there is a link to the Administration area, they are an administrator, otherwise not.
Project Administrators
In addition to being an organization administrator, there is also an administrative role that is restricted to individual projects. Any user can be made a “project administrator” for one or more projects by an organization administrator. Project admins can manage their assigned projects in certain ways. This includes adding other users to and managing permissions for the given project.
On this page , there is more information about how to manage project administrators.
Permissions
If a user wants to access a resource in webmate or start a use case, they need an appropriate permission to do so. For a user lacking a specific permission, webmate may not show specific screen elements, and buttons might be disabled. Operations triggered via the API will return an error if the required permissions are unavailable to the authenticated user.
Administrators are able to assign permissions on a per-project basis. As a result, a user may be able to deploy a device in one project, whereas they may only access existing devices in another one.
There are currently six permission groups that can be assigned to users:
For a detailed reference of these groups and common role patterns, see webmate Permissions .
- Manage Infrastructure
- Allows deploying, redeploying, deleting, and accessing devices (physical or virtual). It also allows modifying device slots.
- Access Infrastructure
- A user with this permission may use infrastructure for manual or automated testing and create artifacts, e.g., screenshots, network logs, videos while using the infrastructure.
- Manage Tests and Jobs
- User may create, modify, and delete tests and jobs.
- Execute Tests and Jobs
- Allows creating new test and job runs.
- Manage Project Resources
- The user may modify and delete resources, such as images, videos, or mobile apps / packages.
- Redeploy Device
- Lets the user redeploy an already deployed device.
Roles
In webmate, it is not possible to assign individual permissions to a user, but only a “role”. A role is more coarse-grained and comprises multiple permissions. There is one built-in role called “Standard User Role” that gives a user full access to the resources of a project. Besides that, administrators can create and configure roles at will.
For role administration, see Assign Roles to Users and Create User Roles .
Assigning Roles
When a role is assigned to a user in a project, its permissions become available to the user. Roles are additive. If a user has been granted two roles for a project, and one specific permission exists in one role and is absent in the other, the user is granted this permission. See for more information about how to manage users’ role assignments.
