---
title: "Collaborators And Ownership"
description: "Manage who can work with a Gobii, transfer ownership, and keep personal and organization-owned Gobiis separate."
sidebar_label: "Collaborators And Ownership"
---

Collaborators let more than one person work with a Gobii. Ownership decides who controls the Gobii, where it is billed, and which workspace policies apply.

## Collaborators

Use collaborators when someone needs access to a specific Gobii 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

A Gobii can belong to a person or an organization. Ownership affects:

- Billing and usage context.
- Who can manage settings.
- Which organization secrets, MCP servers, and policies are available.
- Long-term continuity.

Use organization ownership for team workflows. Use personal ownership for experiments or individual work.

## Transfer and reassignment

Ownership transfer or reassignment is useful when:

- A personal Gobii becomes a team workflow.
- A departing teammate owns an important Gobii.
- Billing should move to an 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.

## Gobii-to-Gobii links

Some workflows use links between Gobiis so they can coordinate. Links should be intentional and limited to Gobiis that need to exchange work.

Use [Meta Gobii](/using-gobii/meta-gobii) when you want help proposing or managing a team of linked Gobiis.
