> 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/run-your-studio/your-dashboard.md). # Your dashboard Where you land, and how to see just the events and tasks that are yours. The dashboard is what you see when you log in, and it's where you get back to by clicking the Schedulink logo in the top left from anywhere. It holds two or three panels, left to right: your events, your tasks, and, if your studio has it switched on, your availability. ## Seeing only what's assigned to you This is the one most people miss. Both the events panel and the tasks panel have a dropdown at the top. Switch each to **My events** and **My tasks** and the dashboard shows only the work assigned to you, rather than everything happening across the studio. So if you're a photographer wondering what you're on this week, that's the answer: open your dashboard and switch both panels to yours. Switch back to **All events** and **All tasks** when you want the studio-wide view, which is what a coordinator or an owner usually wants. {% hint style="info" %} **A panel that looks empty is usually the dropdown, not a fault.** My tasks with nothing assigned to you looks exactly like a broken page. Check the setting at the top of the panel before assuming something is wrong. {% endhint %} ## Events The events panel lists what's coming up. When you've been assigned to an event and the schedule is published, you can **accept or decline** it from here. If you make a mistake you can change your answer. On the day, you **check in and check out** from the same place, and you can do it more than once if a shoot has several sessions. Your studio sees it happen live on the event card. ## Tasks The tasks panel lists work that's ready for you, with what's overdue and what's due today called out. A task only appears once it reaches **Ready**, which happens automatically when its start trigger is met. If someone says a task hasn't reached them, that's the first thing to check. ## Availability Availability is the third panel, on the right. **If your dashboard shows only two panels, availability is switched off for your studio.** It's off unless a studio asks us to turn it on, because some would rather build the schedule themselves without staff marking themselves unavailable. If you'd like it on, get in touch and we'll enable it. When it is on, this is how it works. **Everyone is available by default**, so you're only ever marking the time you can't work. Set a date range here and your studio sees it in red on the Scheduling page. If someone tries to assign you on one of those days, Schedulink flags it. From your own dashboard you can set **one date range**, which covers most things: a holiday, a week away, a few days off. For anything more involved, like being unavailable every Monday and Tuesday through the autumn, someone at your studio with access to Employees sets it on your employee record. Whatever they set shows here on your dashboard. {% hint style="warning" %} **There's only ever one set of dates, and the last save wins.** So if you book a holiday and your studio later sets something else on your record, your holiday is replaced rather than added to. The same happens in reverse. Worth a word with whoever builds your schedule before either of you changes it, especially in the middle of a season. {% 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://schedulink.io/help-center/run-your-studio/your-dashboard.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.