> For the complete documentation index, see [llms.txt](https://schedulink.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://schedulink.io/help-center/set-up-your-studio/setup-overview.md).

# Setup overview

The order to do things in, and roughly how long each part takes.

Four steps take a new studio from an empty account to a booked job. They're in this order for a reason: each one depends on the last.

If we're handling your onboarding, we do steps one and part of three for you. See Start your onboarding.

## 1. Get your data in

Your accounts and the contacts at them. Everything else attaches to these, so nothing works until they're in.

Fill in one sheet and either send it to us or import it yourself, module by module. Preparing your data for import covers the columns and the traps.

## 2. Configure your workspace

Four settings pages, none of which take long.

Preferences defines the dropdown options your team picks from: account statuses, event types, contact roles, task types. Do this before you build templates, because templates draw on these lists.

Organization holds your studio name, timezone and the rules that decide who automated emails go to. Set the timezone correctly now, because everything scheduled is calculated against it.

Permissions controls what each person can see and change.

Integrations connects Google Calendar or Outlook.

## 3. Build your templates

This is the important one, and the part that takes real time. Templates are what make every job of the same type generate identically.

Build task, email and form templates first, then assemble them into event templates. [Templates](/help-center/set-up-your-studio/templates.md) walks through it in order.

Start with one event template for your most common job type rather than trying to model everything at once. Most studios end up with three to six.

## 4. Create your first event

With a template built, create an event and apply it. Schedulink generates the tasks, schedules the emails and sends the forms, all timed from the event date.

From there it's just work. Run your studio covers the daily side.

## Adding your team

You can do this at any point, but it's worth waiting until permissions exist so people land with the right access. Employees covers adding and inviting them.

## Stuck?

Data import and first templates are the two places studios get stuck, and both are quicker with help. Book a call and we'll work through it with you.


---

# 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://schedulink.io/help-center/set-up-your-studio/setup-overview.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.