Set Up webmate
Use this checklist when you prepare a new webmate organization for productive use. It covers the administrative setup that is usually needed before teams can run manual tests, automated tests, and mobile sessions in their projects.
You need organization administrator access for most steps. If the Administration area is not visible in the top navigation, ask an existing organization administrator to grant the required access or to perform the setup with you.
Before You Start
Collect the following information before changing the organization configuration:
- the projects or teams that should work in webmate,
- the users who need access to each project,
- the role model for each project,
- the device slots or private devices that each project may use,
- security settings such as password rules, token lifetimes, and idle timeouts,
- required integrations such as Jira or CI servers,
- and any network requirements for accessing internal test systems.
If webmate must connect to internal systems, identity providers, private device labs, or custom DNS zones, coordinate the required technical details with webmate support (opens in a new tab) before inviting regular users.
Create Projects
Start by creating the projects that represent your teams, products, or test scopes. Projects define where test results, apps, resources, and infrastructure access are organized.
Open Administration, go to Projects, and create one project for each independent team or product area. During project creation, you can already assign users, roles, and slots if that information is available.
For the detailed procedure, see Create Projects .
Invite Users and Grant Project Access
Invite users after the project structure is clear. This keeps the initial access review simple and avoids giving users access to projects that are still being prepared.
For each user:
- Create or invite the user account.
- Add the user to the projects they should work in.
- Assign the project roles that match their responsibilities.
The detailed steps are covered in Add User , Add User to Project , and Assign Roles to Users .
Review Roles and Permissions
Roles control what users can do in each project. Before users start testing, review whether the default roles match your workflow or whether you need custom roles for restricted access.
Use the built-in role model for simple setups. Create custom roles when users should only view results, only execute tests, manage project resources, or administer infrastructure for selected projects.
See Roles and Permissions for the permission model and Create Roles for the role creation workflow.
Assign Device Slots
Assign slots to the projects that are allowed to use them. A project without suitable slot access cannot deploy the related desktop browsers, mobile browsers, or mobile devices.
Review slot assignments carefully when multiple projects share limited infrastructure. Shared slots should be assigned only to projects that actually need them, otherwise users may block devices for other teams.
For the detailed procedure, see Assign Slots to Projects .
Configure Organization Settings
Review organization settings before regular users start working. Common first-run settings include:
- password requirements and failed login handling,
- API token lifetime limits,
- invitation token lifetime limits,
- workbench timeout and concurrent workbench access,
- device idle timeout behavior,
- mobile access availability,
- DNS management,
- and activity visibility.
Use conservative security settings for new organizations, then adapt them after the first teams have completed their setup. See Settings for the available configuration options.
Configure Integrations
Configure integrations after the organization has users, projects, and access rules. This makes it easier to test that exported findings and automated results are created in the correct project context.
Typical integrations include:
- Jira for creating issues from findings,
- TeamCity for CI-based test execution,
- and App Center for mobile app distribution.
See Integrate with Jira , Integrate with TeamCity , and Integrate MS AppCenter for setup instructions.
Validate the Setup
Before handing the organization over to a team, verify the setup with a regular user account:
- Sign in as the user.
- Confirm that only the expected projects are visible.
- Open a project and check that the expected test results and resources are accessible.
- Deploy a device or browser from an assigned slot.
- Start a short manual session or automated run.
- Confirm that issue export, CI integration, or app distribution works if configured.
If validation fails because a menu item or action is unavailable, check the user’s project membership, role assignments, and slot access first.