🔐

When support opens your dashboard

How QREATE staff can look at your server's settings, what you have to agree to first, and how to see or undo anything they did.

Sometimes the fastest way to solve a ticket is for someone on our side to look at your dashboard the way you see it. That never happens quietly. Here is exactly how it works.

Nothing opens until you say yes

A support engineer has to ask, from an open ticket, and say why. You get the request in four places at once: a note in the ticket, a card at the top of your dashboard, a browser notification if you allowed those, and a direct message from the bot.

The request names the person, the server, and the reason. You choose one of three answers: allow them to view only, allow them to make changes, or decline. Choosing view only when they asked for changes is allowed, and it takes effect on our side, not just in what you see.

Note. If you do nothing, the request expires on its own and nothing opens. Declining is never held against a ticket.

A session is small and short

It covers one server, not your account and not your other servers.
It covers only the areas listed in the request, such as module settings or tickets.
It runs for a limited time and ends by itself. The clock starts when the engineer actually opens it.
Closing the ticket ends any session attached to it, immediately.
You can end it yourself at any moment from Account → Support access.

You can see everything they did

Open Account → Support access. Every session, past and present, is listed there with who it was, why, and how it ended. Each one opens into a journal: every page they viewed, and every change they made, with the old value and the new value side by side.

Tip. The journal is written whatever the session is doing. There is no mode that lets someone look at your server without leaving a record.

Anything changed can be put back

Before a support session changes a setting, QREATE saves what that setting was. Those backups are kept apart from your normal settings history and held for at least 30 days after the session ends, so a question that arrives a week later still has an answer.

Undo restores the state from before that session's first change to the module, not some point in the middle, so you never land somewhere you were never in.

What we can never do

Sign in as you. Staff stay signed in as themselves the whole time, which is why the journal can name a real person.
Answer a consent request on your behalf. Inside a support session, the Support access screen is closed to them.
Read your Discord account password or token. QREATE never has those.
Extend a session past the platform limit, or reopen a closed one. A new look needs a new request.

If access was taken without asking

A small number of senior accounts can open a dashboard without consent, for cases like a live outage or a security report. When that happens you are told afterwards, through the same four channels, and the session shows in your history like any other with consent recorded as not granted.