Looking for the previous documentation?Go to v1.docs.pluggy.ai

Team access

The roles of a Pluggy Dashboard team, what each one can do with your applications, secrets and webhooks, and how to keep access to the people who need it.

View as Markdown

Your team's members manage the applications that hold your credentials, so who is on the team, and with which role, is part of your security. A team has three roles: OWNER, ADMIN and MEMBER.

What each role can do#

Action in the DashboardOWNERADMINMEMBER
See applications and list their webhooksYesYesYes
Create applications and edit their name, description and originsYesYesNo
Generate a new client secretYesYesNo
Create, update and delete webhooksYesYesNo
Set a webhook's custom headersYesNoNo
Generate, regenerate or remove the webhook signing secretYesNoNo
Enable or disable an applicationYesNoNo
Delete an applicationYesNoNo
Change the Pluggy Connect customizationYesYesNo
Invite members, change their roles and remove themYesYes, except OWNERsNo
Make someone an OWNERYesNoNo
See billing and submit the due diligenceYesYesNo
Delete the teamYesNoNo

An ADMIN can invite and manage ADMINs and MEMBERs, but cannot invite or promote anyone to OWNER, and cannot change the role of an existing OWNER or remove one.

These rules apply to the Dashboard. Anyone who holds the application's client secret or an API key can do everything the API allows, whatever their role: see Credentials.

Least privilege#

  • Give OWNER to few people. An OWNER can disable and delete applications, manage the webhook signing secret and hand out OWNER to others.
  • Give ADMIN to the people who operate the integration. An ADMIN can generate a new client secret, and with it, read the new secret.
  • Everyone else is a MEMBER. A MEMBER can follow the integration in the Dashboard without changing applications, secrets or webhooks.
  • Keep at least two OWNERs if your team should survive one person leaving. A team whose last OWNER closes their Pluggy account is deleted with it; see Deleting your Pluggy account.

When someone leaves#

  1. Remove them from the team in the Dashboard. To remove an OWNER, another OWNER has to do it.
  2. Rotate the client secret of every application whose secret they could have seen: an OWNER or ADMIN who generated one, or anyone who could read your secrets manager. Removing a member does not change the application's credentials. See Rotate the client secret.
  3. Regenerate the webhook signing secret and the secret in your webhooks' headers if they had access to them. See Rotating the secret.

API keys created before a rotation keep working until they expire. If you need to cut them off sooner, see If a credential leaks.

Does not protect against#

  • A secret copied out of the Dashboard: roles control who can generate or change it, not where it goes afterwards.
  • Access through the API: it is governed by your credentials, not by team roles.

Next: Data protection.

Was this page helpful?