Project access determines who can enter an ordinary project. Session visibility determines which conversations inside it they can read. Neither setting publishes the workspace anonymously to the internet.
#Set project visibility
Open the chevron beside the project name in the workspace header and choose Manage Access. This opens Project Access in account mode.
- Confirm the exact project and owner.
- Open Manage Access from that project's header menu.
- Choose Private or Public.
- For a private project, select Allowed Users.
- Reopen/check the saved state and have the recipient verify access.
Public ordinary projects are available to authenticated workspace users under the server's rules. Private projects require ownership or an explicit grant. Only the valid owner can change sharing; administrator role alone does not supply content ownership.
If no other users are available, create or invite accounts first. A link cannot substitute for an account grant.
#Set new-session defaults
Open the project header menu, then Project Settings → Access → New session visibility. The owner can choose Private or Shared with project members.
This applies to new ordinary project conversations and Issue Start work sessions. Existing sessions, hidden work, and delegated workflows keep their current visibility. Administrators can view the default but cannot change it for another owner.
Worktrees inherit this default from their parent; change it in the parent project.
#Share a particular conversation
Inspect that session's own privacy/sharing controls. A public project does not override a private conversation. Project ownership transfer also does not transfer private session ownership.
For collaborative work, create an appropriately shared conversation and summarize the necessary context there. Keep owner-private Mate or Me information out of it unless deliberately shared.
#Revoke or diagnose
Remove an exact grant when it should no longer apply. Access revocation can close existing connections, and reconnect checks current authorization.
If access persists for a worktree, inspect parent inheritance. An inherited Entire project grant cannot be removed only from a child worktree. See Worktree sharing.
If the UI says Ownership needs recovery, ask the server operator to investigate the account and directory ownership. Content stays disabled until that is resolved; changing a sharing checkbox cannot repair it.
For account roles and underlying OS authority, see Users and roles. For conversation privacy, see Session privacy.