Gem
Connect Gem to Ploy to see every user on your Gem team, whether they are a site admin, and whether they are disabled. Ploy can also disable and re-enable Gem users.
This integration is in beta
The Gem integration is in beta. It was built from Gem's API documentation and has not yet been checked against a live Gem team, so some details may need adjusting once customers connect it. Beta does not limit what the integration can do.
The first step of setup is a consent checkbox. Ticking it lets Ploy capture redacted error data when a request to Gem fails: the error response Gem sends back, with personal details, keys and other secrets removed. Ploy uses it only to fix problems with this integration. You must tick the box to continue.
What Ploy reads
Every user on your Gem team, with their name and email address
Whether each user is a site admin or a regular user
Whether each user is disabled
Ploy reads users from Gem ATS. It does not read candidates, applications, jobs, offers, scorecards, interviews, projects or sequences, and it does not read hiring team assignments on jobs.
Before you start
You need:
A Gem team with Gem ATS enabled. Ploy reads your team's users from Gem ATS, so a team that uses only Gem's CRM cannot be connected yet.
A Gem team admin, who can create an API key in Team Settings.
Create an API key in Gem
Sign in to Gem as a team admin.
Open Team Settings and create an API key.
Copy the key. It works for your whole team, so treat it like an admin password and use it only for Ploy.
Connect Gem in Ploy
In Ploy, open Integrations and choose Gem.
Tick the beta consent checkbox.
Paste the API key and continue.
Choose the Gem user Ploy acts as. Gem records every change made through its API against a named, active team member, so when Ploy disables or re-enables someone, Gem shows the change as made by this person. Pick a team admin who will stay active. You can leave this empty if you only want Ploy to scan; disabling and re-enabling stays off until you choose someone.
Click Test. Ploy reads your Gem users to check the key works.
Finish the setup. The first scan starts straight away.
Things to know
Disabled users show as having lost access straight away.
Gem's API cannot create, invite or delete users, or change whether someone is a site admin. Do those in Gem's Team Settings. To take someone's access away from Ploy, disable them.
When Ploy disables a user, Gem pauses their outreach sequences, scheduled reports and saved search actions, and keeps their history. Re-enabling them restores their access; check in Gem whether their sequences and reports need restarting.
Ploy will not disable the user it acts as, because every later change would then fail. Choose a different acting user first.
Gem does not report when users last signed in or whether they use multi-factor authentication, so Ploy cannot show either.
Troubleshooting
Gem rejected that API key: check the key was copied in full and has not been deleted in Team Settings.
Gem refused to list your team's users: create the key as a team admin, and check that Gem ATS is enabled for your team.
Gem could not find an active team member for the user Ploy acts as: the acting user has been disabled or removed in Gem. Open the Gem integration's settings in Ploy and choose another active user.
Choose the Gem user Ploy acts as: no acting user is set. Open the Gem integration's settings in Ploy and choose one.