> 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/quick-start-guide.md).

# Quick Start Guide

Create an Organization and Project, then set navigation defaults for daily work.

### Overview

Use this guide after sign-in is working. The outcome is a working Organization and Project.

{% columns %}
{% column %}
**What is covered**

* Create an Organization
* Create a Project
* Learn the core navigation patterns
* Create a baseline Save View for repeatable reviews
  {% endcolumn %}

{% column %}
**At a glance**

* **Time:** \~15–30 minutes
* **Access:** Account Admin for Organization creation + Project creation permission
  {% endcolumn %}
  {% endcolumns %}

{% hint style="info" %}
Screenshot placeholder: account navigation with **Organizations** highlighted.
{% endhint %}

### Key Concepts

* **Organization**: container for a client, department, or business unit
* **Project**: delivery container inside an Organization
* **Save View**: stored view configuration for repeatable lists

### How It’s Used

Use this guide during initial rollout. Use it for repeatable onboarding of additional Organizations.

### Benefits

* Faster setup for the first Project
* Cleaner navigation and fewer “lost in scope” issues

### Setup Steps

#### Prerequisites

* Sign-in is working.
* An Organization name is available (client, department, or business unit).
* A Project name is available.

{% hint style="warning" %}
If Organization or Project creation is not available, request access from an admin.
{% endhint %}

Follow the steps in order.

{% stepper %}
{% step %}

### Create an organization

Organizations separate work by client, department, or business unit.

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

{% hint style="info" %}
Screenshot placeholder: Organizations list with **New organization** highlighted.
{% endhint %}
{% endstep %}

{% step %}

### Create a Project

Create a Project inside the new Organization.

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

{% hint style="info" %}
Screenshot placeholder: organization header with **New project** (or **Add project**) action highlighted.
{% endhint %}
{% endstep %}

{% step %}

### Learn the interface basics

Get oriented on navigation, scope, and search.

* [Understanding the Interface](/getting-started/understanding-the-interface.md)

{% hint style="info" %}
GIF placeholder: switch organization → project and point out breadcrumbs + global search.
{% endhint %}
{% endstep %}

{% step %}

### Create a baseline Save View

Save Views reduce rework during weekly reviews.

1. Navigate to **Tasks** or **Requirements** in the Project.
2. Apply a minimal filter set, such as `Status != Complete`.
3. Select **Save view** (or equivalent action).
4. Name the view with intent, such as `Team — Weekly review`.

{% hint style="info" %}
GIF placeholder: create a filtered list, then save it as a team view.
{% endhint %}
{% endstep %}
{% endstepper %}

### Best Practices

* Create a small first Project and iterate.
* Establish a naming pattern before creating many Projects.
* Confirm access scope before inviting external stakeholders.

### Summary

Common next workflows:

* Add Teammates: [Add Teammates](/organizations-and-projects/add-teammates.md)
* Understand access scope: [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md)
* Build structure before scaling: [Blueprint Fundamentals](/blueprints/blueprint-fundamentals.md)
* Customize how you work: [Working with Views](/getting-started/working-with-views.md)
* Start capturing requirements: [Requirements Generation](/transformations/requirements.md)
* Hands-on walkthroughs: [First Steps Tutorials](/getting-started/first-steps-tutorials.md)

Support routing:

{% hint style="info" %}

* Sign-in support: [Login Problems](/troubleshooting/login-problems.md)
* Troubleshooting: [Getting Help](/troubleshooting/getting-help.md)
* Support request: [Contact Support](/resources/contact-support.md)
  {% endhint %}


---

# 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/quick-start-guide.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.