> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/availability/creating-a-calendar/creating-a-calendar-2.md).
# Setting Required Staff & Daily Limits
Now that you've created your day types, you've got an opportunity to add in the required staff you need for that day and the Daily Limit.
### **Required Staff:**
* The required staff is an internal number based on how many instructors that you anticipate needing for this particular day. This could be based on historical numbers plus a growth factor for this season.
* The Required Staff number will appear in the responses section of Availability to let you know how you're tracking with matching the number of staff signed up for that day vs the number of required.
### **Daily Limit:**
* The number entered into this field will set a cap for how many instructors can select that date when they're completing their availability (on a first come/first served basis).
* The idea here is to ensure that you cap the days where you usually don't need a tonne of staff so that they have to commit to days when you actually need them.
* Ex: if the Daily Limit is set to 25, only 25 instructors will be able to sign up for this day in order to meet their commitment.
If the Daily Limit box is left empty, it will not cap the number of instructors that can sign up for the day.
Click **Done** to complete setting up the calendar.
{% hint style="success" %}
Nice one! Calendars are the foundation for everything in Availability. Head to the next section, [creating a group](/flaik-knowledge-base/for-sups-managers/availability/creating-your-group.md), if you're ready to move on.
{% 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://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/availability/creating-a-calendar/creating-a-calendar-2.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.