> 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/new-to-transform.md).

# New to Transform

Get oriented on scope and access, then complete the core onboarding steps.

### Overview

Use this page for fast orientation. Use [Start Here](/getting-started/start-here.md) for the recommended setup path.

### Key Concepts

#### Scope model

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

#### Access model

Access is granted at the same scopes. Roles control actions within a scope.

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

### How It’s Used

Use this guide during onboarding. Use it again when setting up a new Organization.

### Benefits

* Faster navigation through consistent scope concepts
* Fewer access mistakes during rollout
* Cleaner setup for Organizations and Projects

### Setup Steps

#### Transform Platform Map

{% embed url="<https://transform-ai-git.github.io/transform-help-center-html/Transform_Platform_Map.html>" %}

#### First 10 minutes

Complete the steps in order.

{% stepper %}
{% step %}

### Configure profile

Set display name and core preferences.

* [Profile Configuration](/getting-started/profile-configuration.md)
  {% endstep %}

{% step %}

### Join or create a Project

Request Project access from an admin, or create the first Project.

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

{% step %}

### Add Teammates

Invite Teammates at the lowest scope that works.

* [Add Teammates](/organizations-and-projects/add-teammates.md)
  {% endstep %}
  {% endstepper %}

### Best Practices

* Use Organization scope for access to multiple Projects.
* Use Project scope for external collaborators.
* Adopt a single vocabulary for Blueprint and Project naming.

### Summary

Next workflows:

* Build a Blueprint: [Tutorial: Set Up a First Blueprint](/getting-started/tutorial-set-up-a-first-blueprint.md)
* Learn views: [Working with Views](/getting-started/working-with-views.md)
* Generate requirements: [Requirements Generation](/transformations/requirements.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/new-to-transform.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.