# Help Center

## Help Center

- [Schedulink Help Center](https://schedulink.io/help-center/readme.md)
- [What Schedulink is](https://schedulink.io/help-center/start-here/what-schedulink-is.md): Studio management software for high-volume photography. What it does, and who it's for.
- [Finding your way around](https://schedulink.io/help-center/start-here/finding-your-way-around.md): The top navigation bar, what each menu holds, and how to get back to your dashboard.
- [Glossary](https://schedulink.io/help-center/start-here/glossary.md): What each word in Schedulink means, and the words studios often use instead.
- [Preparing your data for import](https://schedulink.io/help-center/start-here/preparing-your-data-for-import.md): The two templates, what goes in each column, and how to get your data in without a failed import.
- [Start your onboarding](https://schedulink.io/help-center/start-here/start-your-onboarding.md): Book a demo, send us your data, and we'll set you up on a call.
- [Setup overview](https://schedulink.io/help-center/set-up-your-studio/setup-overview.md): The order to do things in, and roughly how long each part takes.
- [Templates](https://schedulink.io/help-center/set-up-your-studio/templates.md): Templates are how Schedulink knows what a job looks like. Build them well and the rest of the app runs itself.
- [Task templates](https://schedulink.io/help-center/set-up-your-studio/templates/task-templates.md): Define a piece of work once, with its steps and its fields, then reuse it across every job type.
- [Email templates](https://schedulink.io/help-center/set-up-your-studio/templates/email-templates.md): Write a message once, drop in the account name and date automatically, and let Schedulink send it.
- [Form templates](https://schedulink.io/help-center/set-up-your-studio/templates/form-templates.md): Build the request you send to schools and leagues for rosters, team lists and shoot details.
- [Event templates](https://schedulink.io/help-center/set-up-your-studio/templates/event-templates.md): Assemble your tasks, emails and forms into one job type, with the timing that makes it run itself.
- [Deciding when to build a new event template](https://schedulink.io/help-center/set-up-your-studio/templates/deciding-when-to-build-a-new-event-template.md): When a job needs its own template, and when it's just a different answer.
- [Account, contact and employee templates](https://schedulink.io/help-center/set-up-your-studio/templates/account-contact-and-employee-templates.md): The extra fields your accounts, contacts and employees carry. Set once, rarely touched again.
- [Employees](https://schedulink.io/help-center/set-up-your-studio/employees.md): Add your team, invite them, and give them access to the right parts of Schedulink.
- [Permissions](https://schedulink.io/help-center/set-up-your-studio/permissions.md): Control what each person at your studio can see and change.
- [Preferences](https://schedulink.io/help-center/set-up-your-studio/preferences.md): The dropdown options your team picks from, across accounts, contacts, events, tasks and employees.
- [Organization](https://schedulink.io/help-center/set-up-your-studio/organization.md): Your studio's name, timezone, billing, and the rules that decide who automated emails go to.
- [Integrations](https://schedulink.io/help-center/set-up-your-studio/integrations.md): Put your jobs on Google Calendar or Outlook, so your team sees them where they already look.
- [Your dashboard](https://schedulink.io/help-center/run-your-studio/your-dashboard.md): Where you land, and how to see just the events and tasks that are yours.
- [Accounts and contacts](https://schedulink.io/help-center/run-your-studio/accounts-and-contacts.md): Add the schools and leagues you work with, and the people you deal with at them.
- [Events](https://schedulink.io/help-center/run-your-studio/events.md): Book a job, see everything about it in one place, and move it through its statuses.
- [Sub-events and your calendar](https://schedulink.io/help-center/run-your-studio/sub-events-and-your-calendar.md): You need sub-events to put photographers on a multi-day job. How they work, and why the parent leaves your calendar.
- [Scheduling](https://schedulink.io/help-center/run-your-studio/scheduling.md): Staff your week, publish it, and see who has accepted and who has turned up.
- [Tasks](https://schedulink.io/help-center/run-your-studio/tasks.md): Create, assign and complete the work behind every job.
- [Automated emails](https://schedulink.io/help-center/run-your-studio/automated-emails.md): How emails reach your accounts, how to check they arrived, and what to do when they didn't.
- [Forms](https://schedulink.io/help-center/run-your-studio/forms.md): Get student rosters and team lists from your accounts, with a deadline and a record of who has replied.
- [Working with lists](https://schedulink.io/help-center/run-your-studio/working-with-lists.md): Filters, columns, saved views and search. How to make Schedulink show you the work that matters to you.
- [Pricing and billing](https://schedulink.io/help-center/run-your-studio/pricing-and-billing.md): 10 USD per active employee per month. What counts, what doesn't, and how changes are billed.
- [Why can't I see a page or button?](https://schedulink.io/help-center/when-somethings-wrong/why-cant-i-see-a-page-or-button.md): A menu, button or record that isn't there for you. Almost always permissions, occasionally billing.
- [Why didn't my email send?](https://schedulink.io/help-center/when-somethings-wrong/why-didnt-my-email-send.md): An account says they never got it. Five causes, in the order worth checking.
- [My employee can't sign in](https://schedulink.io/help-center/when-somethings-wrong/my-employee-cant-sign-in.md): Expired invites, password resets going to the wrong address, and new starters who can barely see anything.
- [A form won't open](https://schedulink.io/help-center/when-somethings-wrong/a-form-wont-open.md): The code doesn't work, the link does nothing, or a form times out before it's submitted.
- [September 2026](https://schedulink.io/help-center/release-notes/september-2026.md): Custom fields in every export, one timezone for the whole team, and forms that send their own reminders.
- [August 2026](https://schedulink.io/help-center/release-notes/august-2026.md): Ask the assistant from inside the app, a Day view on the schedule, and form status at a glance.
- [July 2026](https://schedulink.io/help-center/release-notes/july-2026.md): Photographer scheduling, from availability to check-in. Plus map view and multi-day sub-events.
- [June 2026](https://schedulink.io/help-center/release-notes/june-2026.md): Job sheets, default values on custom fields, and Templates moving to its own menu.
- [May 2026](https://schedulink.io/help-center/release-notes/may-2026.md): Forms improvements, studio logo on forms, and calendar invites that show roles.
- [April 2026](https://schedulink.io/help-center/release-notes/april-2026.md): Forms launched, plus account, contact and employee templates.
- [March 2026](https://schedulink.io/help-center/release-notes/march-2026.md): Roles per event, bulk import, and automated event status changes.
- [Contact](https://schedulink.io/help-center/contact.md): Ask the assistant, check the common problems, or talk to a human.


---

# 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
This site has an agentic ask interface you may use to query the documentation dynamically 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/index.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.
