> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/departments/assign-departments.md).

# Assign people to departments

Drag the people on a project into your company's departments, so the transactions they upload are assigned to their department.

Use the **Departments** page to choose which department each person on a project belongs to. Open it from **Departments > Assign** in the sidebar, which shows it to Owners, Super Admins, Managers and Department Heads.

{% hint style="info" %}
The sidebar's **Departments** section appears only if your company uses departments. These are your company's departments with jobs. They're separate from the departments on the **Departments** tab of [**Project > Team**](/project/team.md), which set the people a Department Head manages.
{% endhint %}

## Assign someone to a department

1. In the sidebar, select **Departments > Assign**.
2. Find the person's name. People without a department are in the **Unassigned** box at the top. Everyone else is in their department's box.
3. Drag the name into a department's box.

The change saves on its own. About a second after you drop the name, the indicator above the boxes shows **Saving...** and then **Saved!**.

* Each person is in one department at a time. Dragging them into a new box takes them out of their old one.
* Assignments apply only to the project you're on, so someone can be in a different department on each project.
* Each box lists its people. An empty box shows a hint to drag people there.
* Dragging works with touch on phones and tablets. If the list is long, drag a name toward the top or bottom edge of the list to scroll it.
* Each save stores every assignment as your page shows it, and the page doesn't pick up other people's changes. If someone else may have changed assignments, reload the page first.

To add jobs to the departments, use [**Departments > Manage**](/departments/manage-departments.md). If you see only the **Unassigned** box, your company has no departments yet. Contact RollCredits support to set them up.

## Take someone out of their department

1. In the sidebar, select **Departments > Assign**.
2. Drag the person's name from their department's box into the **Unassigned** box.

## What a department does

Once someone is in a department, the transactions they upload are assigned to that department automatically. When they upload a receipt or invoice, the **Department** field is filled in with their department and they can't change it. For the upload steps, see [Add receipts, invoices and estimates](/transactions/transactions/add-transactions.md).

Changing someone's department doesn't change the transactions they've already uploaded.

## If a change doesn't save

If "Failure when updating department assignment" appears, the change wasn't saved, even though the boxes still show it and the indicator shows **Saved!**. Reload the page to see what was saved, then put back any assignment that's missing.

{% hint style="warning" %}
After your last change, wait until the indicator has shown **Saving...** and then **Saved!** before you leave the page.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.rollcredits.io/departments/assign-departments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.