---
title: "Organizations And Seats"
description: "Use organizations to manage team-owned Gobiis, seats, roles, billing, and shared usage."
sidebar_label: "Organizations And Seats"
---

Organizations let teams share ownership, billing, usage, and access for Gobiis.

Open organizations at `https://gobii.ai/console/organizations/`.

## What an organization gives you

- Shared Gobiis owned by the organization.
- Member roles and seat management.
- Organization billing context.
- Shared credit usage and usage reporting.
- Organization-scoped MCP servers and secrets where available.
- Cleaner separation between personal experiments and team workflows.

## Common roles

Role names and exact permissions can vary by plan, but the model is:

- **Owner**: workspace and billing control.
- **Admin**: manage members, Gobiis, and workspace settings.
- **Member**: use organization resources within granted access.

## Seats

Seats control how many people can belong to an organization. Billing owners can add or schedule seat changes where supported.

Before adding seats, decide:

- Who needs full organization membership.
- Who only needs collaborator access to one Gobii.
- Which Gobiis should move from personal ownership to organization ownership.

## Assign Gobiis to an organization

Use organization ownership for workflows that belong to the company or team rather than one person. This helps preserve continuity if individual users change roles.

When reassigning a Gobii, check:

- Who should own billing and usage.
- Which collaborators still need access.
- Whether secrets, contacts, MCP servers, and app connections still apply.
- Whether the Gobii's charter references personal context that should be removed.

## Billing and usage

Organization usage appears in the usage and billing areas for users with permission.

See [Usage And Billing](/admin-and-teams/usage-and-billing).
