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

# Departments

> Group positions into a department tree to navigate and filter your organization by team.

Departments let you group Positions into a hierarchy that mirrors your organization's structure. They help you organize and navigate your workforce; they don't change how Responsibilities are assigned or how Readiness is calculated.

## Where to find departments

Go to **Account → Organization → Departments**. The view shows your organization as a tree. Each node is a Department, and Positions (with the employees who hold them) sit inside Departments.

## What departments are for

* **Navigation** — Administrators can browse the organization by team, division, or unit instead of scrolling a flat list of Positions.
* **Filtering** — filter the Employees and Positions lists by Department.

An employee's Responsibilities come from the Position → Role → Responsibility structure, not from their Department. See [Key organizational concepts](/concepts/organization).

## The department tree

Departments are nested. A Department can contain Positions (with their assigned employees), sub-departments, or both, with no limit on depth. A typical structure looks like:

**Company → Division → Team → Positions**

A Position can belong to only one Department at a time. Positions not placed in any Department appear as unassigned.

## Add a new department

<Steps>
  <Step title="Open Departments">
    Go to **Account → Organization → Departments**.
  </Step>

  <Step title="Add the department">
    Click **+ Add Department** and enter the Department name.
  </Step>

  <Step title="Choose a parent">
    Select a parent Department, or leave it at the top level to create a root Department.
  </Step>

  <Step title="Save">
    Click **Save**. The Department appears in the tree immediately, ready to receive Positions.
  </Step>
</Steps>

## Department actions

Most actions are in the three-dot menu (⋯) on the right side of the Department row.

### Rename

Updates the Department name everywhere it appears. No Positions or assignments are affected.

### Create a sub-department

There's no dedicated "Add Sub-department" action in the row menu. To nest a new Department, click **+ Add Department** in the header and choose the existing Department as the parent.

### Move

Changes the Department's parent. All Positions and sub-departments inside it move with it.

### Archive

Removes the Department from the active tree. Positions inside it become unassigned. Archive a Department only when it no longer represents an active part of the organization.

### Delete

Permanently deletes the Department. Only available when it's empty (no Positions and no sub-departments). This can't be undone.

## Add a position to a department

<Steps>
  <Step title="Find the department">
    Find the Department in the tree.
  </Step>

  <Step title="Add the position">
    Click **+ Add Position** (or drag an existing Position into the Department), then search for and select the Position.
  </Step>

  <Step title="Confirm">
    Confirm. The Position now appears under that Department.
  </Step>
</Steps>

## Move a position between departments

Drag the Position row from its current Department and drop it into the target Department. Its assignments, Roles, and Responsibilities aren't affected.

## Remove a position from a department

Open the Position's row menu inside the Department and select **Remove from Department**. The Position becomes unassigned and appears in the unassigned Positions list.

## Rules and constraints

* A Position can belong to only one Department at a time.
* Departments can be nested to any depth.
* You can delete a Department only when it's empty.
* Archiving a Department leaves its Positions unassigned. They don't move to the parent Department automatically.
* Department membership doesn't affect Responsibility assignment or Readiness calculation.

## Common questions

<AccordionGroup>
  <Accordion title="Does moving a Position to a different Department change the employee's Responsibilities?">
    No. Responsibilities come from the Position → Role → Responsibility structure, not from the Department.
  </Accordion>

  <Accordion title="What happens to an employee's Readiness data if their Position moves to another Department?">
    Nothing changes. Readiness is calculated from badges and Responsibilities, not from Department membership.
  </Accordion>

  <Accordion title="What does it mean for a Position to be unassigned?">
    The Position exists but isn't placed in any Department. It still works normally (employees can be assigned and Responsibilities flow through it), but it doesn't appear in any Department's branch of the tree.
  </Accordion>

  <Accordion title="Can a Department contain both Positions and sub-departments?">
    Yes, in any mix.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Key organizational concepts" icon="sitemap" href="/concepts/organization">
    The definitions behind the structure.
  </Card>

  <Card title="Positions" icon="briefcase" href="/organization/positions">
    The positions you place in departments.
  </Card>

  <Card title="Organizational tree" icon="folder-tree" href="/organization/organizational-tree">
    How the whole structure connects.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.