๐Ÿ›ก๏ธ

When a server service is restricted

What a Qreate service restriction changes, what remains available, and how a server administrator can ask for review.

Qreate may temporarily restrict one feature or pause its service for a server after a specific acceptable-use, safety, security, legal, provider, or service-integrity concern. The restriction card in your dashboard names the affected service, the public reason category, and the end time when one is set.

A restriction can be narrow

A restriction may cover one module, image generation, or Q Assistant and connected MCP clients. Other Qreate features keep working unless the dashboard says the whole service is suspended.

What a full suspension changes

  • The bot may remain installed in Discord, but Qreate commands and enabled modules stop executing for that server.
  • Automations, scheduled work, publishing, Q Assistant changes, MCP changes, and configuration writes stop.
  • Read-only dashboard access, privacy tools, support, and the minimum records needed for review remain available.
Note. Bot presence and service status are separate. Seeing Qreate in the Discord member list does not mean the service is active.

A user and a server are separate decisions

Restricting a Discord user does not automatically suspend a server they own. A server restriction can also apply when its owner has never created a Qreate web account, because the service decision belongs to the Discord server.

Ask for review

Use Qreate support from an account that administers the affected server. Include the server ID and explain why the restriction should be changed or lifted. Review is available without a paid plan.

The dashboard shows the information intended for the server administrator. Staff investigation notes and reports are kept internal so that reporters, evidence, and security controls are not exposed.

Next๐Ÿ” When support opens your dashboard