Organizations & collaboration · 13 min read · Updated 2026-07-30

What can teammates see when I share an Agent task?

Choose a sharing level, understand what recipients can see, who owns a fork, and how to stop sharing.

Agent researched a task, changed files, and produced a table. A teammate wants to take over or repeat the process. A screenshot is not enough; you need toshow them the task itself.

In TabTin, this is called Shared task. The recipient opensyour actual task, not a copy. If Agent is still working for you, their view updates live.

This is the primary way teams work with Agent:share tasks, not personas. A teammate views your task or forks a copy, then continues with their own AI persona and workspace.

First: sharing applies to one task

The shared object is onetaskbetween you and Agent—in other words, one conversation or session. It is not a folder, workspace, or entire Project.
You can share only with teammates in the same organization. TabTin does not create a public link that anyone can open. The recipient must already belong to your current organization.
Only the task creator can share it. You cannot reshare someone else's task to a third person. To share onward, fork it into your own task first, as explained below.
Shares are delivered through direct messages. After sharing, the system sends adirect messagecontaining a shared-task card. The recipient opens the task from this card. Group chats have no sharing entry and show Not supported in group chats.

If the top bar shows Personal account, the member list is empty because a personal account contains only you. Create a team organization and invite colleagues first.

Two entry points

Share from the task (most common)

Open the task
Find theupper-right of the task headerand click theadd-person icon(tooltip: “Share with teammate”)
Open the Shared task dialog
Search for and select a teammate
Choose Sharing level(explained in the next section)
Click Send to XXX

Success shows Shared and sent by direct message.

This area is hidden when the window is too narrow. Widen it to reveal the control.

Share from a direct message

Open yourdirect message
with the teammate and click the +
Choose Shared task(description: “Choose one of your tasks to share”)
Choose one of your tasks from the list; titles are searchable
Select a level → click Share

Each task row showswho already has access, reducing duplicate shares.

Sharing levels: what recipients can do

The dialog currently offers Sharing level two levels:

Level	What they can do	What they cannot do	Best for
Live view	Open your task and follow the complete process live: your messages, Agent replies, tool calls, and produced docs or tables	Cannot send messages, operate your workspace, or copy the task	Show a manager or another team the process and result without enabling changes
View & fork	Everything above,plusfork the task into their own task and continue	Still cannot send messages in your task or operate your workspace	Let a teammate take over an investigation or reuse a proven workflow

Hover descriptions say “Follow task progress without operating the workspace” and “View live and copy into your own task to continue.”

A third level, View & participate, would let the recipient direct Agent inside your task while execution, approvals, and costs stay with you. This levelis not available in the current app. Do not design a workflow around it.

Exactly what recipients can see

The direct answer to the most common concern:The full task is visible inside the organization, without redaction.

They can see:

The task'scomplete message timeline—every message you sent and every Agent reply
Agent activity: tools called, file paths read or written, and steps performed
Produced TabDoc documents and TabData tables cards
Live updates: when Agent is still working for you, their view updates without manual refresh

They cannot see or do:

Access your execution workspace: recipients cannot browse or operate your workspace directory, terminal, or local files. They only read the task record
Send messagesat either current level, so they cannot drive your task
Reshare itto a third person
High-risk actions that require yourapproval; approval cards still appear only for you

There is one side effect: Explicitly delivered TabDoc documents and TabData tablesautomatically give the recipientread-onlyaccess so their cards open successfully. After sharing,newly produceddocs and tables receive the same grant when the recipient next opens the share card. The resource must belong to the same organization and you must have sufficient permission. Existing Editors are not downgraded.

Therefore:review the task before sharing. If it contains another customer's information, another Project, or personal data, reconsider before sending. There is no option to share only the later part.

What happens after the recipient forks?

The answer:The two tasks become largely independent.

How they fork: At the top of the shared task, click Fork into my tasksand complete two steps:

Step 1 · Choose an executing Agent from their organization
Step 2 · Choose a workspace (their ownpersonal workspace, shown with name and directory)
Confirm → Shared copy created, then the new task opens automatically

What the copy contains:

The new title is Original title (Shared copy)
Its content is asnapshot: messages from both sides, thetool namescalled by Agent, and attachment references whose file IDs allow Agent to read the full content
It excludes Agent thinking and raw tool inputs or results. A fork is a clean starting point for continuing, not a full export
For very long tasks, the snapshot is truncated:recent content is kept and the oldest removed(Agent is told that the snapshot is incomplete and does not treat it as the whole record)

Where it runs and who pays:

The copy lives inthe recipient's workspaceusingtheir selected Agentontheir own computerfor execution
Yourexecution workspace does not transfer. Your directories, device, and file outputs stay with you. They need separate access to any required files
Because sharing happens inside one organization, later usage is charged tothat organization. Execution and approval cards belong to the recipient and no longer interrupt you

Do the tasks affect each other?

You cannot see what they do after forking. It is an independent task under their account, and the app has no View copy entry for you
Your later progress does not flow into their copy. It is a snapshot from the moment of the fork and no longer syncs
As long as the original share remains active, they canreturn to the original task for a live view(forking and viewing are independent, not mutually exclusive)
Each click of Forkcreates a new copy; it never overwrites the previous one

Stop, resume, or change access

Stop sharing

You can stop sharing from any of these three places:

Task header: click the row of avatars in the top right → Manage sharing → click Stop
the shared-task card in your direct message: click Stop sharing
The top of the open shared-task page: click Stop sharing

