Client deliverables, legal work product, and audit evidence all need to move between people — but not everything in a conversation is meant for every reader. NuBench's shared conversations let you share exactly what you intend, with classification enforced at the moment of sharing and access revocable at any time.
Classification is locked at share time
Available now
The classification tier of a conversation is snapshotted when you share it. It cannot drift — even if you later escalate the source conversation.
If you share a CONFIDENTIAL conversation and later re-classify it to RESTRICTED, the share recipient's access is re-evaluated against their live classification clearance. No one receives content above their clearance level. The original classification at time of sharing is recorded in the audit trail.
Recipients can read and comment, but cannot prompt
Available now
Share recipients see the conversation and can leave comments. They cannot send messages, trigger inference, or incur any AI spend.
This is enforced at the gateway layer, not the UI layer. A share principal who calls the API directly will receive SHARE_INFERENCE_FORBIDDEN. Only the conversation owner and their collaborators can send prompts. Share access is completely separate from live collaborative session access.
Branch-scoped sharing
Available now
Share just a branch of a conversation — not the entire thread. Recipients only see messages within the shared branch's scope.
When you share a branch, the gateway enforces message scope: only messages up to and including the fork point, plus messages on the branch itself, are visible to the share recipient. Sibling branches are not visible. File attachments linked to out-of-scope branches are denied, not omitted silently.
Full audit trail for every share event
Available now
Every share creation, view, comment, and revocation is logged to the immutable audit trail with the actor's identity and timestamp.
Auditors and compliance teams can investigate exactly who accessed which conversation, when, and what they did. The Admin Console Shares page surfaces this data for investigation. GDPR Article 20 export includes share and comment records. Erasure requests cover share records in the same two-phase process as conversation data.
Revoke at any time — instantly
Available now
Revoke a share link and the recipient's access stops working on the next request. There is no grace period.
Revocation is checked on every API call, not only at share creation. A revoked principal receives SHARE_ACCESS_DENIED, not a 404 — so the access change is distinguishable from a missing resource in your logs. Supervisors and Super Admins can revoke any share within their hierarchy scope.
Share notifications
Available now
When you share a conversation, the recipient receives an in-app notification and an optional email — no separate link required.
The notification system delivers conversation_shared events via the nb-notify service. Recipients see the new share in their notification inbox and can click directly to the conversation. Email delivery uses SES with per-user preferences. All notification delivery is logged.