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 Dashboard | OWNER | ADMIN | MEMBER |
|---|---|---|---|
| See applications and list their webhooks | Yes | Yes | Yes |
| Create applications and edit their name, description and origins | Yes | Yes | No |
| Generate a new client secret | Yes | Yes | No |
| Create, update and delete webhooks | Yes | Yes | No |
| Set a webhook's custom headers | Yes | No | No |
| Generate, regenerate or remove the webhook signing secret | Yes | No | No |
| Enable or disable an application | Yes | No | No |
| Delete an application | Yes | No | No |
| Change the Pluggy Connect customization | Yes | Yes | No |
| Invite members, change their roles and remove them | Yes | Yes, except OWNERs | No |
Make someone an OWNER | Yes | No | No |
| See billing and submit the due diligence | Yes | Yes | No |
| Delete the team | Yes | No | No |
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
OWNERto few people. AnOWNERcan disable and delete applications, manage the webhook signing secret and hand outOWNERto others. - Give
ADMINto the people who operate the integration. AnADMINcan generate a new client secret, and with it, read the new secret. - Everyone else is a
MEMBER. AMEMBERcan 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 lastOWNERcloses their Pluggy account is deleted with it; see Deleting your Pluggy account.
When someone leaves#
- Remove them from the team in the Dashboard. To remove an
OWNER, anotherOWNERhas to do it. - Rotate the client secret of every application whose secret they could have seen: an
OWNERorADMINwho 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. - 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.
