Sharing projects with a team.
Grant a whole org or team access to a project in one step — and never re-share when someone joins. Access follows membership, so the group stays current on its own.
The idea
Instead of adding collaborators one email at a time, you grant the project to an organization or team, and every current member inherits access. People added to the group later get it automatically, because the grant points at the group, not at a fixed list of people. Remove someone from the group and their access to the project goes with them. There’s nothing to clean up by hand.
How to share with a group
Sharing happens on the web dashboard, on a project that’s already published — not from the desktop app, and not from the org page.
- Build your project in the Orchid desktop app and publish it to Orchid Cloud.
- Open the project on the web dashboard and open its Share dialog.
- Pick the org — that’s everyone in it — or a specific team inside the org.
- Choose an access tier (below).
- Grant. Everyone in the group has it from that moment on.
Access tiers
Each grant carries one tier:
- View — read the project.
- Comment — read, plus leave comments.
- Execute — run cells and use the agent, without saving edits.
- Edit — change the notebook and save.
- Full — edit, plus manage who the project is shared with.
Access is additive. If someone is reached by more than one grant — say they’re in the org at View and also on a team you gave Edit — the most permissive one wins. There is no “deny” that takes access away.
Two guardrails
- You can only share a project into an org or team you yourself belong to.
- Only someone with Full access on a project can change who it’s shared with.
Team projects
You can also start fresh inside a team. On a team’s Projects tab, a manager (a team lead or an org owner/admin) clicks New project to create a blank project that’s shared with the team the moment it’s made — no separate publish-and-share step. Everyone on the team sees it in the same list right away.
Querying shared data together
A project shared with a team pairs naturally with that team’s shared connections and environment variables. Teammates open the project and query the same database from the Orchid desktop app — without swapping passwords. The credential is brokered to the app at run time and never shown; nobody copies a service-account password around to make a teammate’s copy work.
Share the project and the team’s connection as a pair. Then a new hire opens the published project, the connection is already visible to their team, and they’re running queries the same day — no credential handoff.
Staying in sync
Nobody should have to ask “who has access?” or “what changed?” The org and team Activity feed shows who joined, role changes, and connection checkouts. Metrics summarize that activity and the group’s membership over time. Metrics reflect what the group is doing, not a compute or billing meter — notebooks run on each person’s own machine.
Where to next
- Organizations — what an org is and how to set one up.
- Teams — subsets of an org with their own roster and roles.
- Publishing — get a project into Orchid Cloud first.
- Permissions — how tiers and roles decide who can do what.