Neon now has per-project permissions
Blog post from Neon
Neon has introduced a new permission structure featuring org-level roles and per-project permissions to enhance access control for agents and collaborators. This update addresses the limitations of the previous system where a single role was applied uniformly across all projects in an organization, which was suitable for small teams but inadequate for managing databases at scale. The new model allows for more granular access by combining baseline org-level roles—Admin, Editor, Viewer, and Collaborator—with project-specific permissions that can extend access on particular projects. This dual-layered approach ensures that agents can manage projects effectively, reducing the risk of over-permissioned keys and improving safety management. This structure also facilitates developer collaboration by enabling specific project access without exposing the entire organization's resources. While current Neon users will retain their existing access levels, the traditional project collaboration feature will be phased out in favor of the new system, which will soon be available for Vercel Managed Integration users.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.