> 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/mail-out/mail-out-2.md).
# Removing staff from a Group
We get it - it happens. Sometimes there's a couple instructors that get the wrong calendar. Or perhaps they changed their commitment level for the season - part time to full time, or vice versa, etc. If only they told you a few weeks ago!
Well, that just means you need to send them a request to fill out a new Availability calendar.
The first step here is removing the instructors from the group they're in. To get started, head to **Mailout**.
The first order of business is finding the instructors you'd like to remove. If you haven't yet sent them the request to fill out their calendar, they'll fall under the **Ready to send** tab. If you already sent them a request, then they'll land under the **Sent** tab or the **Response** submitted tab, depending on how far along they got with the original request.
Select the folks that you want to remove from the availability group and click Remove from avail. group on the right hand side of the page.
You'll get a prompt to confirm the action. Of course, if the answer is yes, smash the **Remove from group** button.
You've now removed them from their previous Availability group. They'll disappear from the Mailout tab until you've added them to another group...
...which you can do by clicking on the yellow heading to reassign them.
All sorted out! Like it never even happened.
***
## Sending Availability requests
To get started with sending requests, head to the **Mailout** tab (top panel.) You'll land in the **Ready to send** tab. This is where the staff that you just added to the group are sitting - waiting for an action. If you selected a particular date to send your calendars, then these folks will sit here patiently until that date.
{% hint style="info" %}
**NOTE:** Scheduled mailouts will be sent at 10 am local time. Automated reminders are sent between 10 am and 11 am local time.
{% endhint %}
If you selected send manually, then you'll need to select the folks you want to send a request to.
Once you've selected everyone you'd like to send a request to, click Send availability request in the action panel on the right.
You'll see a prompt to confirm. If you're ready, hit **Yes, email them**.
And then you're off to the races. In the **Sent** tab, you'll be able to track when the request was sent, when it was viewed, and when the last reminder was sent. You can also select staff and send them a reminder if you need to (if all the automated ones have run out).
Once an instructor submits their availability, it'll be visible in the **Responses** section. We'll cover that in [the next article](/flaik-knowledge-base/for-sups-managers/availability/responses.md).
{% hint style="success" %}
😤 **Phew!** You've made it to the end of Mailout. Might be time to crack a cold one.
{% 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/mail-out/mail-out-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.