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

# How teams work in Profound

> Learn what teams are in Profound and how they control category access, shared resources, and credits

<Info>
  **Available on**: the Enterprise plan

  **Find it in**: Settings in the organization name menu at the top left of the screen > People > Teams tab

  **Required role**: Admin or custom
</Info>

A team is a named group of members inside your [organization](/getting-started/organizations-and-teams). Where [roles](/platform-config/people/roles-and-permissions) control what a member can do, such as run Agents or manage integrations, teams control what a member can see and which credits they spend.

Use teams to mirror how your company works, for example one team per business unit, brand, or region. Each team can have its own [categories](/getting-started/categories#category-structure-and-how-it-relates-to-other-profound-building-blocks), its own shared resources, and its own [credit](/getting-started/credits) wallet. To set one up, see [Create and manage teams](/platform-config/people/teams/create-and-manage-teams).

<Note>
  Teams are optional. They help organize access and resources within your organization, but if everyone in your organization works on the same categories, you may not need teams.
</Note>

## What problem teams solve

Large companies often have several groups working in Profound at once, each with its own brands, budget, and private material. Without teams, keeping those groups apart takes workarounds:

* **Separate organizations for each group.** Data stays apart, but reporting can't roll up across organizations, and people switch between organizations to manage their work.
* **One shared credit pool.** Any group can use up credits that another group needs.
* **Access set one person at a time.** An admin grants category access to each new member individually.

With teams, you keep everyone in one organization and draw the lines inside it. Each group sees its own categories, uses its own credits, and gets the resources shared with it, while your organization keeps one place for reporting and administration.

## Category access

When you add a [category](/getting-started/categories) to a team, every member of the team can access it. The access that comes from the team adds to the access a member already has, and never removes from it.

For example, a member has direct access to Category 1 and joins a team that has Categories 2, 3, and 4. They can now access Categories 1–4. If you remove them from the team, they go back to Category 1 only. A member of several teams can access the categories visible to all of them.

A team can access only categories your organization uses, including categories another organization shares with yours. Learn more about shared categories in [Categories in Profound](/getting-started/categories#when-you-have-multiple-organizations-and-categories).

## Sharing resources with a team

Resources, such as Dashboards, Documents, Sheets, Agents, or Workflows, are private to the person who created them until they're shared. You can share them with a whole team instead of inviting members one by one. The sharing dialog lists every team in your organization.

Every member of the team gets the access level you pick when sharing, such as viewer or editor, for as long as they're on the team. The share decides their access to that resource, whatever their role says. When someone leaves the team, they lose access that came through the team, but keep anything shared with them directly.

## Team wallets

A team can have its own credit wallet. Credits in a team wallet are reserved for that team, and no other team can spend them. Profound sets up team wallets for you: contact your Profound account team with your team names and monthly credits per team.

Every member spends from one active wallet at a time:

| Member's situation | Where the credits come from |
| - | - |
| Not on any team | The organization's credits. Admins can still set a [credit limit for individual members](/getting-started/credits#estimate-and-track-credit-usage). |
| Joins a team without a wallet | No change. The team's **Team Wallet** panel shows that no wallet is configured. |
| Joins a team with a wallet | The team wallet, once Profound assigns them to it. Until then, they keep spending from the organization's credits. Individual credit limits don't apply while they spend from a team wallet. |
| On more than one team with a wallet | One of the team wallets, set by Profound. Contact your Profound account team to change it. |
| Removed from a team | Back to the organization's credits. |

When the active wallet [runs out](/getting-started/credits#when-you-run-low-or-run-out), Profound doesn't switch to another wallet. The member can't use credits until the wallet is topped up or an admin moves them to another team.

<Note>
  Whoever runs an Agent, a Workflow, or a Sheet pays for the run from their own active wallet. Sharing one with someone doesn't charge the person who shared it.
</Note>

## Who can manage teams

The following permissions control teams:

* **Manage teams**: create, rename, and delete teams, and change their categories.
* **Manage team members**: add members to teams and remove them.
* **View people directory**: see the **People** page, including the **Teams** tab.

Admins have all of them by default, and you can add them to any [custom role](/platform-config/people/custom-roles).

These permissions apply to every team in the organization. Members who can't manage teams see only the teams they belong to.

## Limitations

* **No dedicated team admins.** Anyone with the team permissions manages every team in the organization. You can't make someone an admin of only their own team.
* **One role per member.** A member's [role](/platform-config/people/roles-and-permissions) applies across the whole organization, no matter which teams they're on.
* **No individual credit limits inside a team wallet.** Members who need a personal credit limit should stay on the organization's credits.
* **Teams don't span organizations.** A team lives in one organization. Members of one organization can't be added to a team owned by another organization.