External contributors
Give a contractor access to one project without adding them as an organization member.
Neon · Const
Project sharing
Project sharing lets a project owner invite external Neon accounts to collaborate on one project through the Console, API, or CLI. It does not grant organization membership or project-deletion rights.
How it works
Project sharing lets a Neon project owner invite external Neon accounts to access one project through the Console, API, or CLI. Shared users can work on the project but do not gain organization membership or project-deletion privileges.
Syntax
neon projects list --sharedReturns
A collaborator invitation grants the invited Neon account access to the selected project; the account is not added to the organization and cannot delete the project.
Key points
- Project owners can grant other Neon users access to an individual project.
- The shared project can be accessed through the Console, API, and CLI.
- Invitees need an existing Neon account before they can collaborate.
- The invitation form accepts multiple comma-separated email addresses.
Common mistakes
- Project sharing is deprecated; use organization-based collaboration with the Collaborator role and per-project permissions instead.
- Invited collaborators cannot delete the shared project.
- A collaborator may be able to invite additional users, so review the collaborator list after invitations.
Example: List shared projects
neon projects list --sharedLists projects shared with the authenticated Neon account.
When to use it
Project-scoped collaboration
Let a teammate work on a specific Neon project while keeping billing with the owner.
CLI discovery
Inspect projects shared with the authenticated account from a terminal.
Interview questions
QWhat is Neon project sharing?
Project sharing gives an external Neon account access to one project through supported Neon interfaces such as the Console, API, and CLI. It does not add that account to the owning organization.
Follow-up: What should replace it? Use an organization Collaborator role and grant the required per-project permission.
QHow do you invite a project collaborator?
The owner opens a project, goes to Settings, chooses Collaborators, selects Invite, and enters the invitee's email address. Multiple email addresses can be entered as a comma-separated list.
Follow-up: What must the invitee have? They need a Neon account, either on the Free plan or a paid plan.
QWho pays for a shared project's usage, and what access is granted?
Shared-project usage counts against the project owner's plan allowances, and costs are billed to the owning account. The shared user receives project access but not project-deletion privileges.
Follow-up: How can access be made more granular? Move to organization membership plus per-project permissions, selecting the lowest organization role that covers the person's normal work.
Related
project collaborationCollaboratorproject permissionsNeon ConsoleNeon APINeon CLI