Skip to content
Fork Docs
Guide v1

/servermanager

Open a draft for changing channels, roles and server structure.

Availability

Section titled “Availability”

Public source-edition command; execution remains conditional on installation, server policy and the running service. This reference is built from the repository, not a live Discord registration probe. Explicit registration contexts: server.

Syntax

Section titled “Syntax”
/servermanager [request:String]

Angle brackets indicate required input; square brackets indicate optional input. In Discord, choose the command and fill its named options, rather than typing the brackets.

Parameters

Section titled “Parameters”
Name Type Required Allowed values / bounds Default when omitted Description
request String No Max length 4000 Open the existing draft. What should change? Omit to open the current draft. (English rendering of the registered description.)

Permissions

Section titled “Permissions”

Required native member permission(s): Administrator (Administrator normally satisfies native permission checks).

Fork role access is evaluated using the underlying servermanager policy key, even when the slash name is grouped. Native Discord permission checks remain separate from Fork role grants. Sensitive commands fail closed before valid setup; native Administrator bypasses Fork’s role matrix, not Discord’s bot permissions or target hierarchy. See Permission model.

Examples

Section titled “Examples”
Slash options
/servermanager request:Create a private text and voice space for moderators
Prefix equivalent and aliases
Default prefix
f!servermanager Create a private text and voice space for moderators

Default prefix: f!; installations can configure another. No extra handler aliases.

Grouped prefix routes also delegate to the original handlers, but aliases retain that handler’s argument parsing. Conflicting aliases are rejected as ambiguous. Prefix replies are generally visible in the channel; prefer slash privacy controls for sensitive personal data.

Expected result

Section titled “Expected result”

A request creates or refines a plan. The exact draft needs explicit approval and fresh authorization before Discord writes.

Failure cases

Section titled “Failure cases”

Stale approval, lost Administrator access, hierarchy conflicts, missing bot permissions or partial Discord failure can stop application. Check the returned error, current bot status and the relevant server permissions. A timeout or uncertain receipt is not proof that nothing happened; inspect state before repeating a mutation.

Usage limits

Section titled “Usage limits”

No fixed command-specific cooldown is declared in this reviewed entry. Discord rate limits, provider budgets, service admission and server policy can still apply; this is not an unlimited-usage promise.

Section titled “Related commands”
Section titled “Related guides”

Source edition v1 · Registration, direct handler and shared authorization review are hash-bound in the local documentation validation. This is not a production feature-availability certification.