Plans, approvals, and verification

Review the proposed plan#

1. Confirm the exact server and affected roles, channels, or settings.
2. Read what will change and what permissions or access could be affected.
3. Check the observation is fresh enough for the present server state.
4. Review the available pre-change snapshot, rollback coverage, and execution limits.
5. Only approve a scope you understand and have authority to approve.

Approval is scoped#

Installing the bot or consenting to a read-only scan is not permission for privileged changes. A plan, approval, attempted operation, successful read-back, and rollback are different stages. Use only the operations explicitly enabled for your authorized server.

Check the outcome#

When an enabled operation finishes, inspect the reported outcome and read-back result. Confirm the intended effect in Discord with appropriate member roles. An attempted action or a simulated preview is not evidence that Discord changed.

If the result is uncertain#

Do not approve repeated operations to force a result. Keep the operation reference and error, check whether an action was applied, and use the approved recovery route or contact support. A permission error should trigger a scope review, not a blanket Administrator grant.