A clear start.
A working community.

Start with your Discord account.

Open the workspace and choose “Sign in with Discord”. Discord handles your password; Pochita uses the approved account identity to find your access.

Choose the server you manage.

Use My servers to open an available server. If it is missing, check that you signed into the intended Discord account and have the required server permissions.

Add Pochita when you are ready.

The server picker provides the Add bot action for eligible servers. You must be signed in first. Review the permissions on Discord before approving the invitation.

Give each role the right level.

Open Permissions & roles. Read the commands unlocked by each level, assign the appropriate Discord roles, then save your changes.

Choose what goes where.

In Logging, enable a category and select its destination channel. Save the settings before sending a test. Pochita creates and uses its own logging webhook in that channel.

A webhook lets the logging destination stay separate from the bot's normal command replies.

Check the result, then carry on.

Use Send test after saving a logging destination. Confirm that the message arrives in Discord. For command usage and access details, open the command documentation.

Keep your department in its own workspace.

Eligible members see their department sections after signing in. Membership, rank and any assigned management access determine which requests and actions are available.

Spawn requests begin in Discord. Authorized reviewers handle them on the website; the request records its approver and retrieval deadline.

Follow the missing permission.

If a test fails, check Troubleshooting and the destination channel's permissions. Check that Pochita can view the channel, send messages and manage its logging webhook.

If the workspace is empty, confirm your Discord account and server access. Department membership is checked by the bot; website styling never grants extra permissions.