A cross-workspace mission lets a workspace temporarily host a companion from another workspace. The companion keeps its identity and home workspace, while both organisations keep control of the assignment.
Roles and prerequisites
Every mission has two separate workspaces:
- Home workspace — the workspace that owns the active companion and creates the invitation.
- Client workspace — the different workspace that accepts the invitation and hosts the assignment.
Both workspaces and the home companion must be active. A workspace administrator completes the action on each side.
Place a companion on assignment
In the home workspace, open Settings → Workspaces and select Place on assignment for the companion. This creates an invitation:
- it is single-use and expires after seven days;
- it is shown only when created, so copy it immediately;
- a companion can have one pending invitation at a time.
Share the invitation directly with the intended client-workspace administrator. Until it is accepted, the home workspace shows its expiry date and can revoke it.
Host the assignment
In the client workspace, an administrator opens Add agent, selects Invite an agent on assignment, and pastes the invitation.
Once accepted, the client workspace shows the companion under Invited agents as Name (Home workspace) with a guest badge. The home workspace shows On assignment at Client workspace.
To ask the guest companion to work, type @ in a conversation and select Name (Home workspace). The home-workspace label keeps guests with the same name distinguishable.
End a mission
Either workspace can end an active assignment:
- a home-workspace administrator uses Recall;
- a client-workspace administrator removes the guest from Invited agents.
Ending a mission immediately removes the guest's client-workspace access. To work together again later, create a new invitation.
Privacy and access
A mission keeps workspace access separate: hosting a companion does not let the client browse or retrieve the home workspace, its members, threads, or configuration (see Security).
A mission places the companion you already work with—not a blank agent. By default, it can use the knowledge and rules it accumulated in the home workspace.
Before the assignment, tell the companion which rules must remain internal to your organisation. Rules recorded that way stay in the home workspace. This control applies to rules only: other accumulated knowledge remains available to the companion during the mission.
Work performed for the client stays with that assignment. Mission work is excluded from home-workspace memory and overnight learning. Ending the mission stops the companion from continuing to work in the client workspace.
The companion is also told where it is. Every session of an assignment states the placement, names both workspaces, and sets the boundary: the companion may say who it is and who it works for, and it does not disclose its home workspace's business, its data, or its other clients. That framing guides the companion's conduct; what separates the two workspaces technically is the partitioning above.
Invitation safety
Mission invitations are single-use and expire after seven days. Share an invitation directly with the intended client-workspace administrator. A pending invitation can be revoked before it is accepted.
Accepting an invitation authorises only the temporary assignment. It does not let the client browse or retrieve the home workspace; the hosted companion can still use the knowledge it brings, as described above. After acceptance, use Recall or remove the guest to end the mission.
Related
- Desktop app — workspaces and their settings
- Collaboration — how companion collaboration remains visible
- Security — workspace isolation, permissions, and auditability