> 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/organizations-and-projects/organization-settings-and-management.md).

# Organization Settings and Management

Manage Organization details, access patterns, segmentation, and the Projects inside the Organization.

### Overview

Organization settings define how work is governed inside an Organization. This includes Organization details, segmentation, and Project management patterns.

### Key Concepts

* **Organization details**: name and descriptive context used for search and reporting
* **Organization scope**: boundary for Segments and Segment Types
* **Organization-level access**: shared access across Projects (when enabled)

### How It’s Used

Use Organization settings during initial rollout. Use them when adding new Projects or updating governance.

### Benefits

* More consistent structure across Projects
* Cleaner reporting through shared segmentation
* Reduced access drift through scoped management

### Setup Steps

{% stepper %}
{% step %}

### Open the Organization

Navigate to **Organizations**. Select the Organization to manage.
{% endstep %}

{% step %}

### Update Organization details

Update the Organization name and description when business structure changes. Keep names stable and human-searchable.
{% endstep %}

{% step %}

### Configure segmentation (optional)

Define Segment Types and Segments for reporting and scoping.

* Segmentation
  {% endstep %}

{% step %}

### Manage Projects inside the Organization

Create new Projects for new initiatives. Archive Projects when delivery completes.

* Create a Project
  {% endstep %}

{% step %}

### Set up Interactions Routing (optional)

Add the Organization's email domains on the **Interactions Routing** tab so synced meetings and emails with its people are filed here automatically.

* [Interactions Routing](/organizations-and-projects/interactions-routing.md)
  {% endstep %}
  {% endstepper %}

### Best Practices

* Keep Organization names stable and avoid abbreviations.
* Use segmentation only for real business dimensions used for reporting.
* Standardize Project naming and section structure across related initiatives.

### Summary

Organization settings define governance patterns and reporting structure. Segmentation is managed at the Organization level.

Related:

* Organizations
* Projects
* Understanding Access Levels
* [Interactions Routing](/organizations-and-projects/interactions-routing.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/organizations-and-projects/organization-settings-and-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.