Shared Chats

Overview

Shared Chats lets a chat owner share an immutable snapshot of a conversation with authenticated colleagues. Recipients open a read-only view of the chat exactly as it existed when the link was created, and can optionally continue that snapshot as a new private chat in their own history.

Use it when you want to share the answer with a colleague, validate a draft, or allow a colleague to pick up from a finished conversation without re-running the same prompts.

At a glance

• Owners share from the chat header, pick users and/or groups, confirm the chat is appropriate to share, and copy a unique link.

• Each copy creates a new link which generates a snapshot at that point in time. Older links stay valid and the snapshot unchanged even if the conversation continues.

• Recipients must be logged in. Uploaded files appear as locked file names (not viewable or downloadable). Knowledge-base references only open when the recipient independently has access.

• Who can be invited is governed by the company sharing policy (spaceMembers or allCompany). Set the policy to disabled to turn Shared Chats off for the whole company.

How it works for chat owners

1. Open a chat you own in a space where Shared Chats is enabled.

2. Select Share in the chat header.

3. Search for and select users and/or groups allowed by your company policy.

4. Confirm that the chat does not contain sensitive data you should not share.

5. Copy the share link and share it outside the platform (email, Teams, Slack, etc.).

6. Manage access later from the same dialog: see and revoke access as needed.

Snapshot rules

How it works for recipients

1. Open the shared link while logged in to Unique.

2. View the read-only snapshot — prompts, answers, and references — up to the snapshot cutoff.

3. Optionally select Continue. Unique creates a new private chat in your history. From that point, the continued chat belongs only to you.

What recipients can and cannot see

Enabling Shared Chats

Sharing stays hidden until the following are set.

The company policy defaults to on, so a new company only needs the space toggle. The space toggle is hidden when the policy is disabled.

See also: 2026.34 Infrastructure Changes.

Company sharing policy values

Setting chatSharingPolicy

There is no admin UI for the company policy yet. A company administrator sets it through the companyUpdateData GraphQL mutation on the standard GraphQL endpoint.

Requirements

• The caller must have the chat.admin.all role and the company / write permission. If the permission is missing, the request returns Forbidden even for a chat.admin.all user — grant the permission rather than looking for a different role.

• The change applies to the administrator's own company.

• The update overwrites the entire configuration object (it does not merge). Always read → merge → write.

Read the current configuration

query CompanyConfiguration {
  company {
    id
    configuration
  }
}

This query returns the stored configuration blob, not the effective policy. If chatSharingPolicy is absent, the effective policy is spaceMembers. Absence does not turn sharing off.

Write the merged configuration back

mutation CompanyUpdateData($input: CompanyUpdateInput!) {
  companyUpdateData(input: $input) {
    id
    configuration
  }
}

Variables — take the object returned by the read, add or change chatSharingPolicy, and send the whole object back:

{
  "input": {
    "configuration": {
      "referenceStyle": "style1",
      "chatSharingPolicy": "disabled"
    }
  }
}

Space-level control

After the company policy is set, enable Shared Chats per space:

1. Open Admin → the space.

2. Go to Advanced settings.

3. Turn Shared Chats on.

Company policy still defines the audience (who can be invited). The space toggle only controls whether sharing is offered in that space.

Security and governance

• Recipients must be authenticated — there are no anonymous public links.

• Access is limited to the people and groups the owner selected for that link.

• Owners can revoke access per recipient at any time.

• Uploaded-in-chat files are never downloadable for recipients (name only).

• Knowledge-base references respect the recipient's own access.

• Owners remain responsible for not sharing confidential or CID content. Unique does not detect sensitive content inside a chat.

Troubleshooting

Limitations