Lattice
Connect Lattice to Ploy to see every user in your Lattice company, whether they are active, invited or deactivated, and which of them are Lattice admins.
This integration is in beta
The Lattice integration is in beta. It was built from Lattice's API documentation and has not yet been checked against a live Lattice account, 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 Lattice fails: the error response Lattice 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 Lattice user, with their name and email address
Whether each user is active, invited and not yet signed up, added but never invited, or deactivated
Whether each user is a Lattice admin, shown as Admin or User
Ploy only reads. Lattice's API cannot add, change, deactivate or remove users, so Ploy cannot either; manage users in Lattice or in the HR system that feeds it. Ploy does not read goals, feedback, reviews, check-ins, departments or custom profile fields.
Before you start
You need:
A Lattice account with admin permissions. The API key must be created by an admin: a Lattice key can see only what the person who created it can see, and only an admin can see everyone in the company.
To know which data region your Lattice account is hosted in: the United States, or Europe, Middle East and Africa. Most accounts are in the United States. If you are not sure, ask Lattice support.
Create an API key in Lattice
Sign in to Lattice as an admin.
Open Lattice's admin settings and find the API keys page.
Create a new API key and copy it. Treat it like a password: anyone holding it can see what you can see in Lattice.
Connect Lattice in Ploy
In Ploy, open Integrations and choose Lattice.
Tick the beta consent checkbox.
Select your Lattice data region.
Paste the API key.
Click Test. Ploy checks that the key belongs to an admin and that it can read your users.
Finish the setup. The first scan starts straight away.
Things to know
Deactivated users show as having lost access straight away.
Invited users who have not signed up yet keep their seat in Ploy until they accept or are removed.
Users who were added to Lattice, for example from your HR system, but never invited are listed without access.
Ploy re-checks the key at the start of every scan. If the admin who created it loses admin rights, scans stop until you connect a new key from an admin, so Ploy never mistakes a partial view of your company for the whole of it.
Troubleshooting
Lattice rejected that API key: check the key was copied in full, that you selected the right region, and that the key has not been deleted in Lattice.
Ploy needs an API key created by a Lattice admin: the key belongs to someone who is not an admin. Sign in as an admin, create a new key and paste it in.
Lattice accepted the key but refused to list users: check that the admin who created the key still has access to Lattice.
Scans have stopped: the person who created the key may have lost admin rights or left. Create a new key as an admin and update the connection.