> 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/getting-started/start-here.md).

# Start Here

Follow a recommended setup path for initial Account, Organization, Project, and Teammate setup.

### Overview

Use this page as the default onboarding path for a new Account. Follow the setup steps in order.

### Key Concepts

#### Account, Organization, Project

Transform is organized by scope.

* **Account**: top-level container for all work
* **Organization**: container for a client, department, or business unit
* **Project**: delivery container for a single transformation initiative

#### Teammates

Teammates are people records with roles at one or more scopes. Access should follow least privilege.

#### Blueprints

Blueprints define reusable structure for new Projects. Blueprints reduce setup work and standardize governance.

### How It’s Used

Use this path during initial rollout. Use it again when onboarding a new Organization.

### Benefits

* Faster setup for new Organizations and Projects
* Consistent structure across initiatives
* Cleaner access control and auditability

### Setup Steps

{% stepper %}
{% step %}

### Create a Transform login

Create a login when signing in for the first time.

* [Create a Transform Login](/getting-started/create-a-transform-login.md)
  {% endstep %}

{% step %}

### Create an organization

Create one Organization per client or department.

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

{% step %}

### Invite teammates

Invite Teammates at the lowest scope that works.

* [Add Teammates](/organizations-and-projects/add-teammates.md)
* [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md)
  {% endstep %}

{% step %}

### Build the first Blueprint

Start with a template. Customize after teams start using it.

* [Tutorial: Set Up a First Blueprint](/getting-started/tutorial-set-up-a-first-blueprint.md)
  {% endstep %}

{% step %}

### Create the first Project

Create a Project from a Blueprint.

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

### Best Practices

* Create Organizations early to simplify access control.
* Standardize naming for Organizations and Projects.
* Keep Account Admin access limited.
* Establish a Blueprint before creating many Projects.

### Summary

Recommended reading:

* [New to Transform](/getting-started/new-to-transform.md)
* [What Is Transform](/getting-started/what-is-transform.md)
* [Understanding the Interface](/getting-started/understanding-the-interface.md)

Next actions:

* [Create an Organization](/organizations-and-projects/create-an-organization.md)
* [Create a Project](/getting-started/create-a-project.md)
* [Add Teammates](/organizations-and-projects/add-teammates.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/getting-started/start-here.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.