> This page location: Neon platform > Access & collaboration > User permissions
> Full Neon documentation index: https://neon.com/docs/llms.txt
> IMPORTANT: If this page contains inaccurate or outdated information, report it: POST to https://neon.com/api/docs-feedback with {"feedback": "describe the issue", "path": "/docs/manage/user-permissions"}

# User Permissions

What each role can do in Neon organizations

In Neon, roles determine what actions you can take within an organization and its projects. This page provides a detailed breakdown of permissions for each role: **Admin**, **Member**, and **Collaborator**.

For an overview of organizations, see the [Organizations](https://neon.com/docs/manage/organizations) page.

## Role descriptions

- **Admin**: Full control over the organization and all its projects. Can manage permissions, billing, members, and organization settings. Only Admins can delete organization projects.
- **Member**: Access to all organization projects and can perform most project operations, but cannot modify organization settings or delete projects.
- **Collaborator**: External users invited to specific projects. Collaborators have no organization-level access, but can work on projects they've been invited to.

## Organization management

The following table shows what each role can do at the organization level:

| Action                                   | Admin | Member | Collaborator |
| ---------------------------------------- | :---: | :----: | :----------: |
| Invite organization members              |   ✅   |    ❌   |       ❌      |
| Set organization permissions             |   ✅   |    ❌   |       ❌      |
| Manage organization billing              |   ✅   |    ❌   |       ❌      |
| Rename organization                      |   ✅   |    ❌   |       ❌      |
| Delete organization                      |   ✅   |    ❌   |       ❌      |
| Enable organization Early Access Program |   ✅   |    ❌   |       ❌      |

## Project management

The following table shows what each role can do at the project level:

| Action                       | Admin | Member | Collaborator |
| ---------------------------- | :---: | :----: | :----------: |
| Create new projects          |   ✅   |    ✅   |       ❌      |
| Rename projects              |   ✅   |    ✅   |       ✅      |
| Transfer projects into org   |   ✅   |    ✅   |       ❌      |
| Transfer projects out of org |   ✅   |    ❌   |       ❌      |
| Delete projects              |   ✅   |    ❌   |       ❌      |
| Manage project databases     |   ✅   |    ✅   |       ✅      |
| Configure project computes   |   ✅   |    ✅   |       ✅      |
| Manage project roles         |   ✅   |    ✅   |       ✅      |
| Invite/remove collaborators  |   ✅   |    ✅   |       ✅      |

## Integration management

The following table shows what each role can do regarding integrations:

| Action                                               | Admin | Member | Collaborator |
| ---------------------------------------------------- | :---: | :----: | :----------: |
| Install GitHub integration                           |   ✅   |    ❌   |       ❌      |
| Install Neon Auth                                    |   ✅   |    ❌   |       ❌      |
| Install the Vercel-managed Neon integration\*        |   ✅   |    ❌   |       ❌      |
| Connect project to GitHub integration                |   ✅   |    ✅   |       ❌      |
| Connect project to Neon-managed Vercel integration\* |   ✅   |    ✅   |       ❌      |

*Neon's Vercel-managed integration is managed entirely in Vercel and uses Vercel's permission system. For the Neon-managed Vercel integration, projects must first be made available in Vercel before they can be connected to Neon.

## Snapshot management

The following table shows what each role can do with [snapshots](https://neon.com/docs/guides/snapshots):

| Action                       | Admin | Member | Collaborator |
| ---------------------------- | :---: | :----: | :----------: |
| List snapshots               |   ✅   |    ✅   |       ✅      |
| Create snapshots             |   ✅   |    ✅   |       ✅      |
| Restore snapshots            |   ✅   |    ✅   |       ✅      |
| Delete snapshots             |   ✅   |    ✅   |       ✅      |
| Rename snapshots             |   ✅   |    ✅   |       ✅      |
| View snapshot schedule       |   ✅   |    ✅   |       ✅      |
| Set/update snapshot schedule |   ✅   |    ✅   |       ✅      |

## Notes and limitations

- **Branch management**: All users are currently able to manage [protected branches](https://neon.com/docs/guides/protected-branches), regardless of their role or permission level. Granular permissions for this feature are not yet implemented.
- **Permissions and roles**: The current permissions system may not meet all needs for granular control. Share your feedback and requirements for more detailed permissions settings via the [Feedback](https://console.neon.tech/app/projects?modal=feedback) form or our [Discord feedback channel](https://discord.com/channels/1176467419317940276/1176788564890112042).

---

## Related docs (Access & collaboration)

- [Accounts](https://neon.com/docs/manage/accounts)
- [Organizations](https://neon.com/docs/manage/organizations)
- [Project collaboration](https://neon.com/docs/guides/project-collaboration-guide)
- [Database access](https://neon.com/docs/manage/database-access)
- [API keys](https://neon.com/docs/manage/api-keys)
- [Account recovery](https://neon.com/docs/manage/account-recovery)