Permissions & Safety

Cervantes follows a permission-conscious, guild-scoped design. This page explains the current design principles, not a claim that every planned workflow is available.

• Discord authority matters. Guild ownership, member permissions, bot permissions and role hierarchy constrain sensitive actions.
• Capabilities are scoped. Being allowed to perform one moderation task does not automatically grant broad administration access.
• Least privilege. A module should request only the permissions needed for its features. Module-specific permission tables will be published when those modules ship.
• Private responses when appropriate. Administrator workflows are designed to be initiated explicitly in Discord, rather than through unsolicited DMs or external OAuth gates.

An official install-time permission list will be added after the public installation flow has been reviewed against the running application.