> 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/june-2026.md).

# June 2026

Job sheets, default values on custom fields, and Templates moving to its own menu.

## Shipped

**Generate PDF job sheets.** Click Generate PDF on any event and Schedulink builds a job sheet with the event details, contacts, assigned staff and notes. Print it and hand it to your photographer instead of pulling details from three places.

**Default values on custom fields.** Set a default on any custom field in a template and every new record built from it carries that value. Change the default later and it applies to existing records too, unless you've already edited that field on a particular record.

**Unarchive contacts and employees.** Click the archived option on the filter sidebar to see archived records, open one, and choose Unarchive. They come back exactly as they were, which is what you want when a seasonal photographer returns.

**Go-to date on the schedule calendar.** A calendar icon next to the date on the top bar. Click it, pick a date, jump straight there.

**Templates moved to its own menu.** Templates now sits in the main navigation rather than under Setup.


---

# 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/june-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.
