Leave of absence

Requesting leave

A member who will be away asks for leave with /loa, or with Request leave on their profile on the website, giving the dates they are gone (their first and last day away, up to a year) and a short reason. That files a request for your team to look at; nothing is granted until someone with the Leave permission (or a server admin) says so, unless your server approves leave automatically (see Deciding leave in Discord). A request cannot overlap leave they already have or have asked for.

The reason stays private: the member, your leave staff and server admins see it, and the Discord log only says that one was given. Their leave is listed on their profile, where they can cancel a request still waiting, or approved leave that has not ended yet. A server admin can also put a member on leave directly, with Set leave on the member's profile, approved at once.

The Leave of absence module has to be on, under Modules on the server's Settings.

Reviewing leave

Requests land in the Leave column on the Members page, on the row of the member who asked, where a server admin or anyone with the Leave permission (on Settings) can click the request to approve or decline it. A server admin can also decide it on the member's profile. Moderators see the Leave column too, without the reasons, and cannot decide.

While a request is waiting or somebody is away, the list opens sorted by leave: open requests first, then members away right now, then upcoming leave, so nothing goes unnoticed on a long list. The Dashboard's Leave requests tile always opens it that way. Click any other column header to sort by that instead. Approved leave shows in the same column and on the member's profile, so your staff can see they are away.

While a member is on approved leave they are excused from your guild's requirements for the window. Qutie stops chasing them: no nag to sign up for events, no request to update their profile fields, and no VOD reminders. It also drops them from the VOD requirement for any cycle they are away, and they never pick up a strike for an event they simply did not sign up for. Their merit score leaves out the events and days they were away. An On leave mark shows wherever officers would otherwise expect a response (an event's Not responded list and its sign-ups, a game's Members list), so nobody chases them by hand.

Signing up is still opting in. If a member on leave signs up for an event anyway, that one is on them: they get the start ping and, if they no-show, the normal strike. Leave silences the reminders and requirements you never took on, not the ones you did.

Deciding leave in Discord

A server admin opens Leave settings at the top of the Members page and picks a Requests channel. Every new request is then posted there with Approve and Decline buttons, which work for anyone with the Leave permission and for server admins. Requests already waiting are posted as soon as you pick the channel. Once a request is decided, on the website or in Discord, its post says who decided it and the buttons go.

• Ping one or more roles on each new request, so your leave staff hear about it.
• Approve automatically: every request is approved as it is filed. The post then only tells your staff, with no buttons. This works with no channel too.
• DM them the decision: Qutie DMs the member when their request is approved or declined.

The post shows the reason, so pick a channel only your staff can read. With no channel set, leave works on the website only.