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

# Divisions

> Tenant-owned organizational hierarchy, parent-child relationships, sibling order, and cost-center assignment.

A division belongs to one tenant and can be a root division or a child of another division in the same tenant.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart TD
    T[Tenant] --> A[Sales]
    T --> B[Operations]
    A --> C[Enterprise]
    A --> D[SMB]
```

## Endpoints

<CardGroup cols={2}>
  <Card title="List divisions" icon="list" href="/api-reference/divisions/list-divisions">
    Query the hierarchy by tenant, name, parent, order, cost center, and timestamps.
  </Card>

  <Card title="Create a division" icon="folder-plus" href="/api-reference/divisions/create-division">
    Create a root or child division with dry-run validation.
  </Card>

  <Card title="Get a division" icon="network" href="/api-reference/divisions/get-division">
    Read one division by ID.
  </Card>

  <Card title="Update a division" icon="folder-pen" href="/api-reference/divisions/update-division">
    Rename, reorder, reparent, or change the cost center.
  </Card>
</CardGroup>

## Validation rules

* Parent and child must belong to the same tenant.
* A parent change cannot create a hierarchy cycle.
* A division name must be unique among siblings.
* `parentId: null` represents a root division.
* Nullable `costCenter` can be cleared with `null`.
* The public v1 contract does not expose division deletion.

<Card title="Division management guide" icon="workflow" href="/guides/manage-divisions" horizontal>
  Use safe create, reparenting, ordering, and conflict-resolution patterns.
</Card>