Configure a claim process that fits your community.

Getting started

Install Claims-bot, place its role correctly, and choose the text channel where members will submit claims.

1. Add Claims-bot to your server. You need permission to manage the server during installation.
2. Position the bot role. In Discord’s role list, move Claims-bot above every completion role it should grant or remove.
3. Check channel access. The bot needs to view the claims channel, send messages, create and manage public threads, read message history, and add reactions.
4. Open the dashboard. Choose a server, select the claims channel, configure at least one completion role, and save.
5. Test with two members. Submit a claim, complete the participant requirements, and confirm that the roles and thread behave as expected.

Dashboard settings

Templates and variables

The initial claim template validates typed messages and defines the form submitted through the claim panel. In panel mode, {claimed} becomes a searchable member picker, {claimant} and {server} are automatic, and the form variables below become modal controls. Put guidance in parentheses immediately before a field, such as Brief History: (How long have you known each other?) {text}, to use that guidance as the input placeholder without posting it in the finished claim. Forms longer than one Discord modal continue across private pages. Claims-bot then publishes the correctly formatted claim automatically. Participant templates use the same guided controls in the claim thread.

Example initial claim

**Superior Template:**

**Claiming Superior:** {claimant}
**Claimed Participant:** {claimed}

**Brief History:** {text}
**Open or Closed Dynamic:** {status}

**Rules for the inferior:**
> {text}

Example claimed-partner template

**Claimed Participant:** {claimed}
**Consent to Dynamic:** {approval}

**Rules for the Superior:**
> {list}

**Pledges:**
> {text}

Discord markdown is removed from modal labels so prompts stay readable, then reapplied when the completed template is posted. Modal forms with more than five interactive fields are split into sequential pages and retain progress between pages. Servers can instead let participants complete copyable templates as matching messages in the claim thread; Claims-bot validates and republishes those as canonical responses. The dashboard and /claims templates control this response mode and can post canonical responses as embeds or normal messages. Approval removes temporary prompts, reminders, completion notices, and the obsolete action message while keeping the submitted forms.

Approval and staff actions

Automatic approval

Claims-bot approves once the configured participant templates or acceptance step are complete, both users still satisfy required roles, and neither user exceeds the server’s dynamics limits. Servers may optionally require the claimant template first; the claimed partner’s template or Accept button remains disabled until the claimant finishes.

An optional claimant cooldown limits how often the same person can open a valid claim. Invalid posts do not start a cooldown, and Discord shows the claimant when they may try again.

Manual approval

When the thread says the claim is ready for staff approval, authorized staff can use /claims approve with the original claim message ID or add the configured approval emoji to that message. Staff can decline with /claims decline or the configured declined emoji.

The approval announcement includes the approving staff member. A staff reaction is not duplicated by the bot.

Dynamics and role safety

Claimant and claimed-partner limits default to one. Setting either limit to zero makes that side unlimited. A member cannot bypass limits by alternating between the claimant and claimed positions; when they participate on both sides, the stricter applicable limit governs their combined active dynamics.

When participant ending is enabled, either participant can use /claims end [partner] or add the configured ended-dynamic emoji to the original claim. The command remains available when channel permissions prevent members from adding reactions.

Servers can optionally end active dynamics and cancel incomplete claims when a member leaves or is removed. Configure a grace period to allow accidental departures or quick rejoins with /claims dynamics member-leaving enabled:true cancel_pending:true grace:30m. The bot records the reason in each claim thread and safely removes remaining bot-managed roles.

Claims-bot removes a completion role only when it originally introduced that role and no other active dynamic still needs it. If staff remove a bot-managed completion role, affected dynamics end after a short recheck instead of the bot forcing the role back onto the member.

Staff may end one dynamic by message ID, end every dynamic involving a member, or use the ended-dynamic reaction on the original claim. Deleting the original approved claim also ends its dynamic.

Servers can assign an acknowledged-dynamics directory from the dashboard or with /claims directory. Current-only mode lists active dynamics. History mode retains ended dynamics and their dates. Its title, introduction, sorting, sections, date style, participant labels, and claim-thread links are customizable.

Lifecycle controls can send deadline reminders and periodically ask both participants to reaffirm an active dynamic. Staff may also configure an audit channel, reusable decline reasons, and JSON settings backups from the dashboard and slash commands.

Command reference

Everyone can see /claims, but configuration and staff actions are privately restricted to members with Manage Server or a configured Claims-bot administrator role.

Troubleshooting