Sharing and access

Sharing gives another team access to a thread, folder, or category without moving ownership. Your team stays the owner; the other team sees the item in their Shared view and can open it with the role you granted. That makes sharing the collaboration tool — to hand items over for good, use a shipment instead.

Sharing and shipping both move data over a Connection, but they are different acts: a share is a window into your live Thread; a shipment hands the receiving team their own copy.

Note

Sharing availability depends on your organization’s configuration — if you don’t see a Share button or a Shared section in navigation, it isn’t enabled for your team. See the FAQ.

Who you can share with

• Teams in your own organization — always available, no setup required.
• Teams in other organizations — only after your organizations are linked by a connection, and only if the connection’s data-flow direction lets your team send. When it doesn’t, the team appears in the share dialog but is disabled with the reason “Connection does not allow sharing data with this team.”

Roles

Each share grants one role, chosen from the Relation picker:

Role	What it allows
Viewer	Open the item and read its data.
Editor	Open the item and make changes.

Share a thread, folder, or category

1. Open the item and click Share in its header (on items you can’t manage, the button reads Access instead — see below).

2. In the dialog, find “Share with a connected team” and select one or more teams. Teams that already have a direct share are managed in the access list instead; a team that only inherits access shows “Already inherits access — sharing adds a direct grant.”

3. Pick a role in the Relation picker for each selected team.

4. Click Share. A confirmation such as “Thread shared” appears, and the item shows up in the other team’s Shared view.

Folders and categories share everything inside

The dialog reminds you of the blast radius: “Anyone you share this folder with can open everything inside it — all threads and subfolders.” and “Anyone you share this category with can open every thread in it, including threads in its subcategories.”

The Access view

The same dialog is dual-mode:

• If you can manage sharing on the item, it opens as “Share …” with the description “Manage access to this thread.” (or folder/category) and shows the full share controls.
• If you can’t (for example, you’re a viewer or editor on a thread another team shared with you), it opens as a read-only access summary — “Thread access” — with the note “Read-only — only teams who can share this thread can change who has access.”

Both modes show the “Who can access” list: “Everyone who can open this thread, and how.” Each team entry is labeled with how it got access:

• Owner — the owning team (“Owns this thread”).
• Shared directly — a direct grant, shown with its role, e.g. “Shared directly · Viewer”.
• Inherited from … — access that flows from a container, e.g. “Inherited from folder “Receiving” · Editor“.

Inherited access

Sharing a folder, category, or assembly automatically extends access to what’s inside it. On an individual thread, the Access view shows these grants as “Inherited from” the folder, category, or assembly they come from.

Inherited access can’t be removed on the thread itself — remove or change the share on the container instead. If a team has both a direct share and inherited access, removing the direct share keeps the inherited access; the dialog warns: “Removing the direct share won’t revoke access — still inherited from …”, and the confirmation reads “Direct share removed — inherited access remains”.

The Shared page

The Shared entry in navigation opens two tables:

• “Shared with team” — “Items that others have shared with you.” Columns include Item, Permission, Shared By, and Owner. This is where anything a partner team or a sibling team granted you appears.
• “Shared” — “Items you have shared with others.” Columns include Item, Permission, and Shared With, so you can audit everything your team has granted out.

Both tables are searchable by item name.

Suspended shares

Cross-organization shares depend on the connection between the two teams. A share can become suspended in two ways:

• Connection paused — the share is labeled “Suspended — connection paused”: “The connection is paused, so this share is suspended and can’t be edited. It resumes automatically when the connection is resumed.”
• Direction no longer allows it — the share is labeled “Suspended — direction not permitted”: “The connection no longer allows sending data to this team, so this share is paused and can’t be edited. Update the connection direction to restore it.”

While suspended, the other team loses access, but nothing is deleted — restoring the connection (resuming it, or amending its direction) restores every suspended share automatically.

Unshare

In the manage view of the dialog, use Manage next to a team and choose Remove direct share. The confirmation reads “Thread unshared” (or folder/category). Remember that inherited access survives — revoke it at its source container.

Related

ConnectionsLink your team with a partner organization before sharing across org boundaries.

ShipmentsTransfer ownership of threads to another organization instead of sharing access.

ThreadsThe items you share: threads, their fields, files, and identifiers.