Devin
Connect Devin to Ploy to see everyone in your Devin enterprise, the organizations they belong to and the roles they hold, and to invite people, change their roles or remove them from Ploy.
This integration is in beta. It was built from Devin's published API and has not yet been run against a live Devin enterprise, so expect rough edges and tell us if anything looks wrong.
What Ploy reads
Every user in the Devin enterprise you connect, with their name and email address. This includes people whose access comes from an identity provider group as well as people added directly.
Every enterprise role each user holds, and the role they hold in each organization.
Every organization in the enterprise, shown as an account in Ploy.
Ploy does not read service users, sessions, usage, or the audit log.
What Ploy can change
Invite a person to the enterprise by email, with the enterprise role you choose.
Change a user's enterprise role.
Give a person a role in an organization, or take it away, from that organization's page in Ploy.
Remove a user from the enterprise.
Devin only lets Ploy change roles that were given to a person directly. If someone's access comes from an identity provider group, change or remove it in your identity provider instead, and Ploy will tell you which groups are involved.
Before you start
You need a Devin Enterprise plan and an enterprise admin who can provision service users. Devin Teams plan accounts and organization service users cannot read the enterprise's users, so they cannot be connected.
Step 1: Accept the beta terms
When you open the Devin setup in Ploy (go to Integrations and choose Devin), the first page starts with a Beta integration acknowledgement box. Ticking it means you agree that Ploy may capture technical error details from this connection, including API responses with personal information removed, and use them only to debug and improve the integration. Nothing is shared outside Ploy. You must tick the box to continue.
Step 2: Create an enterprise service user in Devin
Sign in to Devin and open Enterprise settings, then Devin API, then the Service users tab.
Select Provision, then Enterprise service user, and give it a name such as Ploy.
Give it a role that includes View Account Membership and View Organizations so Ploy can scan. To let Ploy invite people, change roles and remove users, the role also needs Manage Account Membership.
Choose the longest expiry your security policy allows, so scans keep working.
Copy the API key. It starts with cog_ and Devin shows it only once.
Step 3: Connect Ploy
Back in the Ploy setup, paste the API key on the first page, below the beta acknowledgement.
Select Test to confirm Ploy can read your enterprise's users, then finish the setup.
Using it in flows
When a flow invites someone to Devin, set the Enterprise role option to the name of a Devin enterprise role, exactly as it appears in Devin. Devin needs a role for every invitation.
Troubleshooting
Devin rejected that API key: the key was not copied in full, has expired, or the service user was deleted. Provision a new key and reconnect.
That key cannot read your enterprise's users: the service user's role is missing View Account Membership, or it is an organization service user. Use an enterprise service user with the right role.
Invites, role changes or removals fail with a permission message: add Manage Account Membership to the service user's role.
A removal says the person's access comes from identity provider groups: remove them from those groups in your identity provider.