Manage webmate Mobile Access

Mobile Access lets local mobile devices reach test systems that are reachable from your webmate test infrastructure. Administrators should prepare the organization, define who may use the feature, and know when to involve webmate support.

This article is for organization administrators. If you want to create and activate a Mobile Access token for your own device, see Mobile Access .

Before You Start

Mobile Access has security implications because it extends access to internal test systems from local mobile devices. Before enabling or rolling out the feature, clarify:

• which projects and teams need Mobile Access,
• which test systems local mobile devices must reach,
• whether access is limited to specific environments,
• which users are allowed to create Mobile Access tokens,
• how long access may remain active,
• and who should be contacted when a local device is lost or should no longer have access.

If Mobile Access is not available in your organization, contact webmate support (opens in a new tab) . Support must enable the feature before users can create tokens.

Review Organization Settings

Open Administration, go to Settings, and search for Mobile Access. The setting controls whether users can access testing infrastructure with external clients. If the setting cannot be changed in your organization, use the support link shown next to the setting.

Also review related security settings such as password requirements, user profile options, and activity visibility. These settings do not replace Mobile Access controls, but they help keep the surrounding account and organization setup consistent.

For the full settings reference, see Settings .

Decide Who May Use Mobile Access

Only users who need local device access to internal test systems should use Mobile Access. Keep the first user group narrow, then expand it after the first users have validated the workflow.

When planning access, check that users:

• have access to the correct webmate project,
• understand which test systems they may access,
• can install OpenVPN Connect on the mobile device,
• know how to protect the device with the required device lock,
• and know who to contact when access should be removed.

Mobile Access tokens are created by users in their own profile area after the feature is available. Administrators should therefore combine project membership, user communication, and support processes instead of treating Mobile Access as a one-time technical switch.

Prepare Users

Before users create tokens, send them the following information:

• a link to the user workflow in Mobile Access ,
• the list of test systems they are allowed to reach,
• the expected duration of the access,
• the required mobile VPN client,
• and the support contact for activation or connection problems.

Users need OpenVPN Connect on their mobile device. During activation, webmate shows a QR code that transfers the Mobile Access configuration to the device. If users do not see a Mobile Access entry in their profile area, the feature is not available for the organization or their account yet.

Validate the First Token

Validate the process with one user before enabling the workflow for a larger group:

1. Confirm that Mobile Access is visible for the user.
2. Ask the user to create a Mobile Access token.
3. Ask the user to activate the token with the mobile device.
4. Start the VPN connection on the mobile device.
5. Open a permitted test system from the mobile device.
6. Confirm that unrelated internal systems are not part of the intended test scope.

Use a simple validation page or login page. Avoid testing with production data or accounts that are not needed for the Mobile Access process.

Handle Lost Devices and Expired Access

Mobile Access tokens are temporary and can be issued again when users still need access. If a device is lost, replaced, or no longer used for testing, remove the access as soon as possible through the available Mobile Access controls or contact support if administrator-side removal is not available in your organization.

When a user leaves a project or no longer needs Mobile Access, also review their project membership and role assignments. Removing project access helps prevent the user from continuing to use related webmate resources.

Troubleshooting

If a user cannot create or activate a Mobile Access token, check the following first:

• Mobile Access is enabled for the organization.
• The user can sign in to webmate.
• The user can open the Mobile Access view from the profile area.
• OpenVPN Connect is installed on the mobile device.
• The device camera can scan the QR code.
• The token has not expired before activation.

If the VPN connects but the test system cannot be reached, check whether the same system is reachable from webmate test infrastructure. If it is not reachable from webmate either, treat it as an infrastructure or DNS issue and contact support with the target host, project, user, and time of the test.