# Team access

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 `OWNER`s | 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 `ADMIN`s and `MEMBER`s, 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](/docs/security/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 `OWNER`s** 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](/docs/get-started/delete-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](/docs/security/credentials#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](/docs/developer-tools/webhook-security#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](/docs/security/credentials#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](/docs/security/data-protection).