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

# Organization settings

> Define and order the hierarchy tiers of the org chart, and define the cross-cutting group types used for task forces, tiger teams and committees.

**Workforce → Organization → Settings** (`/workforce/settings`) holds the two kinds of structure type every org unit is built from: **Hierarchy Tiers**, the levels of the org chart, and **Cross-Cutting Group Types**, the kinds of group that span it. Reading them needs `workforce:read`; adding a type or reordering tiers needs `org:manage`.

![Organization settings (light)](https://mintcdn.com/gloo-b243725a/ahnDPYAsbo1iROpN/forge/images/console/workforce/settings-light.png?fit=max\&auto=format\&n=ahnDPYAsbo1iROpN\&q=85\&s=c4dd322fcf43ab7d8399f22cb1b1fdeb)

Organization settings — Forge Console at `/workforce/settings`

## What you can do

* Read the hierarchy tiers in order, and move a tier up or down.
* Add a hierarchy tier with **Add Tier**.
* Read the cross-cutting group types, and add one with **Add Type**.

## Hierarchy Tiers

The tiers are the levels of your org chart, listed in order. Each row shows:

| Column | What it shows |
| - | - |
| **Order** | The tier's position, from 0, with **Move tier up** and **Move tier down** arrows |
| **Name** | The tier name and its plural |
| **Key** | The tier's stable slug |
| **Icon** | The icon name, or `—` |
| **Nesting** | **Yes** when a unit of this tier can sit under another unit of the same tier |
| **Status** | The tier's status |

An arrow saves the new order at once; there is no separate save. If the server refuses the reorder, the reason appears above the table. [Organization structure](https://docs.gloo.com/forge/console/workforce/structure.md) shows each unit's tier by name in its **Tier** column.

## Cross-Cutting Group Types

Group types define the org-chart-agnostic structures, such as Task Forces, Tiger Teams and Committees, that [Groups](https://docs.gloo.com/forge/console/workforce/groups.md) are created from. Each row shows the **Name** and plural, the **Key**, a **Description** and the **Status**.

## Adding a tier or a group type

**Add Tier** opens **Add Hierarchy Tier**, and **Add Type** opens **Add Group Type**. Both ask for:

* **Name** and **Plural Name**, for example Department and Departments.
* **Key**, a lowercase kebab-case slug such as `department`. The field turns other characters into hyphens as you type.
* **Icon**, optional, chosen from a searchable list.

A tier also has **Allow same-type nesting**, and is added at the end of the order. A group type also has an optional **Description**.

With nothing defined, each table says so: **No hierarchy tiers defined.** or **No cross-cutting group types defined.**

## Key state to watch

* **Tier order** — it is the order of levels across the org chart; reorder it only when the levels themselves change, not to fix a single unit.
* **No group types** — without one, nobody can create a group on Groups.

## Related surfaces

* [Organization structure](https://docs.gloo.com/forge/console/workforce/structure.md) — the org-unit tree built from these tiers.
* [Groups](https://docs.gloo.com/forge/console/workforce/groups.md) — groups created from these types.
* [Org Chart](https://docs.gloo.com/forge/console/workforce/org-chart) — the hierarchy as people and positions.


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