Simployer
Connect Simployer One to Ploy to use your HR system as the source of truth for who works at your company. Once connected, Ploy reads your employee roster on a schedule, keeps your member directory up to date with each person's manager, department, office, team and employment dates, and can deactivate or remove employees from your offboarding automations.
Tip: this integration is for Simployer One (the platform formerly known as AlexisHR). If your company uses Simployer Classic, that is a different product with a different API and is not covered by this integration.
What Ploy syncs from Simployer One
Once connected, Ploy scans your Simployer One account every hour and keeps the following up to date:
Employees — every employee in your roster, active and inactive, becomes a person in Ploy with their profile attributes: name, work and personal email, job title, employee number, manager, department, office, teams, company, employment type, country, and hire and end dates. Each employee also gets a login identity in Ploy, recorded as active or inactive based on their employment status.
Access to Simployer — Simployer itself is added to your app inventory, and Ploy tracks which employees hold access to it: active employees are recorded as having access from their hire date, and offboarded employees are recorded as having lost access on their end date.
Upcoming joiners — an employee whose hire date is in the future appears in Ploy ahead of their start date (so onboarding automations can run against it) without being recorded as holding access yet.
Ploy requests only the profile fields listed above. Sensitive fields that Simployer One also stores on the employee record — such as national identity numbers, bank account details, home address and date of birth — are never requested and never reach Ploy.
Simployer One's API does not expose MFA status, sign-in activity or license usage, so Ploy does not sync those from this integration.
What Ploy can change in Simployer One
With the connection in place, Ploy's automations can also act on Simployer One:
Deactivate an employee — marks the employee inactive in Simployer One. The HR record is kept, so this can be reversed.
Reactivate an employee — marks a previously deactivated employee active again.
Remove an employee — permanently deletes the employee record from Simployer One, via the "Remove user in integration" flow action. This is a hard delete of the HR record, so use it deliberately in offboarding flows.
Prerequisites
A Simployer One account (formerly AlexisHR).
An Owner in your Simployer One account. Access tokens are created by an Owner, and the token is tied to the Owner who created it — if that person later leaves or loses the Owner role, the token stops working and you will need to reconnect Ploy with a new one. Consider creating the token from an Owner account that will remain in place, such as a service account.
Step 1 — Create an access token in Simployer One
Sign in to Simployer One as an Owner.
Open Settings and go to Access tokens.
Create a new access token, making sure access to the Public API is enabled for it (Provisioning API access alone is not enough for Ploy to read your roster).
Copy the token straight away — Simployer One shows it only once.
Keep the token somewhere safe until you have pasted it into Ploy. The token grants broad access to your account, so treat it like a password. Ploy stores it encrypted and only reads the employee fields listed above.
Step 2 — Connect Simployer in Ploy
In Ploy, go to Integrations, find Simployer and click Connect.
The setup page links to this guide and to the Simployer One API guide (Simployer's own documentation on creating and using access tokens) if you need a reference while creating the token.
Enter your Simployer One access token — paste the token you created in Step 1. This field is required. Remember this connects Simployer One (formerly AlexisHR), not Simployer Classic.
Test and save the connection. Ploy verifies the token by reading one employee from your roster — so a successful connection means Ploy can genuinely read your employee data.
After saving, Ploy starts syncing your roster on its hourly schedule. Depending on the size of your organisation it can take a little while for every employee to appear in Ploy.
Updating the access token
If the token is rotated, or the Owner who created it leaves or loses the Owner role, the sync stops working. Create a new token in Simployer One (Step 1), open the Simployer integration in Ploy again, paste the new token and save.
Troubleshooting
"Simployer One rejected that access token" — the token was not accepted. Access tokens are created by an Owner under Settings, are shown only once, and stop working if the Owner who created them leaves or loses the Owner role. Create a new token and paste it again.
"That access token cannot read employees" — the token exists but cannot read your roster. When creating the token in Simployer One, enable access to the Public API (not only the Provisioning API), then paste the new token into Ploy.
"We couldn't reach the Simployer One API with that access token" — a temporary network or Simployer error, or a malformed token. Check the token was copied in full and try again in a few minutes; if it keeps failing, contact Ploy support.
Employees are missing after connecting — scans run in the background on an hourly schedule and can take a while on large rosters. If people are still missing after a couple of hours, confirm they appear in the employee list in Simployer One under the same account the token was created in.