INGENIOUS.BUILD
Connect INGENIOUS.BUILD to Ploy to see every employee in your INGENIOUS.BUILD workspace, the account type each one holds, who is a workspace administrator, and who has been invited, disabled or archived. Ploy can also add employees, change an employee's account type, and archive and restore employees.
This integration is in beta
The INGENIOUS.BUILD integration is in beta. It was built from INGENIOUS.BUILD's documented public API and has not yet been run against a live workspace, so some behaviour may differ from what is described here until it has.
The first step of setup is a consent checkbox. Ticking it lets Ploy send redacted error data to its own monitoring when a call to INGENIOUS.BUILD fails. Redacted means secrets, tokens and personal details are removed before anything is stored. Ploy uses it only to fix problems with the integration. You need to tick it to continue.
What Ploy reads
Every employee in the connected workspace, with their name, email address and account type (for example Administrator, or the custom account types your workspace defines).
Workspace administrators, shown as a separate Workspace administrator entitlement.
Each employee's status: active, invited but not yet signed in, disabled, or archived. Disabled and archived employees are shown as no longer having access. Employees whose records exist but who were never given a sign-in (off-system) are listed, but are not counted as having access.
When each employee last signed in.
The workspace itself, so several INGENIOUS.BUILD workspaces connected to one Ploy organisation stay separate.
Contacts (people at your vendors, subcontractors and clients) are not workspace users, so they are not read. Project roles and project directory membership are not read: INGENIOUS.BUILD's API does not list who holds them.
What Ploy can change
Add an employee with their first name, last name and email address, and an account type. INGENIOUS.BUILD sends them its own invitation email. The account type is required and must already exist in your workspace. Adding someone who is already an employee counts as done. If the address belongs to an archived or disabled employee, Ploy asks you to restore them instead.
Change an employee's account type. The account type must already exist in your workspace.
Archive an employee and restore an archived employee. INGENIOUS.BUILD's API cannot delete employees, so archiving is how Ploy removes someone's access.
Before you start
You need an INGENIOUS.BUILD access token created by a user whose account type can manage employee records and invitations, such as an Administrator. Ploy acts with that user's permissions.
Sign in to INGENIOUS.BUILD as an Administrator.
Open Company Settings, then Access Tokens.
Create a token and copy it. Access tokens do not expire. Revoking the token there stops Ploy's access straight away.
You also need your workspace address, the ingenious.build address you sign in at, for example acme.ingenious.build.
Connect INGENIOUS.BUILD
In Ploy, open Integrations and choose INGENIOUS.BUILD.
Tick the beta consent checkbox.
Enter your workspace address, for example acme.ingenious.build. Just the first part (acme) works too.
Paste the access token.
Select Test to check the connection. Ploy reads the workspace's employees to confirm it works.
Save the connection. The first scan starts straight away.
To connect another workspace, add another INGENIOUS.BUILD connection.
Troubleshooting
INGENIOUS.BUILD rejected that access token: check the token was copied in full and has not been revoked under Company Settings, Access Tokens.
That access token cannot read employees: create the token while signed in as a user whose account type can manage employee records, such as an Administrator.
INGENIOUS.BUILD could not find that workspace: check the address matches the one you sign in at.
Not an INGENIOUS.BUILD account type: the account type named in your workflow does not exist in the workspace. The error lists the account types that do.
INGENIOUS.BUILD refused the change: INGENIOUS.BUILD's own reason is shown with the error.
Changes take a while: INGENIOUS.BUILD allows 60 reads a minute per token by default. Large workspaces are read in pages of 100 employees.