Organizations & collaboration · 4 min read · Updated 2026-09-08
What can teammates see when I share an Agent task?
Who can speak in real-time collaboration, who handles execution and approvals, and the boundaries of independent continuation and resource permissions.
Before sharing a task, decide whether colleagues should join the original task or take over independently. This determines where they continue and who handles execution, approvals, and costs.
For full illustrated instructions, see Work together or hand off? Ways to collaborate on AI tasks. This page focuses on collaboration permissions and handoff boundaries.
What are the two current collaboration options?
| Collaboration option | How the recipient continues | Execution and approvals |
|---|---|---|
| Real-time collaboration | Join the original task, view its context, and send messages to direct the Agent alongside the initiator | The original task’s side remains responsible for execution, approvals, and costs |
| Hand off to a colleague | Create their own task from a frozen snapshot of the existing context and continue independently | This does not transfer control of the original task’s computer, accounts, or approval permissions. Check the new task’s execution environment and model before starting |
Real-time collaboration lets colleagues send messages in the original task. If they only need to read the final result, share the output document separately and choose the appropriate document sharing permissions.
Are you sharing a task or an entire project?
You share the current task conversation and its working context, not the entire project, workspace, or AI persona. Inviting project members and sharing a task are separate actions.
Before sending, review the task name, messages, and attachments to ensure they are appropriate for the recipient. If only the final file is needed, share the document or attachment directly.
Can the recipient make the Agent keep working?
When you choose Real-time collaboration, yes. They can add requirements in the original task and direct the Agent. The original task’s side remains responsible for execution, approvals, and costs.
This does not give them an independent remote desktop or transfer every local directory, account, or connector permission. However, collaborators’ requests may trigger actions by the original task’s Agent, so check the recipient, collaboration option, and execution permissions before sending.
When you choose Hand off to a colleague, the recipient continues in their own task. Independent continuation does not edit the original task in real time.
Why can the recipient open the task but not its files?
Task collaboration and access to documents, files, and connectors are checked separately. Sharing a task does not authorize every referenced resource.
- Cannot open a cloud document or spreadsheet: check the original resource’s sharing settings and the recipient’s permissions.
- The file exists only locally: a local path does not mean the recipient’s device has the file. Prepare accessible materials before handoff.
- A connector is required: check the account connection and authorization in the environment taking over the task.
Will tasks stay in sync after a handoff?
Independent continuation uses context frozen at handoff time. Later messages in the original task do not automatically enter the recipient’s new task. Send new materials or conclusions separately.
Using Fork task yourself also creates an independent task; subsequent messages are not automatically merged. If both tasks reference the same cloud document, they still edit the same resource. Independent conversations do not imply duplicated files.
How do I send a collaboration invitation?
- Open the task to share and click the button to the right of its title: Share with colleagues.
- Search for and verify an organization member, then select the recipient.
- Under Collaboration option, choose real-time collaboration or handoff to a colleague.
- Check the recipient and task again, then confirm.
- Check the completion notice and have the recipient open the task card in your IM direct conversation.
Real-time collaboration opens the original task. For independent continuation, confirm that the recipient entered their own task. See the interface in the illustrated guide.
What if I cannot find a colleague or the group chat option?
Check the current organization, member name, and account first. If loading fails, retry; a loading failure does not mean the organization has no members.
If the group option says “Group chat not supported yet,” use the task’s Share with colleagues entry point and select recipients by member.
What else should I check after ending collaboration?
Check the task’s current sharing status and available management actions. After ending task collaboration, separately review sharing permissions for output files; changing task permissions does not necessarily revoke resource access.
An independently created continuation or fork is a separate task. Ending sharing of the original does not automatically delete the recipient’s copy.