PandaDoc
Connect PandaDoc to Ploy to see every user in your PandaDoc organization, their license, and their role in each workspace. Ploy can also add people to the organization, remove them from every workspace, and add or remove them from individual workspaces.
This integration is in beta
The PandaDoc integration is in beta. It was built from PandaDoc's API documentation and has not yet been checked against a live PandaDoc 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 PandaDoc fails: the error response PandaDoc 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 in your PandaDoc organization, with their name and email address
Each user's license: Full, eSign, Read-only, Creator or Guest
Every workspace in the organization
Each user's role in every workspace they belong to: Admin, Manager, Member, Collaborator, or one of your custom roles
Ploy does not read your documents, templates, contacts or webhooks.
What Ploy can change
Add a person. Ploy creates the user with a license and a Member place in the workspace you choose during setup. Their email address must be on your organization's own domain. Someone who is already a PandaDoc user is left as they are.
Remove a person. PandaDoc has no way to delete or suspend a user through its API, so Ploy removes the person from every workspace they belong to. They lose access to PandaDoc, but their user record and license stay in your organization until you remove them in PandaDoc. A workspace owner cannot be removed from their own workspace; transfer ownership in PandaDoc first.
Workspace access. From a workspace's page in Ploy, you can add a person to the workspace with the role you choose, or remove them.
PandaDoc's API cannot change a license or a workspace role in place. To change someone's role, remove them from the workspace and add them again with the new role.
Before you start
PandaDoc's API needs an Enterprise plan, and PandaDoc must switch on production API access for your account. Contact PandaDoc if you do not have a production API key yet.
You need to be an Organization Admin in PandaDoc. The API key acts as the person who created it, and Ploy needs Organization Admin rights to read users and workspaces.
Know which region your account is hosted in: the United States (the default) or the European Union. If you sign in at app.pandadoc.eu, choose the European Union.
Create an API key in PandaDoc
Sign in to PandaDoc as an Organization Admin.
Open the Developer Dashboard from PandaDoc's API settings.
Generate a production API key. Treat it like a password.
The key stops working if the person who created it is removed from the workspace it was made in. Consider creating it from a dedicated admin account. Generating a new production key in the same workspace replaces the old one, so update Ploy if you do.
Connect PandaDoc in Ploy
In Ploy, open Integrations and choose PandaDoc.
Tick the beta consent checkbox.
Select your PandaDoc region.
Paste the production API key.
Optionally, choose the license people added by Ploy receive. eSign is used if you leave it empty.
On the next page, optionally choose the workspace people added by Ploy join. Leave it empty if Ploy should not add people to PandaDoc.
Test the connection and finish.
Ploy reads users and workspaces every hour. The first scan shows everyone with access.
Troubleshooting
PandaDoc refused that API key. Check the key was copied in full, that it is a production key, and that the region matches your account.
PandaDoc accepted the key but refused to list users. The key was not created by an Organization Admin. Create it again from an Organization Admin's account.
Adding a person fails with an email domain error. PandaDoc only accepts addresses on your organization's own domain.