> For the complete documentation index, see [llms.txt](https://bikecheck.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bikecheck.gitbook.io/guide/shop-owners/shop-holidays.md). # Shop holidays Closing for a while? Set a shop holiday, and riders can't book you for those dates. ## Set a holiday 1. On your **Dashboard**, find the **Vacation** card. 2. Set **From** and **Until**, and choose **Save**. ![The Vacation card at the top of the dashboard](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-8485e0978733fb24f7192be1077c4dc067400cfa%2Fvacation.jpg?alt=media) Riders who pick a date inside your holiday are warned before they send a request, and the request is refused. Walk-ins are covered too. Only the owner sets the shop holiday; **Clear** removes it. ## Bookings you already had If some bookings already fall inside the holiday, BikeCheck lists them under **Bookings inside your holiday**. Nothing is changed automatically: reschedule them with the rider or decline them yourself. ## Your team's holidays Team members set their own personal holiday on their Business dashboard. While they are away, nobody can assign them tasks. You see their dates under **Team holidays**. --- # 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://bikecheck.gitbook.io/guide/shop-owners/shop-holidays.md?ask=&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.