Collaborators And Ownership
Collaborators let more than one person work with an agent. Ownership decides who controls the agent, where it is billed, and which workspace policies apply.
Collaborators
Use collaborators when someone needs access to a specific agent but does not need broad organization access.
Collaborators may be able to:
- View the timeline.
- Send messages.
- Respond to some requests.
- Help manage settings where permitted.
Exact controls depend on role, owner type, and plan.
Ownership
An agent can belong to a person or an organization. Ownership affects:
- Usage context.
- Who can manage settings.
- Which organization secrets, MCP servers, and policies are available.
- Long-term continuity.
Use Team or Organization ownership for shared workflows. Use a single member's My workspace for experiments or individual work.
Transfer and reassignment
Ownership transfer or reassignment is useful when:
- A member's agent becomes a team workflow.
- A departing teammate owns an important agent.
- Usage should be attributed to a Team or the Organization.
- A template or demo should become production-owned.
Before transferring:
- Review files, secrets, contacts, app connections, and MCP servers.
- Remove personal context from the charter.
- Confirm collaborators still need access after transfer.
- Check whether contact endpoints or preferred routes should change.
When accepting a transfer, the new owner reviews the existing collaborators and shared filespaces, including other agents that can access those files. One explicit confirmation keeps that access intact. Collaborators do not need to accept another invitation. If the sharing list changes before acceptance, the recipient must review and confirm the refreshed list.
Pending collaborator invitations are cancelled during transfer. Existing file-download links that identify exact content can remain usable until their original seven-day expiry. New ownership and routine settings edits do not extend or reset that expiry. Older links that do not identify exact content are no longer accepted. Previously downloaded files cannot be recalled.
agent-to-agent links
Some workflows use links between agents so they can coordinate. Links should be intentional and limited to agents that need to exchange work.
Use Meta Agent when you want help proposing or managing a team of linked agents.