Skip to content

Channel type compatibility

Guild inventories retain unfamiliar direct channel types as opaque topology: exact ID, numeric type, position, parent, and obfuscation state. A new type does not invalidate the entire Gateway layout. Ordinary channel reads retain their bounded metadata projection, and channel-order audits identify unsupported groups by numeric type. Unknown types never inherit text-channel operations. Malformed topology, DM and thread entries in the direct inventory, hidden metadata required for a modeled check, and inconsistent Gateway/HTTP evidence still fail closed.

Ordering a supported family is available when unfamiliar channels are outside the affected parents. Direct operations on an unfamiliar type, or ordering through affected unsupported siblings, remain unavailable. Member-role changes, bulk changes, invite role grants, and role deletion retain mandatory authorization and modeled-risk checks while reporting unsupported channel semantics as partial analysis coverage. An unfamiliar type alone does not veto those role workflows.

GuildControl uses bot authentication only. Unavailable bot features never activate a browser, borrow a logged-in user session, or fall back to a user token. Unsupported-type errors are a product boundary, not a request for broader credentials or operator approval. Supporting another channel type requires a verified bot-accessible contract and explicit operation, permission-impact, dependency, privacy, and readback coverage.

Discord's Server Hub guide describes publishing, widgets, and separate Whiteboard role restrictions. Discord's web client identifies channel type 20 as GUILD_SPACE; the official stable and preview bot API specifications, checked on 2026-11-11, do not define its operation contract. Bot-authenticated read probes on that date returned HTTP 403, code 20001 (Bots cannot use this endpoint), from GET /guilds/{guildId}/space and GET /guilds/{guildId}/space/widgets/catalog, despite guild Administrator permission. Basic channel metadata remained readable. These observations do not establish a mutation or permission-dependency contract. This build retains type 20 as opaque topology, declines its direct administration, and discloses partial coverage in ordinary role workflows. The older guild Home Settings object is not a substitute for that contract.

Role plans expose impact.coverage; role-deletion readiness and plans expose dependencies.coverage. Coverage contains a complete or partial status, evaluated and total direct-channel counts, and canonical unsupported channel IDs, types, parents, and positions. These exact gaps participate in the keyed plan and shared bulk evidence. Signed confirmation displays partial coverage before execution without a separate bypass flag. permission.channelPermissionEscalationSubset is null when a complete-inventory escalation proof is unavailable; modeled-channel checks still run. Zero known deletion blockers never asserts absence of undiscoverable experimental references, and explicit overwrite role references on opaque channels remain blockers.

Canonical source: docs/reference.md

Documentation generated for guildctl@2.3.9. Canonical source and edit history remain in the public repository. GuildControl is an independent project and is not affiliated with or endorsed by Discord Inc. Discord is used only to identify the platform that GuildControl connects to.