Thread Visibility
Control who can see your threads with organization-wide and private visibility settings.
Threads in Sazabi have two visibility levels: organization (visible to all team members) and personal (visible only to you). This lets you control who can see your debugging sessions and investigations.
Visibility levels
Organization threads
Organization threads are visible to everyone in your Sazabi organization. Any team member can:
- See the thread in their sidebar under the "Organization" section
- Open and read the full conversation history
- Continue the investigation by sending new messages
- View all tool calls, artifacts, and findings
Use organization visibility when:
- Investigating a production incident that affects the team
- Documenting a debugging session for future reference
- Working on a problem where others might have context
- Creating threads that should be discoverable in search
Personal threads
Personal threads are visible only to you. Other team members cannot see them in their sidebar, search results, or anywhere else in the application.
Use personal visibility when:
- Exploring a hypothesis you are not ready to share
- Debugging a local development issue
- Working through a problem privately before sharing findings
- Creating scratch threads for quick lookups
You can always change a personal thread to organization visibility later if you want to share your findings with the team.
Default visibility
New threads default to organization visibility. This encourages knowledge sharing and makes it easier for teammates to discover relevant investigations.
When you create a thread from Slack, it also defaults to organization visibility so that team members can find related context when debugging similar issues.
Changing visibility
You can change a thread's visibility at any time using the visibility selector in the thread header.
Open the thread
Navigate to the thread you want to modify.
Click the visibility selector
In the thread header, click the dropdown showing the current visibility (either "Personal" or "Organization").
Select the new visibility
Choose "Personal" to make the thread private, or "Organization" to share it with your team.
The change takes effect immediately. If you move an organization thread to personal, it disappears from other team members' sidebars and search results.
Ownership and permissions
Only the thread owner (the person who created it) can change visibility settings. If you want to make a shared thread private again, you must be the original creator.
| Action | Who can do it |
|---|---|
| View organization thread | Any organization member |
| View personal thread | Only the owner |
| Change to personal | Only the owner |
| Change to organization | Only the owner |
| Continue conversation | Anyone who can view the thread |
How visibility affects features
Sidebar organization
The thread sidebar separates threads by visibility:
- Pinned: Pinned threads appear at the top regardless of visibility
- Personal: Your private threads, sorted by most recent activity
- Organization: Shared threads from all team members
This separation helps you quickly find your own work while still having access to team investigations.
Search and discovery
Visibility controls what appears in search results:
- Organization threads: Searchable by all team members
- Personal threads: Only appear in your own search results
When searching past investigations, you will see organization threads from all team members plus your own personal threads. You will not see other members' personal threads.
If you cannot find a thread you are looking for, check whether it might be set to personal visibility by another team member. Ask them to share it or change the visibility if the investigation is relevant to the team.
Forked threads
When you fork from a thread, the new thread inherits the visibility of the source thread:
- Forking from an organization thread creates an organization thread
- Forking from a personal thread creates a personal thread
You can change the forked thread's visibility after creation if needed.
Slack-initiated threads
Threads created from Slack mentions or commands use organization visibility by default. This makes sense because Slack conversations are typically team-wide, and the resulting investigation should be discoverable by other team members.
Best practices
Start with organization visibility
Default to organization visibility unless you have a specific reason for privacy. Shared threads:
- Build institutional knowledge
- Help teammates learn from your debugging process
- Make it easier to hand off investigations
- Create a searchable history of past incidents
Use personal for work in progress
Personal visibility is useful for exploratory work:
- Testing a theory before sharing conclusions
- Learning how to use a new feature
- Debugging issues specific to your local environment
- Quick lookups that do not need to be saved
Move to organization when ready
Once you have findings worth sharing, change the visibility to organization. This makes your investigation available to teammates who might encounter similar issues.
Consider future discoverability
When deciding on visibility, think about whether this investigation might help someone in the future. If you are debugging a tricky issue that others might encounter, organization visibility makes that knowledge findable.