Staff and support
Staff operations that exist in the current stack
The old page advertised custom forms, shifts, ticket commands and staff slash commands that are not in the deployed command registry. Those claims have been removed.
Implemented
Applications, moderation and operator controls
Application records
Nexus builds the operator application view from current Kingdom guild state rather than browser sample rows.
Learn moreReview notes
Operator-only application endpoints support adding reviewer notes to a real application record.
Learn moreFinal application decisions
The current Nexus API includes a permission-checked final review action for application decisions.
Learn moreDiscord moderation
The deployed /mod command supports timeout, untimeout, kick, ban and unban with Discord permission and hierarchy checks.
Learn moreOperator-only controls
Sensitive Nexus reads such as applications, identity, Vault, Studio layouts and audit records require operator access.
Learn moreAudit events
Nexus records audited results for privileged control-plane mutations, and /mod can write successful moderation actions to the configured moderation log channel.
Learn moreDeployed moderation command
These are the moderation subcommands registered by the current Discord runtime.
/mod timeout user:@member minutes:30 reason:"..."
/mod untimeout user:@member reason:"..."
/mod kick user:@member reason:"..."
/mod ban user:@member reason:"..."
/mod unban user_id:123456789012345678 reason:"..."Open the current Kingdom Core stack
Add the Discord application, preview the current /setup3 layout before applying it, and use the production Nexus for authenticated web operations.