webmate Permissions
Permissions control which actions a user can perform in webmate.
Administrators do not assign permissions directly to users. Instead, they create roles that contain one or more permission groups and assign those roles to users in a project. A user can have different roles in different projects, so the same person may be able to manage devices in one project and only view test results in another.
For the role assignment workflow, see Assign Roles to Users . For the broader concept of administrators, roles, and projects, see Roles and Permissions .
Permission Scope
Most permissions are project-specific. They grant access only inside the project where the role is assigned. Organization administration is separate from project permissions: an organization administrator can manage global administration tasks, but still needs project membership and project roles to work inside a specific project as a tester.
If a user does not have the required permission, webmate may hide controls, disable buttons, or reject API requests for the protected action.
Permission Groups
webmate groups related permissions so administrators can build practical roles without assigning every action one by one.
Manage Infrastructure
Allows users to manage devices and device slots. Users with this permission can deploy, redeploy, delete, and access physical or virtual devices. They can also modify device slots.
Use this permission for administrators or technical users who are allowed to manage testing infrastructure for a project.
Access Infrastructure
Allows users to use available infrastructure for manual or automated testing. Users with this permission can access devices and create artifacts such as screenshots, network logs, and videos while using the infrastructure.
Use this permission for testers who need to run tests or inspect devices but should not manage the underlying slots.
Manage Tests and Jobs
Allows users to create, modify, and delete tests and jobs.
Use this permission for users who maintain the test assets of a project, such as test templates, scheduled jobs, or reusable test definitions.
Execute Tests and Jobs
Allows users to start new test and job runs.
Use this permission for users or technical accounts that should execute existing tests without changing the test definitions.
Manage Project Resources
Allows users to modify and delete project resources, such as uploaded images, videos, mobile apps, or packages.
Use this permission for users who maintain the assets that tests depend on.
Redeploy Device
Allows users to redeploy an already deployed device.
Use this permission when users should be able to reset a device state without receiving broader infrastructure management rights.
Designing Roles
Start with the smallest role that lets a user perform their normal work. Add permissions only when the user needs the protected action in that project.
Common role patterns are:
- A tester role with access to infrastructure and permission to execute tests.
- A test maintainer role that can manage and execute tests and jobs.
- A resource maintainer role that can manage project resources.
- A project infrastructure role that can manage infrastructure for a specific project.
Roles are additive. If a user has two roles in the same project, webmate grants the combined permissions from both roles.
Troubleshooting Access
If a user cannot see a project, first check whether the user is a member of that project. If the user can see the project but cannot perform an action, check the roles assigned to that user in the project.
For common administration workflows, see: