> 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/start-here/glossary.md).

# Glossary

What each word in Schedulink means, and the words studios often use instead.

The words below are what Schedulink calls things. Where you might call it something else, that's noted too.

## Account

One of the organisations you photograph for: a school, a district, a sports league, a club, a college, a university, a dance studio. You need an account before you can create an event for it.

## Contact

A person at an account. A principal, an athletic director, a league coordinator, a photo day coordinator. Contacts belong to the account, not to an individual event.

## Contact role

A label on a contact that decides which emails they receive. Several contacts at one account can share a role, and one contact can hold several. If nobody holds the role an email is looking for, that email doesn't send.

## Event

One job. A picture day, a graduation, a team shoot, a dance recital. The event holds the schedule, the staff, the tasks, the forms and the emails for that job. Sometimes called a *job* or a *shoot*.

## Sub-event

One day of a multi-day event. If an account is shot over Tuesday and Wednesday, that's one event with two sub-events.

## Group event

An event that has sub-events. You don't create a group event directly. Adding a sub-event to an event turns the parent into a group event automatically, and the parent stops being schedulable in its own right.

## Event status

Where an event is in its life. Six of them: Planning, Scheduled, Published, In Progress, Complete and Cancelled. Status decides whether emails send and whether the job appears on your connected calendar.

## Task

Anything a person has to do. Culling images, printing ID cards, chasing a roster. A task usually belongs to an event, but it can sit on an account on its own for work that isn't tied to a job. Some studios call these *service items*; in Schedulink they're tasks.

## Task type

A category you define to group tasks, such as pre-production or post-production. You choose the names.

## Task status

Where a task is in its life: Not Started, Ready, In Progress, On Hold and Completed. A task moves to Ready on its own when its start trigger is met, which is when the assigned person is told about it.

## Step

An optional sub-item inside a task. A task can have steps or none, and a task can be marked complete even if some of its steps are still outstanding.

## Template

Defines the shape of a record so you don't rebuild it every time. There are seven types: event, task, email, form, account, contact and employee. Task, email and form templates can be attached inside an event template, so applying the event template generates all of them at once.

## Custom field

An extra field you add to a template to capture something Schedulink doesn't have by default, such as expected head count, background choice or parking notes.

## Form

A secure request sent to contacts at an account to collect files or data, most often a roster or team list. Forms are attached to an event template with a send date, and the recipient verifies their email with a one-time code before the form opens.

## Job sheet

The PDF generated from an event using Generate PDF. It's what your photographers carry on the day. Some studios call this a *job card*.

## Employee

A member of your studio team: a photographer, a coordinator, an editor, an admin. Employees are assigned to events and tasks.

## Scheduling

The page where you assign employees to events, publish schedules, and see who has accepted, declined or checked in.

## Permissions

What each employee can see and do. Permissions are separate from contact roles, and giving someone a role does not on its own give them access. If something is missing from the app for one person, permissions are the first thing to check.


---

# 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/start-here/glossary.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.
