# Neon now has per-project permissions

DevFeed: [Neon now has per-project permissions](<https://devfeed.tech/articles/neon-now-has-per-project-permissions-5669.md>)

Original publisher: [Read original article](<https://neon.com/blog/neon-now-has-per-project-permissions>)

Author: Russ Dias

Published: 2026-08-03T12:00:00Z

Content type: article

Language: en

Sources: [Blog -- Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [Authorization](<https://devfeed.tech/topics/authorization.md>), [Databases](<https://devfeed.tech/topics/databases.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [external](<https://devfeed.tech/tags/external.md>), [product](<https://devfeed.tech/tags/product.md>), [safety](<https://devfeed.tech/tags/safety.md>)

## AI overview

Neon introduces per-project permissions alongside four organization-level roles: Admin, Editor, Viewer, and Collaborator. The two permission layers combine to provide scoped access for users, agents, and external contributors, though project-level permissions currently only expand access and cannot restrict an organization-wide role.

## Source excerpt

Neon now supports a new permission structure, with four org-level roles (Admin, Editor, Viewer, and Collaborator) and per-project permissions that let you control exactly which projects your agents and collaborators can access.