BrowserStack seats and service accounts, read into Ploy

Human users, service accounts and per product licences, read into the same access graph as everything else.

Book a demo

TYPE · SAAS

BrowserStack connectorHOURLY SYNCCAPABILITIES

WHAT PLOY DOES

Sync users and service accountsHuman users and BrowserStack service accounts both arrive as identities, so the credentials driving your test runs are governed beside the people.

READ

Read disabled and pending accountsBrowserStack marks an account disabled or pending and both come through as blocked, with the raw state kept on the identity. An account carrying no state reads as active.

READ

Read product licences and their holdersEach BrowserStack product arrives as its own licence with the people holding it attached, so Automate and App Live are counted separately.

READ

See who can get into BrowserStackAccess is recorded at the application level, with the BrowserStack role held by the user as the entitlement on the row.

READ

Register BrowserStack in the SaaS inventoryBrowserStack itself is registered as an application in Ploy, with its users attached.

READ

2.1WHAT IT UNLOCKS

Three jobs this connector does on day one

SEATS

Every product has a list of holders

BrowserStack licences arrive one per product with the people on them, so who has Automate and who has App Live is a list rather than a guess at renewal.

SERVICE ACCOUNTS

The automation credentials are identities too

BrowserStack service accounts land in the graph beside the humans, typed as machines, with their application access attached.

LEAVERS

A leaver takes their products with them

When HR reports a leaver, the BrowserStack products and role they held appear in the offboarding queue, and the removal is tracked until it is confirmed.

2.3