Infrastructure

BrowserStack

Connect BrowserStack to Ploy to see everyone in your BrowserStack organization, the role each person holds, and the teams they belong to. Ploy matches BrowserStack users to your existing Ploy identities by email and surfaces, for every user, their name, email, account status, role (Owner, Admin, or User), and team memberships.

Before you begin

Ploy reads your users through BrowserStack's User Management REST API. BrowserStack restricts this API, so confirm all three of the following before you connect:

  • Enterprise plan — the User Management REST API is only available on BrowserStack's Enterprise plan.

  • API access switched on — even on the Enterprise plan, this API is off by default. An Owner or Admin must contact BrowserStack Support and ask them to enable the User Management (Users) REST API for your organization. There is no self-serve toggle.

  • Owner or Admin credentials — the credentials you give Ploy must belong to a member with the Owner or Admin role. Only these roles can list every user in the organization.

Which credentials to use

Use the username and access key of an Owner or Admin member. You do not have to use a specific person's personal login — your Owner can create a dedicated member for Ploy, give it the Admin role, and use that member's username and access key.

Do not use a BrowserStack service account. Service accounts only ever get User-level access in BrowserStack, and the User Management API requires Owner or Admin, so a service account's credentials will be rejected.

A note on teams: an Owner, and an Admin with organization-wide access, can see every user. An Admin limited to a single team can only see that team's members, so make sure the account you use has organization-wide access rather than being scoped to one team.

Find your username and access key

  1. Sign in to BrowserStack as the Owner or Admin whose credentials you will use.

  2. Open your BrowserStack account settings from your profile menu in the top-right corner.

  3. Find your Username and Access Key — the same pair used for HTTP Basic authentication.

  4. Copy both. You will paste them into Ploy in the next step.

Connect BrowserStack in Ploy

  1. Open the BrowserStack integration in Ploy.

  2. In BrowserStack Username, enter the username of the Owner or Admin account.

  3. In BrowserStack Access Key, paste that account's access key.

  4. Click Test to check the connection. Ploy verifies the credentials against BrowserStack.

  5. When the test succeeds, click Save. Ploy will begin scanning your BrowserStack users on its regular schedule.

What each field is for

  • BrowserStack Username: the Owner or Admin account Ploy authenticates as.

  • BrowserStack Access Key: authenticates Ploy to the BrowserStack API for this connection. It is stored encrypted and is not shown again after you save.

What Ploy imports

  • Users — every user in your BrowserStack organization, matched to your Ploy identities by email, with their name, email, and account status.

  • Roles — the role each user holds: Owner, Admin, or User.

  • Teams — the BrowserStack teams each user belongs to.

Ploy refreshes this data automatically on a recurring schedule. BrowserStack does not expose a last-login or last-active time through this API, so Ploy does not show BrowserStack activity dates.

Troubleshooting

  • The test reports that your organization does not have permission to access the API. Your organization is not entitled to the User Management API yet. Confirm you are on the Enterprise plan and that an Owner or Admin has asked BrowserStack Support to enable the Users REST API.

  • The test reports that the credentials were rejected or unauthorized. The username and access key are valid, but the account is not an Owner or Admin. Use Owner or Admin credentials — not a service account, and not a standard User.

  • The connection fails to authenticate at all. Re-check the username and access key for typos or extra spaces, and make sure the access key has not been regenerated in BrowserStack since you copied it.

  • A user is missing from Ploy. Ploy lists the users the connected account can see. If the connected Admin is limited to a single team, use an Owner or an organization-wide Admin instead.

Was this helpful?