> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apexgenius.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Discord server tools

> Use tickets, events, leave and approval cards in an enabled pilot server. Learn setup, safe use and recovery.

> [!NOTE]
>
> Use these tools only in a server enabled by an ApexGenius operator. The pilot
> covers tickets, events, leave and approvals. If commands are missing, ask your
> server admin. Connecting Discord alone does not turn these tools on.

Use these commands inside Discord. They help your team handle requests and plan
events. The [Discord connection](https://docs.apexgenius.ai/integrations/discord.md) is a separate way to use
Discord from your AI app.

New here? Start with [server setup](https://docs.apexgenius.ai/guides/discord-server-setup.md), then pick a
[team workflow](https://docs.apexgenius.ai/guides/discord-server-workflows.md). This page covers the four
groups tried in the member walkthrough. The [other server tools](https://docs.apexgenius.ai/guides/discord-server-more-tools.md)
and [connected-app tools](https://docs.apexgenius.ai/guides/discord-server-connected-apps.md) are still in
development. Reading their guides does not turn them on.

## Start with one feature

A server admin uses `/setup module` to turn a feature on. Use `/setup timezone`
to set the server's time zone before you plan an event or a leave request.

Check who can read a channel before you use it for leave or approval requests.
Everyone who can read that channel can see the details, reasons and replies.
Choosing a channel in setup does not make it private. Use `/setup log-channel`
to choose a staff log, and check that channel's access too.

### Tickets

> [accordion] Set up the ticket panel
>
> A server admin sets up the panel once:
>
> 1. Use `/setup staff-role` to add the role that handles tickets.
> 2. Use `/setup tickets-category` to choose where ticket channels go.
> 3. Use `/ticket add-topic` to add a help topic. Add questions if members need to
>    give more details.
> 4. Go to the channel where members should ask for help. Use `/ticket panel` to
>    post the panel there.

Open a ticket from the server's help panel. Staff can mark it open, waiting or
closed. The saved status may appear before the channel and staff log catch up.
If Discord is slow, give those updates time to finish.

Staff should **Claim** a ticket before they reply. Use `/ticket list` to find
open work, or `/ticket assign` to choose its staff owner. A member can close or
reopen their own ticket. A closed channel stays readable. Use
`/setup tickets-archive` if closed tickets should move to a set category.

Keep solved tickets until your team no longer needs the chat. **Delete channel**
removes it for good. The bot does not save a copy of the chat. A member may have
two open tickets at once, with one per topic.

* `/setup tickets-auto-close` lets an admin choose 3, 7 or 14 days. It starts off.
* The timer runs while the ticket waits on the member. With auto-close on, a
  reminder arrives the next day with **I still need help**. Only the member who
  opened the ticket can use that button to bring it back to open. Staff can use
  **Back to open** on the main ticket card at any time while it is waiting.
* A reply typed in the channel does not reset that clock. The member must press
  **I still need help**, or staff must press **Back to open**.
* `/setup tickets-rating` turns on a 1 to 5 score when a ticket closes. It starts off.
* Only the member who opened the ticket can rate it. If a staff log is set, they
  can also add a comment that goes to that log.
* Staff use `/ticket stats period:30` to see counts and scores for the last 30
  days. They can also choose 7 or 90 days.
* **Forget the task** clears a task link that was never confirmed. Check the task
  app first. This button does not delete a task in that app.

### Events

Staff use `/event create` to make an event. Pick the date and a time with AM or
PM. The time you enter uses the server's time zone. Check the preview, then
press **Post it**. The posted time is shown on each reader's own clock.
Set `places` to limit how many people can come. With the usual **Yes**, **Maybe**
and **No** answers, only **Yes** takes a place.

Once the places are full, the next person who says **Yes** goes on the waiting
list. If someone gives up a place, or staff raise the limit, the first person
waiting moves in. They get a reply under the event card. People on the waiting
list do not get the event's reminders or role.

You can set your own answers when you create the event. Every named answer
counts as coming and shares one limit. For example, **Early** and
**Late** do not have their own limits. **Can't come** is always an option.

You can also add repeat dates, up to three reminders and an attendee role. The
role is removed when a person leaves or the event ends or is cancelled. Someone
who still needs that role for another event keeps it. The bot must have permission
to manage the role.

Answers, reminders and the attendee role cannot be changed after the event is
made. Check these choices in the preview before you press **Post it**.

> [accordion] Move an event, add it to a calendar or stop a repeat
>
> Use **Manage** on the card or `/event reschedule` to move an event. Use
> `/event list` to find upcoming dates. The answers stay with a moved event.
>
> The calendar buttons let each member add the event to their own calendar. The
> bot does not write to it. After a move or cancel, each member must fix their
> calendar entry too.
>
> A repeat posts its next card after the current event ends. Its answers start
> empty. Use **Manage** on the current card to cancel the whole series. Cancelling
> one date is not the same as stopping the series.
>
> `/event digest` posts one **Coming up** card with the next two weeks of public
> events. Use `/event digest stop:True` to remove it.

### Leave requests

An admin uses `/leave setup` to choose the request channel and who can decide.
They can also choose an on-leave role and a **Who is away** card.

Use `/leave request` to give your dates and a reason. Only staff can ask at first;
an admin can allow all members. An approver can approve, deny or ask for more.
You cannot approve or deny your own leave request.

Pick the first and last day. Add a year only when you need it. A request can span
New Year. It cannot start in the past, overlap your own open leave, or last more
than 90 days. Use `/leave list` if you are staff or an approver and need to see
who is waiting or away.

**Ask for more** posts a question under the card. Only the person who asked for
leave can press **Answer** to reply.

For approved leave, the role starts at midnight on the first day and ends after
the last day, in the server's time zone. If that start time has passed when leave
is approved, the role is added shortly after approval.

Use `/leave return` to end your own leave early. Use `/leave cancel` to withdraw
your own waiting request or approved leave that has not started. An approver can
press **Mark returned** on someone's card once their leave has started.

Keep the leave feature on while people are away. If it is turned off, overdue
role removal waits until it is turned on again.

### Approval requests

An admin uses `/approval setup` to choose the channel and approver role. Only
staff can ask at first; the admin can allow all members.

Use `/approval ask`, or right-click a message and choose **Apps**, then **Ask for
approval**. The card has **Approve**, **Deny**, **Ask for more** and **Withdraw**.
You cannot approve or deny your own request.

Write the title as the choice you want made, such as "Use this draft reply".
Keep the title to 100 characters and the details to 1,000. Approve or deny with
a short note so the next step is clear. Approval records the team's choice. It
does not run a task in another app or approve an AI tool call.

**Ask for more** posts a question under the card. Only the person who made the
request can press **Answer** to reply.

If someone deletes the card:

1. Use `/approval mine` to find the number of your waiting request.
2. Use `/approval withdraw number:12` to withdraw your own request. Replace `12`
   with its number.
3. An approver can use `/approval list`, then `/approval deny number:12`, to deny
   it by number.

These commands work in the server where the request was made. A finished request
no longer uses one of your ten waiting places. Deleting the card alone does not
finish the request.

## What happens to the text

Text you enter in the request fields is shown as plain text. It cannot add a
heading, bold text, a hidden link or a ping to the card.

The bot saves text in a work queue while it waits to post or tries again. This
includes leave reasons, approval details, notes, questions and answers. When
that job ends, its text is cleared from the queue. If delivery is stuck, the
text stays there until the job ends.

The request record is separate. It keeps facts such as the approval title,
dates, people and status. To redraw a card, the bot reads the leave reason or
approval details from Discord. Once the delivery job has ended, deleting that
card loses the bot's source for those details. The bot cannot restore them.

## Check the result

Try one request as a member and decide it as an approver. Check both what the
member sees and the staff log. For events, have enough people join to fill the
places, then check that the next person waits.

Timers need the bot to be running. A scripted clock check does not prove that a
real reminder or midnight role change ran. Keep those checks separate when you
test the bot.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.