> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/blueprints/segmentation.md).

# Segmentation

### Overview

Segments model Organization structure for scoping and reporting. Segments are not tags or project labels.

Segments and Segment Types are scoped to the **Organization**.

### Key Concepts

#### Segment Types

A Segment Type defines a business dimension. Pick dimensions used to operate the Organization.

For example:

* Legal Entity
* Department
* Line of Business
* Business Unit
* Region

#### Segments

Segments are values inside a Segment Type. They represent divisions used for ownership and reporting.

For example, under **Region**:

* North America
* EMEA
* APAC

Segments can be hierarchical. For example: `North America` → `United States` → `Northeast`.

### How It’s Used

Use Segments to scope work to a part of the Organization. Use Segments to filter and group reporting views.

Segments can be applied across multiple entity types:

* **Processes**: map process ownership by Organization unit.
* **Systems**: align systems to a legal entity or department.
* **RACI items**: define accountability within an Organization boundary.
* **Requirements**: scope and filter by the business unit impacted.

### Benefits

Consistent segmentation enables:

* Filter requirements, tasks, and processes by Organization dimension.
* Group work by legal entity, department, or line of business.
* Build scoped views for a specific part of the business.
* Align accountability and governance to Organization boundaries.

### Setup Steps

{% stepper %}
{% step %}

### Create a Segment Type

Define the business dimension to track.

1. Open the Organization.
2. Create a Segment Type (for example: `Department`).
   {% endstep %}

{% step %}

### Create Segments

Add the actual values for that dimension.

Create Segments inside the Segment Type. Optionally assign a parent Segment to build a hierarchy.
{% endstep %}

{% step %}

### Apply segments to work

Associate Segments with processes, systems, RACI items, and requirements. Use Segments for filtering, sorting, and reporting.
{% endstep %}
{% endstepper %}

### Best Practices

{% hint style="info" %}
**Ground segments in the real org structure.**

If a value would not show up on an organization chart, it is usually not a Segment.
{% endhint %}

{% hint style="info" %}
**Use hierarchies when you need rollups.**

Parent-child segments enable both summary and deep reporting.
{% endhint %}

{% hint style="success" %}
**Be consistent across entity types.**

The value comes from reuse, not one-off assignments.
{% endhint %}

{% hint style="warning" %}
**Avoid Segment Type sprawl.**

Start with a few strong dimensions. Add more only when reporting needs require it.
{% endhint %}

### Summary

Segmentation standardizes business structure for scoping and reporting. Segment Types define dimensions. Segments provide values and optional hierarchy.

#### Quick decision check

If unsure whether something is a Segment Type:

* Does this reflect how the Organization operates?
* Would it appear in a formal business taxonomy?
* Is it a real division, not a project category?

If yes, this is usually a good fit.

Related:

* [Organizations](/organizations-and-projects/organizations.md)
* [Organization Settings and Management](/organizations-and-projects/organization-settings-and-management.md)
* [What Are Blueprints?](/blueprints/blueprint-fundamentals/what-are-blueprints.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/blueprints/segmentation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.