> ## Documentation Index
> Fetch the complete documentation index at: https://ona.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage teams

<Note>Requires [Enterprise plan](https://ona.com/pricing). [Contact sales](https://ona.com/contact/sales) for access.</Note>

Teams are for **organizational reporting and cost management**, not access control. Use them to mirror your real-world structure, for example "Backend", "Mobile", or "Platform", so you can see where credit consumption goes and give each part of the organization its own spending target. To grant access to projects or runners, use [groups](/ona/organizations/groups) instead. See [Groups vs. teams](/ona/organizations/overview#groups-vs-teams) for a side-by-side comparison.

## Managing teams

Only organization admins can create, rename, or delete teams and manage team membership.

### Create a team

1. Go to **Settings → Members → Teams**
2. Click **New Team**
3. Enter a team name (3–80 characters, unique within the organization)
4. Optionally select members to add during creation
5. Click **Create**

### Add members

1. Open the team
2. Click **Add People**
3. Select members and click **Add**

A member can only be on one team per organization. If you add someone who is already on another team, move them from the original team first.

### Remove members

1. Open the team
2. Select members using the checkboxes
3. Click **Remove**

Removed members keep all their existing access to projects and runners. Team membership only affects how their usage is attributed going forward.

### Rename a team

1. Open the team or use the team card menu
2. Click **⋯** → **Edit**
3. Enter the new name and save

### Delete a team

1. Open the team
2. Click **⋯** → **Delete**
3. Confirm

<Warning>
  Deleting a team removes its credit budget and ends per-team usage attribution for its members. Historical usage already attributed to the team is preserved in usage reports. Members keep all their access to projects and runners.
</Warning>

### Find members not on a team

The Teams tab shows a **Members not assigned to a team** section so you can spot who still needs to be placed. Use it as a checklist when rolling out teams across your organization.

## Roles within a team

Two roles apply inside a team. Both are assigned automatically. You do not manage them by hand.

| Role            | Granted to                               | Can do                                                   |
| --------------- | ---------------------------------------- | -------------------------------------------------------- |
| **Team admin**  | Organization admins, on every team       | Rename the team, delete the team, add and remove members |
| **Team viewer** | Every organization member, on every team | View the team and see its member list                    |

Because every member is a viewer on every team, there is no concept of a private team. Team membership is visible across the organization.

## Per-team credit budgets

Each team can have a credit budget that you set on the **Cost & Budgets** page.

<Note>
  Budgets are **soft**: they are used for reporting and alerting only and are **not enforced** at usage time. Members on a team that has exceeded its budget can still create environments and run agents. The sum of all team budgets is allowed to exceed the organization's total credit grant.
</Note>

Use budgets to:

* Give each team a planned credit allowance for the month
* Spot teams that are trending over their allowance early
* Compare planned vs. actual consumption across teams

### Set or change a team's budget

1. Go to **Settings → Cost & Budgets**
2. Switch the grouping to **Teams**
3. In the team's row, click the budget value (or **Set budget** if none is set)
4. Enter a credit amount and save

## Usage attribution

Once teams are in place, the **Cost & Budgets** page can group consumption by team:

* A daily credit chart broken down by team
* A table listing each team's consumption for the selected period, with a link to the team detail page
* CSV export, including the team column

Usage is attributed to whichever team a member belonged to **at the time the usage was metered**. Moving a member to a different team does not re-attribute their past usage.

Members who are not on any team appear under an "Unassigned" bucket in the chart and table.

## FAQ

<Accordion title="Does adding someone to a team change what they can access?">
  No. Teams are for usage attribution and budgeting only. Access to projects and runners is controlled by sharing, either directly with users or through [groups](/ona/organizations/groups).
</Accordion>

<Accordion title="Can a member be on more than one team?">
  No. Each member belongs to at most one team per organization. If you need overlapping membership for access purposes, use groups instead.
</Accordion>

<Accordion title="What happens to usage history when I move someone between teams?">
  Past usage stays attributed to the team they were on at the time. Only new usage from the moment of the change is attributed to the new team.
</Accordion>

<Accordion title="What happens when a team's budget is exceeded?">
  Nothing is blocked. Budgets are soft and exist for reporting and alerting only. Members can continue to create environments and use Ona normally.
</Accordion>

<Accordion title="Can I hide a team from other members?">
  No. All members of an organization can see every team and its members.
</Accordion>