A confirmation dialog appears. Once confirmed, you will see Sharing stopped, and the card in your direct message changes to Stopped. If the recipient opens it again, they will see Sharing has stopped or you do not have access.

What stopping a share does—and does not—revoke

Item	After sharing stops
The recipient's access to this task	Revoked; access ends immediately
Copies the recipient has already forked	Not revoked; those copies are now their own tasks
Read-only document and table access granted automatically when you shared	Not revoked automatically; remove it separately in that document or table's sharing settings

That last point is easy to miss:Stopping a share does not revoke access to its outputs. If the task delivered a sensitive document or table, remove the recipient from that resource after you stop sharing the task.

Resume sharing

To restore access after stopping it, openTask header → Manage sharingand click Restore, or click Resume sharingon the shared-task card in your direct message. The access level stays the same. Resuming sharingupdates the original card back to Sharing; it does not add another message.

Change the access level

There is no separate Change access button. Instead,share the task with the same person againand choose the new level; it replaces the old one. This time, your direct message will receivea new card(the old card remains, but its status updates with the share).

See who has access

The row ofstacked avatarsin the task header shows the current recipients. Open Manage sharing to see the full list, each person's access badge, and stopped shares shown in gray as Stopped.

In a direct message, the canvas sidebar also has a Share conversation page that lists both Shared by me and Shared with me, so you can find either direction later.

Which access level fits each common scenario

Scenario 1: Hand off an unresolved investigation

Choose View & fork.

Have your colleague open the original task first andreview everything you triedfrom the beginning. The complete record is more reliable than a verbal recap. Then click Fork into my tasks to create their own task and continue investigating.

Two things to remember: the copydoes not containthe files or directories from your workspace, so send any needed outputs separately. It doesnotreceive your later discoveries. If you keep investigating, update them yourself.

Scenario 2: Let the whole team reuse a proven workflow

Choose View & fork and share it with each person.

Each person gets anindependent copyin their own workspace, running with their own Agent. The copies do not interfere with one another or alter your original task.

Tip: Give the task a clear title before sharing—for example, Weekly report automation · Reusable—because that title appears on sharing cards and in lists.

Scenario 3: Show results to a manager or another team without allowing changes

Choose Live view.

The recipient can see the full process and outputs, but cannot fork, reply, or make a quick change. Remember to return after the review and Stop sharing.

Note: even with Live view, the recipientsees the full task, not a summary. Before sharing outside your immediate team, make sure the task contains no information from other projects. TabTin currently does not support sharing outside the organization.

Sharing a task is not the same as a handoff

Direct messages also offer a Context handoff card where you record the goal, progress, next steps, and risks. The recipient then clicks Continue from here to take over. The two flows serve different purposes:

	Shared task	Context handoff
What it provides	The live task itself	A handoff note you write, plus links to supporting material
Recipient action	Open the task / Fork to My Tasks	Acknowledge / Decline / Continue from here
Responsibility	Does not transfer; the task remains yours	Explicitly transfers the work
Best for	Take a look / Follow this example	This is yours now

Share a task when someone needs visibility. Use a handoff when responsibility needs to move to them.

FAQ

I cannot find the colleague I want to share with

Check whether the top bar is set to Personal account. Switch to the correct team organization and try again
They may not have joined the organization yet. Go to Organization settings → Members & quota and invite them
You cannot share a task with yourself, so your name will not appear in the list

The recipient cannot open the task or sees a blank page

First make sure sharing is still active. In the task header, check whether the recipient's row in Manage sharing is marked Stopped
Ask them to open it fromthe shared-task card in your direct messageClick Open task, or from the Share conversation page in the direct-message canvas
A shared task opens as a tab in thedirect-message canvas, not as a pop-up. If the recipient has collapsed the canvas, it may look as though nothing happened

Why is there no sharing option in a group chat?

Task sharing grants access from you to one specific person. A group chat has no single recipient, so itis available only in direct messages. To share with several people, add them one at a time. Each person receives an independent grant that can use a different access level or be stopped separately.

Can I reshare a task someone shared with me?

No. Only the task owner can share it. You can first Fork into my tasks to create your own task, then share that copy. Keep in mind that it is asnapshot, not a live view of the original task.

Will the recipient use my credits?

With either Live view or View & fork, the recipientcannot run the Agent in your task. Viewing or forking therefore creates no execution usage on your side. A fork runs on their device with their Agent, and usage is charged to the organization's wallet.

Can I see whether they viewed or forked the task?

TabTin records an audit trail of who viewed or forked the task, changed access, or stopped sharing, butthe app does not display that audit trail yet. For now, the fastest way to confirm they have opened it is to ask them in the direct message.

What remains with the recipient after sharing stops?

Any already-forkedcopy remainsand cannot be revoked
Theread-only document and table access granted during sharing remains; remove it separately from that resource
They can no longer open the original task; it shows Sharing has stopped or you do not have access

Can the recipient see my files or terminal?

No. They can seethe timeline recordsincluding file paths the Agent worked with, but theycannot enter your workspace. They cannot browse directories, open a terminal, or change your files. Your execution workspace never transfers with a share.

Still stuck?

Take a screenshot of the step where you are stuck—the sharing dialog, sharing card, or error the recipient sees—and send it to contact@larchiveai.com. We will help you diagnose it. Beta users can also ask their contact in the group, which is usually faster.