Skip to content
Qreate

Browse documentation

Search documentation

Suggested guides

Qreate Pro

Operational overview across multiple servers, health signals, configuration history, and access policies.

On this page

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 show what was last confirmed, not a live guarantee. Health signals say when they were last checked.

  • Bot presence: Shown from the last time Qreate confirmed the bot in the server.
  • Module status: Shows which modules are currently switched on for each server.
  • Activity metrics: Summed per day (UTC).

Security and permission scoping

Access control in Pro is strictly bounded to the authenticated user's verified permissions on each guild:

  • Scoped to you: Pro shows only the servers where your own Discord permissions allow it.
  • Secrets hidden: Module views hide webhooks, tokens and passwords.
Client accounts and cross-server template synchronization are scheduled for future phases. Each server in your Pro portfolio continues to map directly to your primary verified Discord management connections.

Next steps