Discord Apps and reaction shortcuts
Use all 17 stable right-click actions, two configured reaction shortcuts, and the capture marker ModFlow adds after success.
- Audience
- moderator · senior reviewer · team lead
- Availability
- free · premium preview · feature flagged · private beta access
- Maturity
- alpha · partial
Last reviewed
On this page
Start from the visible member or message
Discord calls right-click commands Apps. They are useful when the member or source message is already in front of you: open Apps, choose the action, then review the confirmation or destination before continuing.
Right-click a member or message and open Apps to see commands registered for your account. For reactions, use only the symbols configured and announced by the server's supported setup result.
Every stable Discord App and reaction behavior
| Discord App | Use it when | Example | What happens next |
|---|---|---|---|
| History | You need the member's moderation profile before acting. | Right-click @Maya → Apps → History | Opens the server's profile and visible incident history. |
| Open Case Profile | You want case context for the member. | Right-click @Maya → Apps → Open Case Profile | Opens the member-focused case view you may access. |
| Jail | The member needs the configured private jail flow. | Right-click @Maya → Apps → Jail | Opens the jail confirmation and reason flow. |
| Mute | The member needs a temporary timeout. | Right-click @Maya → Apps → Mute | Opens the duration, reason, and confirmation flow. |
| Extend Mute | An active mute needs more time. | Right-click @Maya → Apps → Extend Mute | Opens the active-mute adjustment flow. |
| Warn | A formal warning is the lightest action that fits. | Right-click @Maya → Apps → Warn | Opens the reason and confirmation flow. |
| Start Ban Review | A proposed ban needs senior review instead of immediate action. | Right-click @Maya → Apps → Start Ban Review | Creates or opens a review packet; it does not ban the member. |
| Discord App | Use it when | Example | What happens next |
|---|---|---|---|
| Jail Author | The message author needs the configured jail flow. | Right-click the message → Apps → Jail Author | Opens a jail confirmation tied to that author. |
| Mute Author | The message author needs a temporary timeout. | Right-click the message → Apps → Mute Author | Opens a mute confirmation tied to that author. |
| Warn Author | The message supports a formal warning. | Right-click the message → Apps → Warn Author | Opens a warning confirmation tied to that author. |
| Create Case From Message | The source should begin a new case. | Right-click the report → Apps → Create Case From Message | Creates a case while preserving the source message identity. |
| Add to Active Case | You have an active case and this message belongs in it. | Right-click the message → Apps → Add to Active Case | Adds a permission-aware source reference to the selected case. |
| Add Message to Active Case | You want the explicit message-focused alias for the same handoff. | Right-click the message → Apps → Add Message to Active Case | Adds the source message to the selected active case. |
| Capture Conversation Window | Nearby messages are needed to understand the source. | Right-click the key message → Apps → Capture Conversation Window | Captures a supported context window without granting wider channel access. |
| Open Around This | You need to inspect nearby context before saving anything. | Right-click the message → Apps → Open Around This | Opens the supported around-this view if the source is still visible. |
| Save as Evidence | The message should become evidence for an authorized review. | Right-click the message → Apps → Save as Evidence | Starts the evidence destination and visibility flow. |
| Add to Evidence | You are already working in an evidence flow. | Right-click the message → Apps → Add to Evidence | Adds a source-aware evidence reference after confirmation. |
| Reaction | Configured meaning | Example | What to check |
|---|---|---|---|
| 📌 | Capture the message as evidence. | React 📌 to the source message after confirming it belongs in the current review. | Open the resulting evidence record and confirm its source. |
| 📎 | Show that ModFlow captured the message. | ModFlow adds 📎 after a supported capture succeeds. | This is not a capture shortcut. Use 📌 to capture; interacting with 📎 only hides the marker. |
| ⛔ | Run the server's configured delete-and-log action. | Use ⛔ only when the server has announced and verified that shortcut. | Confirm the deletion and the destination log; never infer behavior from the emoji alone. |
Preserve source context through the handoff
Verify the source
Confirm server, channel, member/message, timestamp, and whether the source is still visible.
Check: The action begins from the intended source identity.
Choose the current menu or configured reaction
Use Apps for registered context menus or a verified server reaction shortcut.
Check: The interaction maps to an implemented handler.
Review the private response
Read permission, case-selection, evidence, or action confirmation details before continuing.
Check: Restricted context does not leak into a public reply.
Verify the destination
Open the resulting case, evidence item, record, marker, or flagged-message log and compare the source identity.
Check: The handoff remains traceable and permission-aware.
The App or action shortcut links the correct member or message to an authorized moderation flow, while the marker shows a completed capture or explains why access, configuration, or source state prevented it.
Find and verify Discord Apps
Choose the source type
Right-click the member for a User App or the exact message for a Message App.
Check: Discord opens the correct Apps menu.
Read the current list
Use Apps and select only a documented, currently visible action.
Check: Feature-flagged or permission-hidden entries are not guessed.
Verify target/source
Read the selected member or message author/channel/timestamp in the response.
Check: The workflow is tied to the intended source.
Complete confirmation
Enter reason, duration, Case destination, evidence visibility, or review detail as requested.
Check: A write is not triggered from an ambiguous source.
Open the result
Verify the action, Case, evidence item, or context view.
Check: The source identity and destination agree.
Detailed User App boundaries
| App | Starts | Does not |
|---|---|---|
| History | Member profile/history in the selected server. | Grant cross-server history or hidden evidence. |
| Open Case Profile | Member-focused Case/profile context. | Create a Case or expose every Case. |
| Jail | Reason/duration confirmation for the selected member. | Bypass role hierarchy or setup. |
| Mute | Duration/reason confirmation. | Apply until the human confirms. |
| Extend Mute | Adjustment flow for an active mute. | Prove an active mute exists or permit contradictory fields. |
| Warn | Formal warning confirmation. | Mute or jail the member. |
| Start Ban Review | A proposed-ban review packet. | Ban the member or approve the request. |
Detailed Message App boundaries
| App | Use | Expected result |
|---|---|---|
| Jail Author | The visible message supports a jail decision. | Jail confirmation for the message author; source remains context. |
| Mute Author | The message supports a timeout decision. | Mute confirmation for the author. |
| Warn Author | A warning is the proportional response. | Warning confirmation for the author. |
| Create Case From Message | The source should begin a new investigation. | New Case with source identity/context reference. |
| Add to Active Case | The source belongs to an already selected Case. | Permission-aware evidence/reference handoff. |
| Add Message to Active Case | Explicit message-focused alias for the same Case handoff. | Source message added to the selected active Case. |
| Capture Conversation Window | Nearby messages are needed to understand the source. | Nearby context is captured without granting broader channel access. |
| Open Around This | Review nearby context before preserving it. | Permission-aware around-this view when source remains visible. |
| Save as Evidence | Preserve the source in an authorized evidence workflow. | Case/destination and visibility flow. |
| Add to Evidence | Continue an existing evidence flow. | Source-aware evidence reference after confirmation. |
Use configured reaction actions
| Reaction | Who adds it | Meaning | Verify |
|---|---|---|---|
| 📌 capture action | Authorized staff | Requests supported evidence capture for the source message. | A resulting Case/evidence record and source identity. |
| 📎 capture marker | ModFlow after supported success | Indicates the capture workflow completed; it is not the capture trigger. | The evidence record, not the marker alone. |
| ⛔ configured delete/log | Authorized staff where setup announced it | Requests the server’s configured delete-and-log behavior. | Message deletion and correct staff log destination. |
- Use only symbols confirmed by the current server setup response.
- Do not infer an action from a familiar emoji used casually by members.
- Confirm the reaction was added to the intended source message.
- Check the destination record/log before repeating a reaction.
- Treat deleted or inaccessible source content as unavailable even when a marker remains.
Recover a stale or inaccessible source
The source message cannot be opened or captured
What you see: The App exists, but the message is deleted, channel access changed, or the source check fails.
What may be happening: Discord source visibility is rechecked and a Case reference never grants hidden-channel access.
What to do
- Confirm the selected server/channel and your current channel access.
- Use the available provenance fields without copying an unauthorized private cache.
- Request replacement evidence from an authorized source when appropriate.
- Record the source as unavailable or partial in the Case.
The wrong active Case was selected
What you see: The source was attached to an unintended Case.
What may be happening: A stale active-case selection or similarly numbered Case caused the handoff.
What to do
- Open both Cases and verify server, Case ID/number, subject, and evidence item.
- Remove/move the evidence only through an authorized supported control.
- Record the correction if the wrong attachment affected review.
- Reattach once to the intended Case with the correct visibility.
Recover a missing menu or shortcut
Discord can hide context commands the account cannot use. Deleted messages, inaccessible channels, stale case selections, and unconfigured reactions can prevent capture; a marker does not guarantee the full artifact remains available.
The Discord surface is missing or did not complete
What you see: A command, menu, reaction, queue, or panel is unavailable, denied, stale, or uncertain.
What may be happening: Registration, server feature access, Discord permission, ModFlow team permission, source visibility, or interaction state may not support it.
What to do
- Confirm the command is present under Apps for the current account.
- Open the source directly and verify channel access.
- Use the resulting case/evidence record rather than repeating the interaction.
- Ask a server administrator to verify reaction destinations and setup.