Set up your server.
One step at a time.

01. Add Pristine and check its role

1. Add Pristine to your server with an account that can add bots.
2. In Discord’s Server Settings → Roles, place Pristine above roles it needs to assign or moderate.
3. Grant permissions for your enabled features. Role assignment needs Manage Roles; moderation needs the selected kick, ban or timeout permission.
4. Run /setup and inspect /help.
5. Open Manage Servers, connect Discord and choose your server.

Check: Pristine is online and the dashboard loads.

02. Give your team specific access

1. The server owner opens Bot access.
2. Paste a Discord user ID, copied with Discord Developer Mode enabled.
3. Select feature permissions and save. Commands controls availability. The separate risky Command access & options permission controls member access rules and optional inputs; grant it only to trusted admins. Appointed accounts do not need server membership.
4. Review Risky permissions before granting Command access & options, Verification contact data, Server listing, Activity log, Backups or Member recovery.
5. Remove the appointment or uncheck a permission to revoke access. A new server owner must appoint their own admins.

Manage Server permission alone does not grant website access. Appointed admins cannot appoint other admins or expand their own permissions.

03. Configure member verification

1. Open Verification → Verification settings & panel editor.
2. Enable verification. Choose the verified role, optional unverified role and gate channel.
3. Email and IP collection start off. Contact the Pristine owner to request approval for your server, then choose the approved options and save.
4. Edit and publish the Discord panel. Pristine needs access to the channel and Manage Roles.
5. Open the verification link as a test member and review its permissions before authorizing.

Optional email/IP records are retained for 30 days. New settings do not broaden existing consent retroactively. The website owner edits verification wording; each server’s Verification panel controls collection within the Pristine owner’s approvals.

Check: the test member receives the selected role and sees the saved permission choices.

04. Configure AI moderation and anti-raid

1. Open AI moderation, connect its provider and select a moderation log channel.
2. Review content categories and link rules. Choose what is allowed, blocked and acted on.
3. Set confidence thresholds and staff exclusions. Test harmless examples and review feedback before applying stricter settings.
4. Open Anti-raid and set event limits, time windows and protective actions.
5. Review whitelist roles/users and save. Check permissions for each selected action.

Automated decisions can be wrong. Keep logs available and review member reports.

05. Set up Pristinepot

1. Choose a dedicated text channel with a clear warning. Avoid normal conversation channels.
2. Run /pristinepot with mode setup, your selected action and channel. All three options are required.
3. Set a log channel and any extra exempt roles through the command’s options.
4. Use mode status to inspect permissions and whether your account is exempt.
5. Use mode disable, with the required action/channel options, to turn it off.

Owners, bot operators, staff permission holders and exempt roles are skipped. Their test messages show a brief explanation and leave the action counter unchanged.

After successful moderation, Pristine attempts a private recovery notice. Kicks and completed softbans can include a single-use rejoin invite that expires after seven days. The bot needs Create Invite in a publicly visible channel. Closed DMs or missing permissions can prevent delivery. A timeout keeps the member in the server.

Inspect configuration and exemptions first. Do not test automatic kicks or bans on an unsuspecting real member.

06. Welcome, react and keep reminders visible

Open Modules in Server Manager, find the feature and choose Settings to edit welcomes, reactions, event logs, sticky messages, voice rooms or counters. Update its options and save.

Welcomer

Run /welcomer with mode setup and choose a channel. Edit title, text, footer and optional image. Personalize with {user}, {username}, {server} and {membercount}. Use mode preview before rollout. Invite tracking’s invited announcements are separate.

Automatic reactions

Run /autoreact with mode add, a trigger and emoji. Optionally restrict the channel or require an exact match. Inspect with status; use remove or clear to remove rules.

Sticky reminders

Use /stickymessage with required text, a required Messages or Seconds trigger, and a required amount. Seconds works without a message count and reposts on the next message after the interval; it is not an automatic countdown. Stop with /channel unsticky.

Event logs

Run /logs with mode setup. Channel is required. Run the command to choose the required events. In the private menu, select all the events you want, then click Save events. At least one event is required; Cancel leaves your settings unchanged. You can also tick multiple events in Modules → Server event logs → Settings. Test an edit or deletion after enabling. Deleted-image capture allows three Discord CDN files of 4 MB each, cached ten minutes. Old or uncached files cannot be recovered.

Live server counters

Run /serverstats mode:setup with Manage Server permission to create read-only channels for members, people, bots, roles and boosts. Pristine needs Manage Channels and View Channels. Counters refresh every five minutes. Use /serverstats mode:status to check setup, or /serverstats mode:disable to pause updates and keep the channels.

07. Create temporary voice rooms

1. Run /voice with mode setup and check its channel/category options.
2. Join the creation channel. Your new room receives controls in its own chat.
3. Use Lock/Unlock for joining, Ghost/Reveal for visibility, Rename for the name and Increase/Decrease for capacity.
4. The current owner controls the room. Another member can Claim it after the owner leaves.

Empty rooms are removed. Use mode status to inspect setup or disable to stop creating rooms.

08. Organize tickets and giveaways

Use /help tickets to find ticket setup and panel commands. Choose the staff role, support category and transcript channel, then create a test ticket. Check opening, claiming, handing off and closing from the relevant accounts.

Website support is separate: Contact us starts a conversation, and replies arrive in Inbox. Participants can close/reopen it and move closed conversations to recoverable Trash.

Giveaway hosts need Manage Server permission or a role whose decorated name contains “giveaway”. Inspect the command’s prize, duration and winner-count options, then test with a small event.

09. Backups, listings and activity

Backups creates and downloads role/channel/member-role snapshots. Confirm before replacing the latest snapshot and keep a downloaded copy before major changes. This is not a complete Discord message archive.

Server listing lets you set a description, category and invite, then submit for website-owner review. Only approved listings appear publicly; edits require another review.

Activity log shows recent dashboard changes and their actors. The server owner can grant each feature separately under Risky permissions.

10. Troubleshoot before changing settings

A command is missing

Check its enabled status in Commands, inspect Discord’s slash-command selector and use /help.

A role or moderation action fails

Check permissions and role position. Owners and protected members cannot be moderated.

Verification fails

Open the current verification link after saving. Check role hierarchy and service status. Consent may need reviewing again after settings change.

A bot admin sees a lock

The server owner must explicitly grant that feature. Membership does not replace an appointment.

A deleted image is missing

Capture must be enabled before deletion; file size, source and cache-age limits apply.

Use /status or service status for availability and changelogs. If the problem persists, contact support with the server ID, command, steps and error. Keep passwords, tokens and API keys private.