> 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/manage-departments.md).

# Manage department jobs

Add and rename the jobs in your company's departments, which people choose in Project/Division when they code a transaction.

Use this page to add jobs to your company's departments and to rename them. Open it from **Departments > Manage** in the sidebar, which shows it to Owners, Super Admins, Managers and Department Heads.

{% hint style="info" %}
If your company uses departments, the **Departments** section shows in the sidebar. Its departments are separate from the ones on the **Departments** tab of [Project > Team](/project/team.md). To put people in a department, see [Assign people to departments](/departments/assign-departments.md).
{% endhint %}

The page, headed **Manage Department Jobs**, has one tab for each department in your company. Each tab lists the department's jobs in a **Job Name** table. If your company has only one department, its jobs show without a tab.

## How jobs are used

Jobs belong to your company, so every project in it uses the same jobs. When people code a transaction, they choose a job in **Project/Division**, or in the **Project** column of the transactions table. A job can be limited to some budget categories, and once someone picks it, the category list shows only the categories open to it. See [Code transactions](/transactions/transactions/code-transactions.md).

## Add a job

1. Select the department's tab.
2. Select **Add Job**. A window titled "Add New Job to" and the department's name opens.
3. Enter a **Job Name**.
4. In **Copy Categories From**, choose the job whose categories the new job should use. It starts on the first job in the department, and it lists only this department's jobs.
5. Select **Confirm**.

The new job can use the same budget categories as the job you copied from. You can't change a job's categories on this page.

{% hint style="info" %}
**Confirm** stays unavailable until you've entered a name and chosen a job to copy from, so you can add a job only to a department that already has one. If the job you copy from has no categories set up, the job isn't added and you see "Failed to add job".
{% endhint %}

## Rename a job

1. Select the department's tab.
2. Select the **...** menu at the end of the job's row.
3. Select **Edit Job**.
4. Replace the text in **Job Name** with the new name.
5. Select **Save**.

The new name shows everywhere the job is used, including transactions already coded to it on every project in your company.

## What you can't do here

* Jobs can't be deleted.
* Departments can't be added, renamed or deleted.
* Two jobs can have the same name, so check the department's list before you add one.


---

# 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/manage-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.