> ## 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.

# Set up Discord server tools

> Plan roles, channels and access before trying the Discord server tools.

> [!NOTE]
>
> Use these steps only in a server enabled by an ApexGenius operator. Ask your
> server admin which features are ready before you start.

Start with one quiet test channel and two people. One person makes a request.
The other checks it as staff. Use made-up details until you have checked who
can see each channel.

## Before setup

An ApexGenius operator must first allow server tools for the server. A server
admin then turns on each feature. Connecting Discord to an AI app does not do
this setup for you.

Use the bot your operator names. Check its app identity before you grant access.
Do not copy a test bot's key, server settings or channel choices to the official
bot. Never paste a bot token or an ApexGenius key in Discord.

The pilot covers **tickets, events, leave and approvals**. Other features stay
off. A server admin cannot turn on a feature outside the operator's pilot list.

## Choose roles and channels

| Place or role | Access and use |
| - | - |
| Help panel | Members read the help button. Staff post it. |
| Ticket category | Requester, staff and bot use one private channel per ticket. |
| Events channel | Members read and answer. Staff post events and reminders. |
| Leave channel | People who may ask and approvers see dates, reasons and decisions. |
| Approval channel | People who may ask and approvers see details and decisions. |
| Staff log | Staff and bot see actions and their outcomes. |
| Staff role | People who create events and work tickets. |
| Approver role | People who approve or deny leave and approval requests. |

Choosing a channel in setup does not make it private. Check its Discord access
first. Anyone who can read the leave or approval channel can read the requests
there. The requester must still be able to read the channel to answer questions.

People with Discord's **Administrator** permission can also see private
server channels. Do not collect details that must be hidden from those people.

## Run setup in order

You need Discord's **Manage Server** or **Administrator** permission for setup.
That is the person's permission; it is not a reason to give the bot admin access.

1. Check the bot's channel access. It needs to see and post in each chosen
   channel. Tickets also need the rights to make channels and set their access.
2. If you use leave or event roles, give the bot **Manage Roles**. Put its role
   above only the roles it needs to give and take back.
3. Use `/setup log-channel` to choose the staff log. The bot checks that it can
   post before it saves the choice.
4. Use `/setup timezone name:America/New_York`, or your own time zone.
   Without a choice, times use UTC.
5. Use `/setup staff-role` with `action:add` for each staff role. Pick a role
   that ordinary members do not share.
6. Use `/setup module` to turn on just the feature you will try. The four pilot
   names are `tickets`, `events`, `leave` and `approvals`.
7. Use `/setup view` to check the saved choices. Follow the feature's setup in
   the [server tools guide](https://docs.apexgenius.ai/guides/discord-server-tools.md).

Do not turn on extra Discord access just to make a button work. Read the error,
fix the named channel or role, and try that action again.

## Who may act

| Person | What they may do |
| - | - |
| Server admin | Set up features and roles; act as staff |
| Staff | Handle tickets and events; ask for leave or approval |
| Approver | Decide other people's requests in their chosen feature |
| Member | Open their own ticket and answer events; ask for leave or approval only if the admin allows everyone |
| Requester | Answer questions and withdraw their own waiting request |

Staff status alone does not make someone a leave or approval approver. Holding
an approver role does not let a person approve their own request. Finish the
server's own rules screen when a command asks you to do so.

The `/ask` agent has its own account rules. A Discord staff role does not give
someone access to another person's connected apps.

## Check access with a member

Make one harmless request. Check its card, the member's view and the staff log.
Try an action the member should not have, such as deciding someone else's
request. It should be refused. Then complete or withdraw the sample through the
normal buttons before removing its messages.

For a role, check both steps: that it was added and that it came off. A saved
decision alone does not prove Discord changed the role.

## Privacy and records

The bot does not send direct messages. Some replies are shown only to the person
who used a command. Request cards and replies follow their channel's access.

The bot keeps settings, request status and action records. Some features also
keep text, such as approval titles and idea text. It does not save ticket chat
as a transcript.

Leave reasons, approval details, notes, questions and answers are saved in a
work queue until their delivery job ends. They stay there while it waits or
tries again. The job's text is then cleared. This is separate from the saved
request record, which keeps facts such as its title, dates, people and status.

After delivery, Discord cards and replies hold those details. Deleting a card
can lose that text without closing the request. The bot cannot restore it from
a finished delivery job.

A staff log is not a backup of a request's details. Keep the original channel
or card while your team needs that record. Ask your operator about retention
before you use real personal data.

## Stop a test safely

1. Withdraw waiting requests and return people from active test leave.
2. Cancel test events. Stop the series too if it repeats.
3. Check that leave and event roles came off. Fix any failed role removal.
4. Close test tickets. Delete a channel only if you no longer need its chat.
5. Restore any settings you changed, then turn off the test feature if needed.

Turning a feature off is not a pause or cleanup. Due jobs may be skipped and
their text cleared. Turning it back on does not replay those jobs. Leave has
its own catch-up for overdue role changes, but that does not restore skipped
messages. Finish active work and check the result before switching it off.

## If setup fails

| What you see | Next step |
| - | - |
| Commands are missing | Ask the operator to check the app and server access. Reconnecting alone may not add them. |
| A feature is off | An admin checks `/setup module`. |
| Only staff may act | Check `/setup staff-role` and the person's role. |
| The bot cannot post | Check View Channel and Send Messages in that channel. |
| The bot cannot change a role | Check Manage Roles and the order of roles. |
| A card is slow to update | Check the saved status before trying again. Ask the operator to check the worker if it stays stuck. |
| The staff log is missing | Fix its channel access and run `/setup log-channel` again. Check whether the action already finished. |

Next, try one [team workflow](https://docs.apexgenius.ai/guides/discord-server-workflows.md).


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