LOA Requests
Manage Leave of Absence requests for department members.
The LOA (Leave of Absence) Requests module allows staff to formally request a period of inactivity. During an active LOA, the member is excluded from activity quota calculations and receives a configurable LOA role.
Configuration
Run /config or open the dashboard and navigate to LOA Requests.
Change the status from Disabled to Enabled.
Set the LOA Role — this role is applied when an LOA is approved and removed when it expires or is deleted.
Set the LOA Channel — all LOA submissions will be posted here for management to approve or deny.
Both settings required
LOA Requests will not function unless both the LOA Role and LOA Channel are configured.
Submitting an LOA Request
Use /loa request with:
- Time — Duration of the absence (e.g.
7 days,2 weeks) - Reason — Explanation for the leave
The request is posted to the LOA channel where management can Approve or Deny it. If approved, the LOA role is applied immediately.
Viewing Your LOA
Use /loa view to see details of your currently active LOA including start date, end date, and reason.
Managing LOA Requests
All active LOAs
Use /loa active to see a list of all currently active LOAs in the server, including who is on leave and when their LOA ends.
Administrating a specific LOA
Use /loa admin and select a user to:
| Action | What it does |
|---|---|
| List | View the member's full LOA history |
| Delete | End their active LOA immediately |
Deleting an LOA
Deleting an active LOA removes the LOA role from the user. Only active LOAs can be deleted — expired LOAs remain in history.
Clearing all LOA data
Irreversible action
This permanently deletes all LOA records for the server. It does not remove the LOA role from users — you must do that manually.
- Run
/server manage - Navigate to Introduction → Activity Notices → Erase LOA Notices
To clear only pending requests, select Erase Pending Requests from the same menu.