> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Set up Custory quickly and move into building your first useful journey.

Use this path when you want the shortest reliable route from signup to a first journey the team can review.

## 1. Create or join a workspace

If you were invited to an existing workspace, accept the invite and use that workspace. Do not create a duplicate workspace for the same team.

If you are starting from scratch, create one workspace for the product, product area, or operating team that will own the journey.

If you add a company website during workspace creation, Custory can use it to generate starter context. Treat that as a draft, not validated customer truth.

Read [Workspace](/workspace) for the full workspace model, or [Manage your team](/team-management) for roles and invitations.

## 2. Choose one narrow journey

Pick one journey that matters now.

Good first choices:

* new user onboarding
* activation
* trial to paid
* support escalation
* renewal risk

Avoid starting with the full customer lifecycle. A narrow first journey is easier to build, review, and improve.

## 3. Choose a starting path

From the dashboard, choose one:

| Path               | Use it when                                                                                        |
| ------------------ | -------------------------------------------------------------------------------------------------- |
| **Import with AI** | A focused website, repository, Notion source, or available Figma source already explains the flow. |
| **Use a template** | You want a proven starting structure and can adapt it quickly.                                     |
| **Start blank**    | The journey is new, hypothetical, or no source is trustworthy yet.                                 |

Read [AI journey imports](/ai-journey-imports) or [Journey templates](/journey-templates) when you need the detailed setup path.

## 4. Invite the initial editors

Start with a small editor group.

Good early editors are usually:

* founder or product lead
* one support or customer-facing teammate
* one engineering lead or product engineer
* one design or research owner if relevant

Use viewers for people who need visibility without edit access. Read [Manage your team](/team-management) for roles and invitation details.

## 5. Connect one useful integration

Do not connect every tool during setup.

Start with one integration that removes real friction:

* Slack or Discord for updates
* GitHub, Jira, or Linear for follow-up work
* Notion or Figma when they already hold useful journey source material
* PostHog or Stripe when metrics or signals should stay connected

Read [Integrations](/integrations) when you are ready to choose more intentionally.

## 6. Continue to your first journey

Once the workspace exists, the first journey is chosen, and the starting path is clear, move into the hands-on guide.

Read [Your first journey](/build-your-first-journey) to shape the journey, add stages and steps, attach items, and use it in a real review.