Help
Frequently asked questions
Short answers for the issues administrators are most likely to encounter while operating Kyvera.Access and connection
Your Discord account needs Manage Server or Administrator permission. Sign out and back in after permission changes.
Kyvera is connected to Discord, but the dashboard control link is temporarily unavailable. Bot automations continue while live dashboard actions may be delayed.
The live Discord connection may be degraded, or Kyvera cannot view that resource. Check service status and bot permissions.
Use the official hosted dashboard and Discord slash commands. Infrastructure controls are not part of the user product.
Permissions and actions
The target may be an administrator, above Kyvera in the role hierarchy, or protected by missing Discord permissions.
Discord rejected role delivery, usually because the role is managed or above the Kyvera role.
The destination may have been deleted or Kyvera may lack View Channel or Send Messages there.
Check its Discord permission, Command Access policy, allowed roles, blocked channels, and role hierarchy.
Data and privacy
No. Message events are processed for configured bot features, but the dashboard does not provide general live-chat retrieval.
When a rule is triggered, the relevant message content and action context can be attached to that moderation case.
Server structure, roles, and supported permissions. They do not include message history or member accounts.
Use the dashboard Feedback Inbox or the /feedback command. Check System Status first for an active incident.
Check live platform availability before submitting a report.