> 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/finding-your-way-around.md).

# Finding your way around

The top navigation bar, what each menu holds, and how to get back to your dashboard.

Everything in Schedulink is reachable from the bar across the top of every page.

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2Fb8fCLHJXCxCLyajCMDMV%2FScreenshot%202026-08-13%20at%207.36.41%E2%80%AFPM.png?alt=media&#x26;token=0e65fbb1-3bba-46bd-b0d0-a8c6dbc23e14" alt=""><figcaption></figcaption></figure>

## The main menu

Five of these open a list you can filter and sort. See Working with lists for how to shape what you see.

**Accounts** — every organisation you photograph for. Filter by type or status.

**Events** — every job. Switch between list, calendar and map views, and filter by date, status or location.

**Tasks** — all the work across your studio. Filter by due date, assignee or status to see what needs attention.

**Contacts** — every person at your accounts, searchable by name.

**Scheduling** — the studio's staff calendar. Assign photographers to events, publish schedules, and see who has accepted, declined or checked in. This is the view for whoever builds the schedule; if you just want to know what you're on, see Your dashboard.

The last two open dropdowns rather than pages.

## Templates

Seven kinds, each with its own page:

* Task templates
* Account templates
* Contact templates
* Employee templates
* Event templates
* Email templates
* Form templates

Event templates are the ones that pull the others together. Attach task, email and form templates inside an event template, and applying it to a job generates all of them at once.

## Setup

Five pages:

* **Preferences** — the dropdown options your team picks from, like event types and statuses
* **Employees** — add your team and archive people who've left
* **User Permissions** — what each person can see and do
* **Organization** — your studio's own settings, including how event emails find their recipient
* **Integrations** — connect Google Calendar or Outlook

## Getting back to your dashboard

Click the Schedulink logo in the top left from anywhere. Your dashboard shows your events, your tasks and your availability, and each panel can be switched between the whole studio's work and just yours.

## On the right of the bar

**Search** finds any account, event, contact, task or employee by name without leaving the page you're on. Results are grouped into tabs by record type.

**Notifications** alert you inside the app when a task is assigned to you, when you're mentioned in a note, or when you're scheduled for an event.

**Your profile** is the avatar at the far right. Click it, then My Profile.

## Using Schedulink on a phone

There's no app to download. Schedulink runs in your phone's browser, and it's the same Schedulink your studio uses on a desktop, with the same login.

Open app.schedulink.io in Safari or Chrome and sign in as usual.

It's worth adding to your home screen so it opens like an app rather than a bookmark. On an iPhone, tap the share button in Safari and choose Add to Home Screen. On Android, open the browser menu in Chrome and choose Add to Home screen.

That's how most photographers use it on a shoot day: checking what they're on, accepting a job, and checking in and out from the dashboard.

## Your profile

Three things live here, and the notification settings are the ones people go looking for.

### Personal information

Your photo, name, phone number and email. Keep it current, because this is what your colleagues see against schedules and notes.

{% hint style="warning" %}
The email address in your profile is only used for notifications. Your sign-in email is separate, can't be changed here, and is where password reset codes are sent.

So changing your profile email doesn't change how you log in. If you need your sign-in address changed, email us and we'll do it. Being able to change it yourself is on the way.
{% endhint %}

### Security

Change your password at any time.

### Emails and texts

Everyone controls their own. Nobody else can turn your notifications on or off, and changing yours doesn't affect your colleagues.

Four switches:

| Setting                 | What it sends                                          |
| ----------------------- | ------------------------------------------------------ |
| Note Mentions           | An email when someone mentions you in a note           |
| Task Assignments        | An email when a task assigned to you becomes ready     |
| Event Assignment Emails | An email when an event you're assigned to is published |
| Event Assignment Texts  | A text when an event you're assigned to is published   |

Alongside them, **Reminders** sends a summary of your open tasks and upcoming events, set to Daily, Weekly or Off.

If Schedulink is emailing you more than you'd like, this is the page to fix it, and it's worth pointing new team members at during their first week.

{% hint style="info" %}
If a menu or button described here isn't in your app, it's almost always a permission rather than a bug. Ask whoever administers your studio to check your permission set. Scheduling is the exception: it isn't permission-controlled yet, so everyone can see it.
{% endhint %}


---

# 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/finding-your-way-around.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.
