Change who can read your sessions

Who can read a session is decided twice: once by your default when the session starts, and again whenever you change it on the session itself. Storing is separate; a hidden session is still stored

Your default audience

New sessions take the default from your active profile. The values:

Value	Who can read a new session
private	Only you
project	Members of the projects that hold the repository. Team and Enterprise plans
org_public	Everyone in your organisation, for the organisation’s own repositories; a session in a personal or unrecognised repository stays private
public	Anyone signed in to your workspace. Not the open web

kcap config set default_visibility org_public
kcap config show

Admins set which repository owners count as the organisation’s under Administration → General → Sessions

One session

In the web app, open the session from Sessions and choose Share in its header. The audiences offered depend on your plan and the repository’s projects:

• My default: inherit whatever your default was
• Org members: everyone in the organisation, as a deliberate choice that survives a change to your default
• Project members: members of the projects holding this repository; adding the repository to another project widens it
• Teams & people: only the teams and people you pick. Admins create native teams; a team grant follows the team’s membership, so adding someone to the team gives them every session shared with it
• Private: only you

Choose, add recipients if needed, and Apply. If the server is catching up, the change is saved and shows once it is done. A continuation chain is several sessions; share each segment that matters

How much they see

Where the Detail level selector is offered: Full includes the transcript and tool output; Activity shows what happened without the conversation; Overview shows the outcome and metadata. You always have full access to your own sessions. The same limits apply to what an agent can read through kcap’s tools on the reader’s behalf

What never grants access

A link. Knowing a session id. Being in the same repository. If someone outside the audience opens a session link they see “not available”, the same as for a wrong link

Further reading

• Hide a session narrows one to owner-only in a single step
• Keep private repos out decides what is stored at all