# Preferences

ScheduLink is built to match how your studio actually works. The Preferences page is where you define the options that appear in dropdown menus throughout the system — things like account statuses, event types, and employee roles.

Set these up once at the start. Everything you add here becomes available across accounts, events, contacts, and staff records.

***

### How to add an option

1. Go to **Setup > Preferences**
2. Find the list you want to edit (e.g., Account Status or Event Type)
3. Click **New +** in the section header
4. Enter a name (e.g., "High School")
5. Pick a color — this adds a colored badge to that option in your list views, making it easy to scan at a glance

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

<details>

<summary>Account Dropdowns</summary>

### Account Status

The current standing of the account with your studio.

<table><thead><tr><th width="220.0234375">Value</th><th>Description</th></tr></thead><tbody><tr><td>Active</td><td>Clients you're actively working with</td></tr><tr><td>Prospect</td><td>Potential clients or leads</td></tr><tr><td>On Hold</td><td>Clients paused or waiting on next steps</td></tr><tr><td>Lost</td><td>Clients that did not move forward</td></tr></tbody></table>

#### Account Type

Categorizes the organization so you can filter by market.

Suggested values:

* Elementary School, Middle School, High School, University, Corporate, Sports League

#### School District

Groups accounts together by region or administrative body. Add the districts your studio serves.

#### Address Type

Identifies locations used for shipping orders or conducting photoshoots.

Suggested values:&#x20;

* Primary, Shipping, Billing

</details>

<details>

<summary>Contact Dropdowns</summary>

#### Contact Title

The person's official job title at their organization.

Suggested values:&#x20;

* Principal, Vice Principal, Office Administrator, Teacher

#### Contact Role

Defines the function this person serves for your studio — for example, who do you call about scheduling vs. who handles yearbook orders.

Suggested values:&#x20;

* Primary, Scheduling, Yearbook, Data

</details>

<details>

<summary>Event &#x26; task dropdowns</summary>

#### Event Type

The specific category of the photoshoot.

Suggested values:&#x20;

* School Portraits, Senior Portraits, Graduation, Sports Teams, Clubs & Groups

#### Event Location

The environments or venues where your studio provides services.

Suggested values:&#x20;

* On-Campus (Indoors), On-Campus (Outdoors), In-Studio

#### Task Type

Categorizes to-do items by department or phase.

Suggested values:

* Pre-Production, Editing, Sales, Logistics

</details>

<details>

<summary>Employee dropdowns</summary>

#### Employee Title

Their official title at your studio.

Suggested values:&#x20;

* Photographer, Lead Photographer, Studio Manager, Studio Owner

#### Employee Role

The functional role they play in your team. Often linked to skills and used when assigning staff to events.

Suggested values:&#x20;

* Event Supervisor, Driver, Data, Posing

</details>

<details>

<summary>Global Tags</summary>

Tags work differently from dropdowns. You can apply multiple tags to a single account, contact, or event — and they work across all modules.

Use them for anything that doesn't fit neatly into a single dropdown: seasonal campaigns, client tiers, special handling notes.

Examples:&#x20;

* VIP, New Client, Season 2025-26

</details>

> **Tip:** You don't have to add every option upfront. Start with the values you use most. You can always add more as your team's needs become clearer.


---

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