# Setup Overview

Once you're logged in, follow these steps to get your studio running in ScheduleLink.

<details>

<summary><strong>Step 1: Import Your Data</strong></summary>

Get your studio into the system fast. You can enter data manually or import it in bulk.

<figure><img src="/files/sky70MsTifw36SoTtYxg" alt=""><figcaption></figcaption></figure>

You can import:

* **Accounts** — Schools, leagues, clubs
* **Contacts** — Administrators, coordinators, directors
* **Employees** — Photographers and staff
* **Past Events** — Last year's shoot schedule including school names, dates, times, and locations

With our new import feature, importing data is as easy as uploading the file. You should be able to see the past years events auto populate. If not, reach out and we're happy to help.&#x20;

For more information about data importation, [click here.](/help-center/setup-and-configuration/importing-data.md)

</details>

<details>

<summary><strong>Step 2: Configure Your Workspace</strong></summary>

Tailor ScheduleLink to match how your studio works. Go to **Setup** in the top nav to access:

* **Preferences** — Set your timezone and customize system tags
* **User Permissions** — Control what each team member can see and do
* **Organization** — Update your studio name and details
* **Integrations** — Connect Google Calendar or Outlook
* **Employees** — Add your team members and set their roles

<figure><img src="/files/Wj0xwEyCG0iPtCgLOI6s" alt="" width="563"><figcaption></figcaption></figure>

For more information about setting up your preferences, [click here.](/help-center/setup-and-configuration/preferences.md)

</details>

<details>

<summary><strong>Step 3: Build Your Templates</strong></summary>

Templates are the engine of ScheduleLink. This is the most important setup step.

There are four template types, all under **Setup**:

* **Event Templates** — The master workflow for a shoot type. Attach Task, Email, and Form templates here so everything generates at once.
* **Task Templates** — The repeatable work for a shoot — before, during, and after.
* **Email Templates** — Automated emails that go out at the right time with event details filled in automatically.
* **Form Templates** — Data collection forms sent to clients automatically.

<figure><img src="/files/bi8YZ4Vppa0qRXgNfn40" alt=""><figcaption></figcaption></figure>

For more information about creating templates, [click here.](/help-center/setup-and-configuration/templates.md)

Still unsure? Check out our [using ScheduLink guide here](/help-center/using-schedulink/the-basics.md).

</details>

<details>

<summary><strong>Step 4: Create Your First Event</strong></summary>

With your templates built, create an Event. Attach your Event Template and ScheduleLink generates the tasks, emails, and forms automatically.

**Example**: You create a Fall Portraits Event Template. Inside it, you attach all your task, email, form, employee requirements, location and shoot field templates. Once created, every time you create a Fall Portraits shoot, all of that generates automatically.

We recommend starting with one Event Template for your most common shoot type. Build from there.

<figure><img src="/files/wTmsgewzcTIhHqYwmd5q" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/WfcGPJLrlZglGfQWY4rv" alt=""><figcaption></figcaption></figure>

For more information about managing events, [click here.](/help-center/using-schedulink/managing-events.md)

</details>

***

**We're here to help**

If you need help with data import or setting up your first template, [email us](/help-center/using-schedulink/the-basics.md) or [book a call.](https://cal.com/seenuyellapu/45min)


---

# Agent Instructions: 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:

```
GET https://schedulink.gitbook.io/help-center/setup-and-configuration/setup-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.