Command permissions and parameters
Caller access, required parameters, optional parameters, defaults, and Discord prerequisites for TiaraBot commands.
This page lists the authorization TiaraBot checks for the person running each command. Discord must also allow TiaraBot to view and send messages in the selected channels.
Permission labels
| Label | Requirement |
|---|---|
| Any Discord user | No TiaraBot monitor role or Discord management permission is required. |
| Self | The command can read your own record. Looking up another person requires a configured monitor role. |
| Monitor | You must hold one of the target server's TiaraBot monitor roles. A member with Manage Server is not automatically treated as a monitor unless they hold a role. |
| Monitor or Manage Server | You must hold a configured TiaraBot monitor role or have Discord's Manage Server permission in the target server. |
| Manage server | You must have Discord's Manage Server permission or Administrator in the target server. A TiaraBot monitor role alone is not enough. |
| Check-in filler | You must be one of the fillers recorded on that check-in prompt. |
| Original submitter | You must be the Discord account that sent the team submission. |
Monitor roles are registered with /server add monitor_role. Manage Server is called Manage Guild in some Discord API output.
Schedule, slots, teams, and status
| Command | Caller access | Required parameters | Optional parameters |
|---|---|---|---|
/schedule list | Self. Monitor when user is another person. | day | user, server_id |
/slot list | Any Discord user for ephemeral. Monitor for persistent. | day | server_id, message_type |
/slot button | Monitor. | day | server_id |
/team list | Self. Monitor when user is another person. | None | user, server_id |
/screenshot | Monitor. | channel_name, day | server_id |
/status | Any Discord user. | None | None |
/slot list defaults to an ephemeral response. Set message_type to persistent only when the result should remain in the channel. /screenshot returns an image of the configured schedule-sheet range. Its channel_name is the logical running-channel name stored in TiaraBot, not a Discord channel mention.
Check-in and room operations
| Command | Caller access | Required parameters | Optional parameters |
|---|---|---|---|
/checkin manual | Monitor. | None | channel_name, hour, server_id, template |
/checkin test_auto | Monitor. | None | server_id |
/room_order manual | Monitor. | None | channel_name, hour, heal, server_id |
/kick manual | Monitor. | None | hour, channel_name, server_id |
When channel_name is omitted, the manual check-in, room-order, and kick commands use the current Discord channel to resolve the running room. The optional template on /checkin manual is an advanced Handlebars message template. The optional heal value tells room order how many healer positions are needed.
For automatic-check-in servers, TiaraBot cleans each configured running channel’s lockdown role at minute 15. /kick manual is the fallback for ad-hoc cleanup and is useful only when the running channel has a configured lockdown role. TiaraBot rejects the command from minute 40 through minute 59 so fillers scheduled through minute 00 of the next hour are not removed early.
Personal DM preferences
| Command | Caller access | Required parameters | Optional parameters |
|---|---|---|---|
/preference checkin-dm status | Any Discord user. | None | platform |
/preference checkin-dm enable | Any Discord user. | None | platform, client_id |
/preference checkin-dm disable | Any Discord user. | None | platform |
/preference monitor-dm status | Any Discord user. | None | platform |
/preference monitor-dm enable | Any Discord user. | None | platform, client_id |
/preference monitor-dm disable | Any Discord user. | None | platform |
/preference dm client | Any Discord user. | client_id | platform |
platform currently supports discord and defaults to it. On either enable command, client_id defaults to the current TiaraBot client. Monitor DMs matter only when you are assigned as moni even though anyone can configure their own preference.
Event server settings
All /server commands require Manage Server or Administrator in the target server.
The same fields are available from a server's Dashboard → Settings → Server page with the same permission requirement.
| Command | Required parameters | Optional parameters |
|---|---|---|
/server list_config | None | server_id |
/server add monitor_role | role | server_id |
/server remove monitor_role | role | server_id |
/server set sheet | sheet_id | server_id |
/server set auto_checkin | auto_checkin | server_id |
/server set monitor_channel | channel | server_id |
/server unset monitor_channel | None | server_id |
auto_checkin is a required true or false choice. Turning it off does not prevent manual check-ins. Mana/moni can continue to use /checkin manual with server-chosen timing.
monitor_channel is the shared destination for automatic monitor summaries and handoff check-ins.
It cannot be a running channel. TiaraBot must be able to view and send messages in it. Unsetting it
restores the legacy automatic summary behavior; manual check-in is unaffected.
Running-channel settings
Channel configuration commands require Manage Server or Administrator in the target server. Lockdown setup and undo allow either a configured monitor role or Manage Server. The Dashboard → Settings → Channels page provides the same configuration and lockdown operations. Monitor-role users can select a channel and run lockdown actions there, but cannot view stored server or channel configuration.
| Command | Caller access | Required parameters | Optional parameters |
|---|---|---|---|
/channel list_config | Manage Server. | None | channel, server_id |
/channel set | Manage Server. | None | channel, running, name, role, checkin_channel, server_id |
/channel unset | Manage Server. | None | channel, running, name, role, checkin_channel, server_id |
/channel lockdown_setup | Monitor or Manage Server. | channel | None |
/channel lockdown_undo | Monitor or Manage Server. | channel | None |
channel defaults to the current Discord channel. On /channel unset, set each field flag to true when that stored value should be cleared. The optional role is the running-channel lockdown role, which /channel list_config labels Lockdown role. It is separate from the server-level TiaraBot monitor roles that authorize commands labeled Monitor in this reference. If it is not set, TiaraBot does not grant or remove lockdown roles and /kick manual is not needed.
The configuration commands store TiaraBot's channel mapping. If a lockdown role is configured, TiaraBot needs Manage Roles and its bot role must sit above that role.
/channel lockdown_setup replaces the selected channel's overwrites with the standard lockdown permissions: the Lockdown role can view, read, send, and use external emojis; configured monitor roles also receive Manage Channels and Pin Messages; and View Channel is denied for everyone else. /channel lockdown_undo removes all permission overwrites from the channel so its inherited permissions apply again. See Set up lockdown channel permissions before using either command.
The web Setup confirmation warns that every existing overwrite will be replaced. The Undo confirmation separately warns that every explicit channel overwrite will be removed so inherited permissions apply again.
Message controls
| Control | Caller access | Parameters | Notes |
|---|---|---|---|
| Check-in button | Check-in filler. | None | Records that filler and restores the configured lockdown role when the room uses one. |
| Open Slots button | Any eligible user. | None | Refreshes the slot list attached to the registered TiaraBot message. |
| Room-order Previous or Next | Monitor. | None | Changes the interactive draft. |
| Room-order Send or Pin tentative | Monitor. | None | Sends the selected order or pins the tentative order. TiaraBot needs Manage Messages to pin it. |
| Team Confirm or Reject | Original submitter. | None | Requires the configured channel and server feature flag. Unavailable after a terminal action. |
Team submission has one availability gate: the server feature flag must be enabled in addition to the monitored-channel mapping. Without it, TiaraBot does not dispatch, write, persist, react, or reply. Confirm, Reject, and rollback failure make a submission terminal; editing its source message afterward does not reopen it.
Parameter defaults and targeting another server
server_iddefaults to the current Discord server. Supply the server's Discord ID when running the command in a DM or when intentionally targeting another server.- Permissions are always checked against the targeted server. Supplying
server_iddoes not bypass its monitor-role or Manage Server requirement. dayis the schedule-sheet day number.houris the schedule hour TiaraBot should use. If it is omitted, TiaraBot resolves the applicable hour from the interaction time.userdefaults to the person running the command.- Commands that send or pin messages also depend on TiaraBot having the matching Discord channel permissions.
For the short operational lookup, return to the Quick command reference.