> 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/understanding-organizations-and-projects.md).

# Understanding Organizations and Projects

### Overview

Organizations and Projects define how work is structured in Transform. This structure also defines the scope for access control and reporting.

### Key Concepts

#### Organization

An Organization is a container for work belonging to a client, department, or business unit. Organizations contain Projects.

#### Project

A Project is a delivery container for a single transformation initiative. Projects contain requirements, tasks, tests, and artifacts.

#### Access scope

Access is assigned at Account, Organization, and Project scope. Scope determines what a Teammate can see.

* [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md)

### How It’s Used

Use Organizations to separate clients or internal divisions. Use Projects to separate initiatives and delivery timelines.

### Benefits

* Clear separation of work by client or department
* Cleaner access control through scope-based permissions
* More consistent reporting across Projects

### Setup Steps

Follow the common setup path.

{% stepper %}
{% step %}

### Create an Organization

Create an Organization for a client, department, or business unit.

* [Create an Organization](/organizations-and-projects/create-an-organization.md)
  {% endstep %}

{% step %}

### Create a Project

Create a Project for one transformation initiative.

* [Create a Project](/getting-started/create-a-project.md)
  {% endstep %}

{% step %}

### Configure the project

Set defaults, roles, fields, and integrations.

* [Project Settings and Configuration](/organizations-and-projects/project-settings-and-configuration.md)
  {% endstep %}
  {% endstepper %}

### Best Practices

* Keep Organization names stable.
* Use consistent Project naming, such as `{Organization} {initiative}`.
* Start with least-privilege access and expand only when needed.

### Summary

Core pages:

* [Organizations](/organizations-and-projects/organizations.md)
* [Projects](/organizations-and-projects/projects.md)
* [Project Settings and Configuration](/organizations-and-projects/project-settings-and-configuration.md)

Related:

* [Start Here](/getting-started/start-here.md)
* [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.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/organizations-and-projects/understanding-organizations-and-projects.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.