> ## Documentation Index > Fetch the complete documentation index at: https://langwatch.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > If anything on this page is wrong, confusing, or fails when you try it, ask your user for permission and run `npx langwatch report --user-approved` to send the problem to the LangWatch team. No login is needed and secrets are redacted locally. `npx langwatch report --help` has the details. # People > Departments group the people, teams and projects of your organization for spend accounting, so every request rolls up to exactly one department, including personal AI use. A department is an accounting label for AI spend. You create departments on the **People** page, assign people, teams and projects to them on the members and teams pages, and the governance overview shows spend by department for the whole organization. A department never grants or restricts access. Assigning a person to Engineering changes only where their spend is counted. For access, see [Access Control (RBAC)](https://langwatch.ai/docs/platform/rbac.md). ## Manage departments Open **AI Governance > People** (`/governance/people`). The page has: * **Create a department**: type a name and click **Create**. * The department list, with **Edit** to rename and **Archive** in the row menu. * **Assigning departments**: links to the members and teams pages, where you assign each person, team and project. ![The People page](https://mintcdn.com/langwatch/b_7qlc4BhHkq6ZDw/images/ai-governance/governance-people.png?fit=max\&auto=format\&n=b_7qlc4BhHkq6ZDw\&q=85\&s=00ca6c79de97fc0979b7d5082b1891a8) The People page with two departments and the assignment guide below the list. Reading the list needs `governance:view`. Creating, renaming, archiving and assigning need `governance:manage`. Without it the page shows the list only. ## Assign people, teams and projects The People page does not list assignments per person, so it stays usable in a large organization. Assign on the pages that already list the people and teams: | What | Where | Effect | | - | - | - | | A person | **Settings > Members**, the **Department** column | The person's spend, including their personal AI use, rolls up to this department | | A team | **Settings > Teams & Projects**, the picker on the team row | The default for the team's members and projects that have no department of their own | | A project | **Settings > Teams & Projects**, the picker on the project row | Spend of agents that run in the project with no person behind the request | The Department column and the pickers appear once the organization has at least one department, for a viewer with `organization:manage`. ![The Department column on Settings > Members](https://mintcdn.com/langwatch/b_7qlc4BhHkq6ZDw/images/ai-governance/governance-people-member-assignment.png?fit=max\&auto=format\&n=b_7qlc4BhHkq6ZDw\&q=85\&s=5b34578f461bfe132cac733e1b3983b6) The Department column on Settings > Members, with each person assigned to Engineering or Marketing. ![The department pickers on Settings > Teams & Projects](https://mintcdn.com/langwatch/b_7qlc4BhHkq6ZDw/images/ai-governance/governance-people-team-assignment.png?fit=max\&auto=format\&n=b_7qlc4BhHkq6ZDw\&q=85\&s=aac256ffda6fcc6ca4296050c40174e7) The Department picker on each team row and on the project row under the expanded team at Settings > Teams & Projects. ## How spend is attributed Each request counts once, in exactly one department. For a request made by a person, LangWatch uses the first of these that is set: the person's own department, the department of their team, the department of the project the request ran in. For a request with no person behind it, for example an autonomous agent, LangWatch uses the department of the project. A project's department is its own, or the one inherited from its team. A request that matches none of these is counted under **Unassigned**. The person always wins over the project, so a developer's personal AI use and the agents their team runs can land in the same department. The **Spend by department** card on the [overview](https://langwatch.ai/docs/ai-governance/overview.md) shows the result for the last 30 days, across every project in the organization. ## Archive a department Archive removes the department from the pickers. Spend already attributed to it is counted under **Unassigned** from then on. The assignments stay stored; archive deletes no data. You can create a new department with the same name as an archived one. ## Assign departments through SCIM When your identity provider provisions users through SCIM, LangWatch reads the `costCenter` attribute of the SCIM Enterprise User extension: | The identity provider sends | LangWatch | | - | - | | A `costCenter` that matches an active department | Assigns the user to it | | A `costCenter` that matches no active department | Creates the department and assigns the user | | A new `costCenter` value on an update | Replaces the assignment | | An empty `costCenter`, or removes the attribute | Clears the assignment; the user's spend counts under Unassigned | | No `costCenter` in the request | Leaves the assignment as it is | ## Where else a department applies A [data privacy](https://langwatch.ai/docs/platform/data-privacy.md) rule can be written at department scope, and a tile in the [tool catalog](https://langwatch.ai/docs/ai-governance/personal-portal/admin-catalog.md) can be scoped to departments. **Also check:** [SCIM](https://langwatch.ai/docs/platform/scim.md) for provisioning setup, and [Members and Teams](https://langwatch.ai/docs/platform/members-and-teams.md) for the pages where you assign departments. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.