Operations & data
Operations contains the controls owners should use for service health, retention, data portability and destructive cleanup. These tools are intentionally separated from everyday ticket/application management because they can affect large amounts of historical data.
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
Authorized owners can export server data as JSON. Exports are useful before moving a server slot, making major configuration changes or performing destructive cleanup. The export is generated for the selected licensed server, not for every customer on the Submitt platform.
Data purge
Purge is a deliberately destructive operation. It removes operational records while preserving the account/subscription/license relationship and selected platform configuration. The dashboard requires a typed server-name confirmation to reduce accidental deletion.
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 configuration changes, server-linking events, branding updates, data exports/purges and other important administrative actions. Search by action and filter by server when multiple communities share the same Submitt account.
Service status
The public Status page reports high-level service health for the Discord bot, website/API, database and billing integration. 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.