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

# Projects, Divisions & Departments

> Set up your organizational structure and use it to organize spend

Seloria organizes spend along a three-level hierarchy: **Division → Department → Project**. Every purchase request, budget, RFQ, and purchase order can be tagged with these levels, so you can always answer "what is this division/project spending?"

All three are managed in **Settings**, in the organizational structure tree, where you can expand each division to see its departments and each department to see its projects. Creating, editing, deactivating, or deleting these items requires a **Buyer**, **PM**, or **Admin** role — requestors cannot modify the structure.

## Divisions

A division is the top level (for example, Operations or Construction).

* **Create** a division from the tree with a **Name** and optional **Description**.
* **Edit** it at any time from the tree's edit action.

## Departments

Departments always belong to a division.

* **Create** a department with a **Name**, its parent **Division**, and an optional **Description**. When you add a department from a division's row in the tree, the division is preselected.
* Department lists across the app are **filtered by division**: in the purchase request form, the budget form, and the project editor, you must pick a division first, and only that division's departments appear. Changing the division resets the department selection.

## Projects

Projects always belong to a department.

* **Create** a project with a **Name**, its parent **Department**, an optional **Description**, and optional **Start date** and **End date**. The end date cannot be earlier than the start date.
* A short project **code** is generated automatically from the name.
* **Edit** a project from the tree to change its name, department, description, or dates. When reassigning the department, the list is scoped to departments in the project's own division so you don't accidentally move it across divisions.

<Note>
  Projects do not carry a budget amount themselves. To fund a project, create a budget in the **Budgets** module and assign it to the project — the budget then tracks allocated, committed, and spent amounts for that project. See [Budgets](/budgets/budgets).
</Note>

## Deactivating and deleting

Each item in the tree can be **deactivated** instead of deleted; inactive items stop appearing in selection lists but keep their history. Budgets assigned to an inactive division, department, or project flag it with an **Inactive** label on the budget detail page.

Before deleting, Seloria checks for dependencies and warns you:

* A **division** with active departments,
* A **department** with active projects (or linked RFQs/POs),
* A **project** with linked RFQs or purchase orders

will show what depends on it so you can decide whether to deactivate instead.

## How the hierarchy organizes spend

* **Purchase requests** capture the requestor's division and department, which carry forward to the RFQ and purchase order created from them.
* **Budgets** can be assigned to a division, a department, and a project (cascading selectors), and the Budgets list can be filtered by these, letting you see allocation and utilization per organizational unit.
* The budget detail page shows the full assignment path (Division → Department → Project) so it is always clear which part of the organization a budget belongs to.

Set up your divisions and departments before inviting requestors — both fields are part of the purchase request form, and a clean structure keeps downstream reporting meaningful.