> 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/run-your-studio/accounts-and-contacts.md).

# Accounts and contacts

Add the schools and leagues you work with, and the people you deal with at them.

An **account** is an organisation you photograph for: a school, a district, a league, a college. A **contact** is a person at one of them, like the office manager or the athletic director you deal with.

You need an account before you can book a job for it, so this is where a new client starts.

## Adding an account

Go to **Accounts** and click **Add**, top right.

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2F3ga7sEPtUMOr1vWlEBP8%2Fimage.png?alt=media&#x26;token=ebf51d76-c00d-4603-971e-21cf73992e88" alt="" width="375"><figcaption></figcaption></figure>

Status, type and address type come from lists you control in **Setup > Preferences**. If a value you want isn't there yet, add it in Preferences and come back.

If you're bringing in a lot of accounts at once, don't do it one at a time. See Preparing your data for import.

## What's on an account

Everything about that organisation lives on one page.

| Section             | What's in it                                                                                                                                                                        |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Account information | Status, type and the top-level details                                                                                                                                              |
| Addresses           | As many as you need, each with a type and a name. Useful when a school shoots in the gym one day and the auditorium the next, because you pick the address when you create an event |
| Contacts            | Everyone you deal with there                                                                                                                                                        |
| Events              | Every job for this account, upcoming, past and archived                                                                                                                             |
| Tasks               | Work tied to the account or its events                                                                                                                                              |
| Attachments         | Contracts, logos, reference files                                                                                                                                                   |
| Activity log        | Every change, who made it and when                                                                                                                                                  |
| Notes               | Internal notes for your team. Pin the important ones, and tag a colleague to notify them                                                                                            |

{% hint style="info" %}
An attachment added to a note can't be taken off again, so check you've picked the right file before saving.
{% endhint %}

## Adding a contact

Two ways, and one is better.

**From the account.** Open the account, scroll to Contacts, click Add. The contact is linked to that account automatically, which is why this is the way to do it.

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2FvSwOk6zjo2zMMqvH3pqK%2Fimage.png?alt=media&#x26;token=26ebfb25-06e1-4dcd-88f1-fa2f9475ea80" alt="" width="563"><figcaption></figcaption></figure>

**From the Contacts page.** Go to Contacts, click Add, then choose the account they belong to.

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2FvuqAbbkhX3HOC27VoMiN%2Fimage.png?alt=media&#x26;token=771e5d9e-85aa-4596-98cf-6d0ca6779b76" alt="" width="375"><figcaption></figcaption></figure>

A contact belongs to one account. If the same person looks after two schools, add them separately under each one.

## What's on a contact

| Section             | What's in it                             |
| ------------------- | ---------------------------------------- |
| Contact information | Name, title, roles and how to reach them |
| Events              | Jobs this particular person is linked to |
| Attachments         | Files specific to them                   |
| Activity log        | Change history                           |
| Notes               | Internal notes about this person         |

{% hint style="warning" %}
**Title and role do different jobs.** Title is their real job at their organisation, like Principal or Head Coach, and it's there so your team knows who they're talking to. Role is what they do for you, and it's the only thing that decides which automated emails they receive.

Schedulink sends to roles, not to names. If a school says they never got an email, check that somebody there actually holds the role that email is looking for. See Preparing your data for import for the full explanation.
{% endhint %}

## Downloading an account

Open the account, click the **three dots** at the top of the page, and choose **Generate PDF**.

You get the account's details, its contacts with their roles, and its custom fields as a document. Useful when someone outside Schedulink needs the picture, like a lab or a new coordinator who hasn't been set up yet.

For a list of accounts rather than one, use **Export** on the Accounts page instead. See Working with lists.

## When you stop working with someone

Archive rather than delete, so you keep the history of what you shot for them.

Archived accounts and contacts drop out of your normal lists, and out of the search bar at the top of the screen. To see them again, use the archived toggle on the filter bar to the left of any list, which is also how you bring back a school that returns next season.


---

# 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://schedulink.io/help-center/run-your-studio/accounts-and-contacts.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.
