> 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/release-notes/july-2026.md).

# July 2026

Photographer scheduling, from availability to check-in. Plus map view and multi-day sub-events.

## Photographer scheduling

Availability, assignment, notifications and check-in now live on one screen instead of across a spreadsheet, a group text and a phone call.

**Photographers mark their own days off** from their dashboard, and you can do it for them. For a contractor hired for peak season, set a date range and exclude specific days of the week within it.

**The Scheduling page shows the whole team's availability** in one calendar, red for unavailable and green for available.

**Conflicts are flagged as you build.** Assign someone on a day they've marked off, or into two events at once, and Schedulink tells you immediately. Nothing goes to staff while you're working, so you can balance the week before anyone hears about it.

**Publish one event or the whole week in a click.** Every assigned photographer gets one email and one text covering everything they're on that week, links included.

**Staff accept or decline from their dashboard** and can change their answer. You see who has responded on the Scheduling page.

**Check-in and check-out** happen from the photographer's dashboard on the day, more than once if a shoot has several sessions. You see it live on the event card.

## Also shipped

**Map view for events.** Events now has a Map view alongside List and Calendar. Filtered events appear as pins, clicking one shows the details, and all your usual filters carry over. Useful when you're routing photographers across a region.

**Create a week of sub-events at once.** In the Sub-events section click Add, choose Multiple, set a start and end date and a template, and Schedulink creates one sub-event per day. They inherit the parent's status.

**Salutations on contacts.** An optional Mr, Mrs, Dr field that shows in the display name and pulls into email templates.

**Clickable phone numbers, emails and addresses** in slide-in panels across Accounts, Events, Contacts and Employees. Phone numbers dial, emails open a compose window, addresses open in Google Maps.

**Your view stays where you left it.** Switch Events to Calendar or Map, go elsewhere, come back, and you're still in the view you chose.

**Custom fields in slide-in panels** for Accounts, Contacts and Employees, so you can see a full record without opening the page.

**Custom field sections in templates are now fixed-height tables**, so a template with many fields no longer stretches the page.


---

# 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/release-notes/july-2026.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.
