Overview

The BrowserStack integration reviews who has access to your BrowserStack organization. LowerPlane reads the user roster (name, email, role, and invite status) with the User Management API, matches each user to your People directory, and flags accounts that belong to people who have left. Connection type: Username and access key (HTTP Basic, read-only)

Prerequisites

The BrowserStack User Management API requires an Enterprise plan, and the account you connect with must be an Owner or Admin. BrowserStack may need to enable the API for your organization. If connecting fails with a 403 or 404 error, contact BrowserStack support.

Getting Your Credentials

1

Sign in as an Owner or Admin

Sign in to BrowserStack with an account that has the Owner or Admin role.
2

Open your access key

Go to Account → Settings → Access Key (or open the Access Key menu in any BrowserStack product).
3

Copy the username and access key

Copy the Username (for example jane_ab12cd, not your email) and the Access Key.

Connecting in LowerPlane

1

Open the integration

Go to Integrations in LowerPlane and find BrowserStack.
2

Enter your credentials

  • Username — your BrowserStack API username
  • Access Key — your BrowserStack access key
3

Connect

Click Connect. The first sync starts right away. If the credentials are wrong or the User Management API is not enabled, that sync fails with the error from BrowserStack.

Permissions and Data

Permissions Required

LowerPlane only reads users. It never invites, updates, disables, or deletes users, and never starts test sessions.

Data Used by LowerPlane

LowerPlane does not read test sessions, builds, screenshots, videos, logs, or usage data.

Additional Information

Access Review

BrowserStack appears as a system in Access Review. Every user is listed with their BrowserStack role (Owner, Admin, or User) and the products they can use. Users removed from BrowserStack are marked inactive on the next sync.

Automated Checks

On each sync, LowerPlane runs these checks against every BrowserStack user:
Users whose email does not match anyone in People (for example contractors) fail the access-valid check until you add them to People or mark them out of scope. The API does not expose MFA or last-login data, so there is no MFA check.

Frameworks Supported