> For the complete documentation index, see [llms.txt](https://docs.securepass.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.securepass.me/documentation/admin-user-guide/configuration/departments.md).

# Departments

Departments model your organisational structure inside SECUREpass. They are what users are assigned to, what dynamic groups can be built from, what approval routing can follow, and what the department-based reports group by.

They describe **where someone sits**, not what they can reach — that is what groups and roles are for. Most access models use all three.

Select **Configuration → Departments**. The list shows each department, its sub-departments, its source, who created and last modified it, and the row actions.

The **Source** column matters: departments synced in from a connected directory are marked as coming from the system rather than being created here. Those reflect the upstream directory, so a correction belongs at the source rather than in SECUREpass.

## Creating a department

{% stepper %}
{% step %}

### Select Create Department

![Adding a department.](https://content.gitbook.com/content/W2srIAMN6RKFwvuEorV5/blobs/3QhP0Ul6GLUyxQeVeAru/assets/01.png)
{% endstep %}

{% step %}

### Enter the department name

Add **sub-departments** one at a time — type a name and select **Add**, and it appears as a chip beneath. Repeat for each.

Sub-departments are where the real detail lives. *Finance* with *General Ledger Accounting* and *Accounts Payable* beneath it lets you scope something to one of those rather than to all of Finance.
{% endstep %}

{% step %}

### Create the department

Select **Create Department**.
{% endstep %}
{% endstepper %}

## Editing a department

The pencil icon reopens it.

![Editing a department.](https://content.gitbook.com/content/W2srIAMN6RKFwvuEorV5/blobs/cTQnNw18CyjCcCrm5xvx/assets/02.png)

The name can be changed, sub-departments added the same way, and existing ones removed with the **×** on their chip.

{% hint style="warning" %}
Removing a sub-department affects the users assigned to it. Check what is scoped to it before taking it away — dynamic groups and approval routing that reference it will stop matching.
{% endhint %}

## Deleting a department

The bin icon asks for confirmation.

![Confirming deletion.](https://content.gitbook.com/content/W2srIAMN6RKFwvuEorV5/blobs/hpvSijEDTkP6DyRERkfh/assets/03.png)

{% hint style="info" %}
**Deleting deactivates the department rather than erasing it.** It disappears from the list and can no longer be assigned, but the record of it survives — so historical reports and audit entries that reference it still make sense.
{% endhint %}

A department you delete is gone from the picker but not from your history.