The staff console
What the Cyrqle staff console is, who can open it, and the rules that apply to everything you do inside it.
This section is for Cyrqle staff. Customers do not see the admin console.
The staff console is the internal operations tool for Cyrqle. Support, data operations and superadmins use it to answer questions about any workspace, run licence and money procedures, tune the platform, and watch reliability.
The console lives at https://app.cyrqle.app/admin. It runs inside the same application customers use, on the same sign-in. There is no separate staff password and no separate staff account.
Before you start
- You need a Cyrqle account with a staff role. See Access and roles.
- You sign in the same way a customer does: email address, then a one-time code.
- Read this page before you open a customer's record. Every page you open is recorded.
How to recognise the console
The console is styled as the inverse of the customer app: a dark background, cream text and yellow accents. A stripe across the top reads internal · cyrqle ops and carries an exit admin link back to the customer app.
If the page you are looking at is light, you are in the customer app, not the console. Check the stripe before you act.
Steps
Open the console
Go to https://app.cyrqle.app/admin.
Sign in
Enter your email address, then the one-time code Cyrqle sends you.
Check the footer
The sidebar footer shows your name and your role label. Confirm the role is the one you expect.
Navigate
Use the sidebar, or press Cmd-K (Ctrl-K on Windows) to search creators, workspaces, users and campaigns.
Leave
Click exit admin when you finish. Sign out if you share the machine.
What the sidebar shows
The sidebar is filtered by your role. A page your role cannot open is not in your sidebar at all. Two people with different roles see two different consoles.
If a colleague describes a page you cannot find, your role is lower than theirs. Do not assume the page was removed.
Rules that apply to everything here
Opening a customer's page writes a record of who looked, when, from which address, and with which search terms. Treat every read as visible.
- Every change needs a reason. The reason box is not a formality. It is the record another operator reads next month.
- Reads are recorded too. "Who looked at this account" is an answerable question.
- Some procedures have no button. Payout retry, payout reversal, workspace suspension, workspace archiving, account deletion, password setting and overage settlement are not available in the console today. Raise them with engineering.
- Destructive actions need a fresh sign-in. See step-up re-authentication.
- Nothing here moves money on a schedule, with one exception. A licence that stays unpaid for 14 days is suspended automatically.
Pitfalls
- Demo workspaces force payouts and ad boosts onto the test path. A run inside a demo workspace proves nothing about live money.
- The console reads live production data across every tenant. There is no sandbox copy of it.
Reference
| Question | Page |
|---|---|
| How do I get access, and how is it removed? | Access and roles |
| What can my role do? | Access and roles |
| A customer says they cannot create a campaign | Licences |
| A creator was not paid | Money and payouts |
| A creator asked to be removed | Creator data operations |
| Search results look wrong | Search and embeddings |
| Something is down | Reliability |