> 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/organization.md).

# Organization

Your studio's name, timezone, billing, and the rules that decide who automated emails go to.

This is where your studio's identity and its studio-wide behaviour live. **Setup > Organization**.

Most of it you set once during onboarding and never touch again, with the exception of the email rules further down, which are worth understanding properly.

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2Fc59Bjbsa4Zr5VR1Mq1T5%2Fimage.png?alt=media&#x26;token=db137635-1b7f-4c00-9ac7-1defbf8252c1" alt="" width="563"><figcaption></figcaption></figure>

## Your studio's details

| Field        | What it does                                          |
| ------------ | ----------------------------------------------------- |
| Studio Name  | Appears on every automated email your clients receive |
| Studio Email | The address used to connect your calendar             |
| Studio Phone | Internal only, so our support team can reach you      |

## Studio-wide settings

| Field                 | What it does                                             |
| --------------------- | -------------------------------------------------------- |
| Default Country       | Fills in the country when you add a new address          |
| Default Timezone      | Every time in Schedulink is set and shown in this        |
| Archive Offset (Days) | How many days after a job ends before it archives itself |

### Your timezone governs everything

Every time in Schedulink is both calculated and displayed in your studio's timezone, not the timezone of whoever is looking.

A 9am event reads as 9am for everyone: the coordinator at the studio, the photographer at home, and the editor working from somewhere else entirely. That's deliberate, because a shoot happens at a school at a particular hour, and everyone needs to be talking about the same one.

It also governs every email offset, every task due date, and the times in your exports.

Get it right before you go live. Changing it later means auditing work that's already timed.

### Archiving

Archiving doesn't delete anything. An archived job drops out of your normal lists so your team sees only live work, and out of the search bar at the top of the screen.

You can still find it using the archived toggle on the filter bar to the left of any list.

## Who automated emails go to

Schedulink sends emails based on contact roles, and two settings here decide how it finds the right people. They apply across your whole studio, not per template.

### Where it looks

When an email is due, Schedulink checks the event for contacts holding the role. This setting decides what happens next.

**If no recipient in the event** is the recommended option. Schedulink checks the event first, and if nobody there holds the role, it falls back to the contacts on the account. This is what most studios want, because it means an email still reaches someone when a job was booked without assigning contacts.

**Always** pulls everyone with that role from both the event and the account, every time. Use it when you want the account's standing contacts copied on everything regardless of who's attached to the job.

**Never** looks only at the event. If nobody there holds the role, the email doesn't send. This gives you tight control and it's also the setting most likely to be behind an email that never arrived.

### How it's delivered

When several people share a role, this decides whether they get one email or several.

**Group** sends a single email with everyone copied, so recipients can see one another. Sensible for a school office where the team expects to be on the same thread.

**Individual** sends separate emails, and nobody knows the others received it. Sensible for coaches across different teams, who have no reason to see each other's addresses.

{% hint style="info" %}
If a client says they never received an email, these two settings are worth checking alongside whether anyone at that account actually holds the role. See Email templates for how roles are chosen.
{% endhint %}

## Billing

The Billing button opens your subscription, where you can update your payment method, change your plan, and download past invoices.

Worth knowing: if a subscription lapses, editing is restricted across the app. That can look like a permissions problem, so if several people suddenly can't change anything, check billing before you check anything else.


---

# 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/set-up-your-studio/organization.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.
