QREATE Pro
Operational overview across multiple servers, health signals, configuration history, and access policies.
QREATE Pro is the multi-server management surface at /pro. It gives community managers and studio leads portfolio-level visibility across every server they manage, with centralized health signals, activity feeds, configuration snapshots, and permission policies.
Multi-server overview
The Pro servers screen lists every Discord guild connected to your account. Each server card provides high-level indicators including member count, active feature modules, automation counts, and a composite health status.
- Healthy: Bot is connected, operational modules are configured, and recent runtime error rates are zero.
- Warning: Server has zero active modules configured, or recent telemetry errors have been detected.
- Critical: Bot is disconnected from the guild and requires an invite to restore management.
Data provenance and accuracy
Pro views distinguish clearly between live checks and persisted database records. Health signals report data sourced from synchronized database timestamps rather than claiming live Discord gateway connection without active REST confirmation.
- Bot presence: Read from the latest recorded database sync timestamp (
botJoinedAt). - Module status: Derived dynamically from the shared 33-module catalog, reflecting currently enabled module configurations.
- Activity metrics: Aggregated into UTC daily rollups by background synchronization.
Security and permission scoping
Access control in Pro is strictly bounded to the authenticated user's verified permissions on each guild:
- Connection scoping: Single-server permission queries resolve against the caller's specific connection record, preventing exposure of unrelated server roles.
- Safe permission fallbacks: When connection records are unset, permissions fall back safely to manager rather than granting administrator access.
- Config redaction: Module inspection views redact sensitive keys such as webhooks, tokens, passwords, and private credentials.
- Telemetry bounding: Event activity strings and metadata payloads are bounded to prevent denial-of-service and sanitized to mask sensitive endpoints.