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

# Preferences

The dropdown options your team picks from, across accounts, contacts, events, tasks and employees.

Schedulink is built to match how your studio actually works, and Preferences is where you define the options that appear in dropdowns throughout the app: account statuses, event types, contact roles, task types and more.

Set these up before you build your templates, because templates draw on these lists. A template can't offer an event type you haven't created.

**Setup > Preferences**.

## Adding an option

1. Find the list you want to edit, such as Account Status or Event Type
2. Click **New +** in that section's header
3. Enter a name
4. Pick a colour, which shows as a badge in your lists and makes them far quicker to scan

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2FaJrP6nN9JwsKmfQvZ5qg%2Fimage.png?alt=media&#x26;token=c0893c9d-7ec8-45c2-928b-4d1d7683ce24" alt="" width="563"><figcaption></figcaption></figure>

You don't need to add everything up front. Start with the values you use most and add more as your team's needs become clear.

## Deleting an option that's in use

If records are already using a value, Schedulink won't quietly remove it. Instead it shows you the list of records using it, so you can open each one, change it to something else, then come back and delete.

That's a small amount of work up front and it means you never end up with records pointing at a value that no longer exists.

## Account dropdowns

**Account Status** is the client's current standing with your studio. Common values are Active for clients you're working with, Prospect for leads, On Hold for clients paused or waiting, and Lost for those that didn't go ahead.

**Account Type** categorises the organisation so you can filter by market: elementary school, middle school, high school, university, sports league, corporate.

**School District** groups accounts by region or administrative body. Add the districts you serve.

**Address Type** identifies what a location is for, typically Primary, Shipping and Billing.

## Contact dropdowns

**Contact Title** is the person's real job title at their organisation: principal, vice principal, office administrator, athletic director, teacher. It's there so your team knows who they're speaking to.

**Contact Role** is what that person does for you, and it controls which automated emails they receive. Common values are Primary, Scheduling, Yearbook and Data.

Those two are easy to confuse and they do completely different jobs. Title is information; role is routing. See Preparing your data for import for the full explanation.

## Event and task dropdowns

**Event Type** is the category of job: school portraits, senior portraits, graduation, sports teams, clubs and groups.

**Event Location** describes the setting: on campus indoors, on campus outdoors, in studio.

**Task Type** groups work by department or phase: pre-production, editing, sales, logistics.

## Employee dropdowns

**Employee Title** is their title at your studio: photographer, lead photographer, studio manager, owner.

**Employee Role** is the function they perform on a job, and it's used when assigning staff to events: event supervisor, driver, data, posing.

## Global tags

Tags work differently from dropdowns. You can apply several to one record, and they work across every module rather than being tied to one field.

Use them for anything that doesn't fit a single dropdown: seasonal campaigns, client tiers, special handling notes. Values like VIP, New Client or Season 2026-27.


---

# 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/preferences.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.
