Operations & data
Operations & Health covers service health and retention. Data Export and Data Purge are separate delegated permissions so a staff member can troubleshoot the community without automatically receiving access to download or permanently delete its records.
Server health
The Operations page combines the latest bot heartbeat and guild-health scan so you can see whether the bot is online, permissions are healthy and role hierarchy is valid. A stale heartbeat usually points to the bot hosting process, token or database connection rather than the website dashboard itself.
Retention policies
Ticket, application and transcript retention can be configured independently. Retention settings allow you to keep operational history for the period that matches your community's needs instead of accumulating records forever.
Normal retention cleanup avoids deleting open/active records. If you need history for moderation, legal or internal policy reasons, choose a period that reflects those requirements before reducing retention.
Data export
Data Export must be granted explicitly. It is not automatically included with Operations & Health. Exports are generated only for the selected licensed server and include community product data; owner-only billing/licensing audit events remain redacted for delegated non-billing users.
Data purge
Data Purge is a separate high-risk permission. It is never implied by Operations & Health or Data Export. Purge removes operational records while preserving the account/subscription/license relationship and selected platform configuration, and the dashboard still requires a typed server-name confirmation.
Export the server's data first and confirm you are viewing the correct active server. Purge is not the same as closing tickets or archiving applications and should not be part of a normal staff workflow.
Audit Log
Use the Audit Log to investigate community configuration and operational actions. Delegated Audit users do not receive subscription, Stripe, payment, server-license or White Label ownership events; those remain visible only to the subscription owner.
Service status
The public Status page reports high-level service health for the Discord bot, website/API, database and billing integration. Global bot totals include both official Premium connections and active White Label bot connections instead of counting only the official bot process. It also shows a rolling monitoring history plus the live number of Discord servers and combined members currently connected to Submitt. Historical grey bars mean no stored sample exists for that day; they are not treated as downtime.
The authenticated Operations area remains the source for server-specific permission, role hierarchy and setup diagnostics. If the public website is healthy but your guild heartbeat is stale, focus troubleshooting on the bot host and its database/Discord connectivity.
Recommended operational checks
Review Operations after installing the bot, after changing Discord permissions/roles, after moving hosting, and any time ticket/application actions suddenly stop working. Also review retention before your community begins generating large volumes of transcripts or applications.