Project Access and public project snapshots are staged for dev acceptance.
This page describes the implemented controls, not a live production release.
Do not publish this page to the public docs site yet.
Give members access
New projects start private, with their creator as Manager. Other people must be active members of the same organisation and have an explicit project grant. Organisation roles alone, including owner or admin, do not give access to a private project.- Open the project and choose Project actions → Access.
- As a Manager, select an Organisation member and a Project level.
- Choose Review change, check the person and level, then Yes, set access.
To change a level, repeat those steps. To remove access, choose Remove explicit
grant, then Review change and Yes, remove grant. The person loses access
to the private project, not their organisation membership. You cannot change
your own level here, and the last Manager cannot lose access through grant editing.
Project access does not give control of personal conversations, computers,
connectors or funding. Author-specific rules for published sessions and runs
still apply. Removing a grant cannot recall downloaded copies or revoke public
links: revoke those links separately.
Make an existing project private
Existing projects that show Organisation inheritance keep access through organisation roles. Owners and admins can manage them, members can write, and viewers can read. In Access, choose Make private…, review the explanation, then Yes, make private. Current members keep their effective roles as explicit grants: viewers become Viewers, members become Editors, and owners and admins become Managers. Future organisation members no longer inherit access. This action does not remove current members or revoke public links, and cannot be reversed here. Remove individual grants afterwards if needed.Share a project snapshot
A project Manager can create and revoke public project links. For projects with organisation inheritance, the organisation owner or an admin manages these links. Editors and Viewers cannot create or revoke them.- Choose Project actions → Share project.
- Select the published reports to include. Check the revision shown beside each report; the link pins those exact revisions.
- Choose 7, 30 or 90 days. Leave Include the project brief unchecked unless you want to disclose it too, including its goal, labels and preview rows.
- Review the selection and disclosure text, choose Create public link, then copy the link.
Share one report
The existing report-sharing flow remains separate from Share project. People who can write to the project can create, copy and revoke report links, including Editors on private projects.- Open the report revision and choose Share link, or Share report in Outputs.
- Choose 7, 30 or 90 days, then Create share link and copy it.
Share a session from the terminal
Run/share in a session. The agent asks which project to use if needed, shows
the title, summary and selected messages, and waits for approval before
publishing. Tool output, secrets and private paths are left out.
It then asks how long the public link should last. That link contains only the
published session, not the brief, sibling reports or files. Ask the agent to
revoke it to end access before expiry.