Share with your org
Every project is either private to its creator or shared with the org.
New projects start private. Sharing is a deliberate act.
What each means
Section titled “What each means”| Who can see it | Who can change it | |
|---|---|---|
| Private | Its creator only | Its creator, and administrators |
| Org | Everybody in the org | Its creator, and administrators |
Note what does not change: sharing a project does not give everybody the right to edit it. It gives them the right to use it. Running somebody’s project is safe; editing it under them is not.
A project you cannot see answers “not found”
Section titled “A project you cannot see answers “not found””Not “forbidden”. That is deliberate: whether a colleague has a private project called Q4 migration attempt 3 is not something the API should let you probe for.
Which plans allow it
Section titled “Which plans allow it”Sharing is a plan feature. On a plan without it, projects stay private and an attempt to share is
refused with FEATURE_SHARED_PROJECTS.
The check is on the server, not in the wizard. That matters because the same projects are reached by the SDK and by an agent over MCP — a gate the widget honours and the API does not would not be a gate at all.
See Plans and limits.
When to share
Section titled “When to share”Share the ones that encode a decision the organisation has made:
- The monthly file from Finance, with its match rule.
- The vocabulary of a recurring import — which columns mean which fields.
- Anything you would otherwise explain to a colleague over their shoulder.
Keep private the experiments, the one-offs, and anything half-built. A shared project is implicitly a recommendation.
Projects from a configuration repository
Section titled “Projects from a configuration repository”A project pushed from a config bundle belongs to the whole org by design — that is what pushing it means.
Because pushing them is sharing, a plan without shared projects refuses a bundle that carries
any, rather than quietly importing them as somebody’s private ones. The error names the feature and
suggests removing projects/ from the bundle or upgrading.
Pushed projects carry where they came from, so re-pushing updates the same project rather than accumulating copies, and they never collide with a hand-made project that happens to share a name.
Deleting
Section titled “Deleting”The creator or an administrator can delete a project. Run history is kept — it records what happened, not what the project says now, and deleting the recipe should not erase the evidence of what it did.