Guide
Platform admin
The console RoodtSquared support staff use to run the service. No customer has access to it at any workspace role. It is documented here because “what can support see?” is a fair question and deserves a straight answer.
Who can reach it
Access depends on a platform role held against the account itself, entirely separate from workspace roles. Being an admin of your workspace grants none of it, and there is no setting anywhere that turns it on — the flag is set by a database operation performed by RoodtSquared.
Two separate ideas that share a word
What the console contains
| Screen | Purpose |
|---|---|
Generation runs | Every run across every tenant, with status, timing and failure reason. This is how a support engineer investigates “it didn’t work” without asking you to reproduce it. |
User lookup | Find an account and see which workspaces it belongs to and in what role. Answers “I can’t get in” and “who has access to this?”. |
Credit pricing | The price list: what each metered action costs, globally and per tenant. Where an agreed rate is applied. |
Credit management | Grant credits, review batches, and read the ledger of what was spent on what. |
Default plan | What a new workspace starts on. |
Text-tool logs | Use of the standalone humanise and detect tools, for support and abuse investigation. |
Platform health | Whether the service and its dependencies are behaving. Answers “is it us or is it you?” before anyone starts guessing. |
Demo codes | Codes that let a prospect try a generated piece before signing up. |
What support can and cannot see
The console is built for operating the service, not for reading your work. Support can see that a run happened, who triggered it, how long it took and why it failed — the operational record. Browsing a workspace's library is not a feature of this console.
Secrets are never visible. A destination's credential cannot be read back by anyone, including RoodtSquared, and failure messages are stripped of credentials before they are stored. If you need a secret rotated, you set a new one — nobody can tell you what the old one was.
For the formal account of what data is processed and who it is shared with, see the privacy policy. That page, not this one, is the authoritative statement.
Asking support to look
When you report a problem, the useful details are the workspace, roughly when it happened, and what you expected instead. That is enough to find the run. You do not need to reproduce it — the record is already there.
Consequential changes made inside your workspace are recorded in your own audit log, which your managers and admins can read at any time without asking anyone.