Payout runs

Path: /payouts · access: payouts

Who can see the tab

The tab requires the payouts scope and host level 3 or higher.

Interface map

server → fields and filters → validation → action → result

Fields and actions

Fields come from the server schema and the payouts scope. Required fields have visible labels; role and channel IDs use Discord selectors, while numeric values enforce their minimum and maximum.

Saving and realtime

Editing a field marks the page as dirty. Select Save once and wait for completion. Do not close the page during the request. Realtime events refresh related lists; conflicting local edits must be reviewed again.

Interface states

A loading indicator is shown while data is fetched. An empty state explains what to create first. An error includes a cause and retry action. Success is communicated with text, not color alone.

Discord impact

Changes are applied to the selected server and synchronized with related Discord features.

Safe setup order

Configure roles and channels first, then feature toggles, and finally run one test action. Before a bulk operation, verify the selected server and filter. Record a reason for staffing, financial, and restriction actions.

Error recovery

Refresh page data, verify the server and scope, correct the invalid field, and retry. Do not repeat a 403 request; obtain the required access. Reopen a record after a realtime conflict.