NEWFlows V2 has been releasedSee what shipped
INTEGRATIONSSAAS
Gem28 OF 28 CAPABILITIES ASSESSED

Who can see your candidates in Gem, and who runs the account

Gem ATS users and who is a site admin, with users disabled and re-enabled from Ploy.

TYPE · SAASAUTH · API KEYDOMAIN · GEM.COM
Gem connectorHOURLY SYNCCAPABILITIES
WHAT PLOY DOES
Sync Gem usersEvery user on your Gem ATS team arrives in Ploy as an identity. Candidates are not users and are not scanned.
READ
Read site admin or userEach user carries their access, site admin or user, on Gem.
READ
Disable a userPloy disables a user in Gem.
WRITE
Re-enable a userPloy turns a disabled user back on.
WRITE
2.1WHAT IT UNLOCKS

Three jobs this connector does on day one

REVIEWS

Site admins named on the row

Users and their admin flag are read on every scan, so the access review starts from who can reach candidate data today.

LEAVERS

Out of the candidate pipeline on the last day

Offboarding disables the user in Gem, so a departing recruiter no longer holds access to candidate records.

AUDIT

Every change has a name on it

Gem records each change Ploy makes against the team member you choose, so the change shows in Gem with a person beside it.

2.3

SETUP

TYPICALLY 10 MINUTES
STEP 01

Create a team API key

A team admin creates the key in Gem under Team Settings. Gem ATS must be enabled for your team, because Ploy reads users from Gem ATS. The key works for the whole team, so store it as you would an admin password.

STEP 02

Choose the user Ploy acts as

Gem records every change made through its API against a named, active team member. Choose that person from the list. Leave it empty if you only want Ploy to scan; disabling and re-enabling users stays off until you choose someone.

STEP 03

Watch the first sync

Ploy tests the key, then your Gem users and site admins land in the graph.

2.4OFTEN CONNECTED TOGETHER
AshbySAASOktaIDENTITY PROVIDERSlackAPPROVALS
BROWSE ALL 117 INTEGRATIONS

Connect Gem, see it in 10 minutes.