Privacy, Sharing, and Collaboration

Visibility determines whether the wider community can interact with the object. Public problems and papers are discoverable and can attract comments, reviews, votes, and sharing. Private objects are restricted to owners, admins, collaborators, and any users who redeemed a valid share workflow where supported.

The visibility toggle is intentionally explicit because publishing changes who can interact with the work and how much of the surrounding discussion becomes durable.

• Share links are a private-viewing workflow. A recipient must sign in and redeem the link before access is granted.
• Collaborators are an editing and run-access workflow. They see the project in their own workspace context and receive collaboration notifications.
• Redeemed viewers and collaborators are tracked separately so owners can tell who merely accessed a shared private asset versus who joined the working team.

Once a collaborator is added, they can be surfaced in the Team panel and notified that access was granted. This is the right model for recurring joint work, not one-off review visibility.

For private papers, a shared state can still allow signed-in members who redeem the link to review and discuss the paper without making it fully public. That is useful when you want distributed critique before publication.