Sharing Threads

When you find something important during an investigation, you can share the thread with teammates. They see the full conversation history, including tool calls and artifacts, giving them complete context.

Sharing options

Sazabi provides several ways to share thread content depending on your audience and use case.

Copy thread link

The simplest way to share a thread with teammates in your organization:

1. Right-click the thread in the sidebar, or click the three-dot menu.
2. Select Copy link.
3. Paste the link in Slack, email, or any other communication channel.

Team members who click the link see the full thread, including all messages, tool calls, and artifacts. They can continue the conversation or use it as context for their own investigations.

Share a message permalink

To link to a specific message within a thread:

1. Hover over the message you want to share.
2. Click the share icon in the message actions bar.
3. The permalink is copied to your clipboard.

When someone opens the link, the thread opens and scrolls directly to that message. This is useful for highlighting specific findings or tool output.

Create a public snapshot

For sharing outside your organization, you can create a public snapshot:

1. Right-click the thread or click the three-dot menu.
2. Select Share.
3. Choose Create public link.
4. Copy the generated URL.

Public snapshots are read-only copies of the thread at the moment you create them. Anyone with the link can view the snapshot without signing in.

Access control

Thread sharing respects the visibility settings of the original thread.

Changing visibility before sharing

If a thread is private but you want teammates to access it:

1. Right-click the thread in the sidebar.
2. Select Move to Organization.

The thread becomes visible to all organization members, and internal links start working for teammates.

To make an organization thread private again:

1. Right-click the thread.
2. Select Move to Personal.

Slack integration

When your organization has connected Slack, Sazabi automatically unfurls thread links with rich previews.

How link unfurling works

1. Paste a Sazabi thread link in any Slack channel where the Sazabi app is installed.
2. Slack displays a preview card showing:
   • Thread title (or first message preview)
   • Project name
   • Organization name
   • Creation date

Team members can click the preview to open the full thread in Sazabi.

Starting conversations from Slack

Beyond sharing links, you can start new threads directly from Slack by mentioning @Sazabi in any channel where the app is installed. These conversations sync bidirectionally, so team members can continue them in either Slack or the dashboard.

See Threads Overview for details on starting threads from Slack.

Privacy considerations

When sharing threads, keep these privacy aspects in mind:

Internal links

• Require organization membership to access
• Respect thread visibility settings
• Full conversation history is visible to viewers

Public snapshots

• Accessible to anyone with the URL
• Include all messages and tool output from the snapshot time
• Do not update when new messages are added
• Can be revoked by removing the public link

Slack unfurls

• Only show preview metadata (title, project, date)
• Full content requires clicking through to Sazabi
• Respect the same access controls as direct links

Best practices

Use internal links for team collaboration. When working with teammates on an incident, share internal thread links. They maintain access control and always show the latest state of the conversation.

Create public snapshots for external sharing. When you need to share findings with stakeholders outside your organization (vendors, customers, external partners), use public snapshots.

Update snapshots after significant findings. Public snapshots are frozen at creation time. If the investigation continues and produces important new findings, update the snapshot so external viewers see the complete picture.

Review before making public. Threads often contain raw log data, stack traces, and system information. Verify the content is appropriate for public sharing before creating a snapshot.