Flow reference: Server Management
Lock/Unlock Channels
Stop (or allow again) @everyone sending messages in some channels, or in every text channel. Sets {lockdown.count}.
Stop (or allow again) @everyone sending messages in some channels, or in every text channel. Sets {lockdown.count}.
When and how to use it
Connect the input from the preceding step on the path that should perform this operation.
Fill the fields with data available in the trigger's context.
Connect the needed outputs; an unconnected path cannot run later blocks.
Configuration fields
Mode — mode
Choose the operating mode before other fields. Update versus create, acknowledgement mode and punishment mode have different consequences.
Input: Fixed choice.
Default:
lock.Available choices (preserve the exact value):
lock — Lock (no messages)unlock — Unlock (back to normal)Channels (one per line, blank = all text channels) — channels
Channels to change, one per line (mention, ID or name). Leave blank to change every text and announcement channel of the server.
Input: Multiline text.
Format example, not a ready value for your server:
#general.Default: ``.
Reason — reason
Describe why the action is taken. Use a meaningful audit/support explanation and avoid sensitive personal details.
Input: Text with variable suggestions.
Default: ``.
Outputs and next steps
out: Continue to the next step.Test and troubleshoot
Check caller permissions, bot permissions, channel overrides and role hierarchy separately. Test delete/ban/permission changes in a dedicated server rather than against production data.
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).