1. What an administrator can do¶
Part 01
An Admin can do everything a User can do, plus everything in this guide. Read the companion document, QuantaCloud for Users, first — it describes the product your users actually live in, and most support questions are answered there rather than here.
1.1. The account roles¶
Role |
What it grants |
Who assigns it |
|---|---|---|
User |
Use the products granted to the account. No admin console. |
Any admin, on the Users page. |
Admin |
Everything a User has, plus the whole admin console: accounts, groups, entitlements, sign-in method, mail, storage, limits and monitoring. |
Any admin, on the Users page. |
Root |
A protected built-in account. Its role cannot be changed — the edit dialog says so: Root role cannot be changed. |
Nobody. It is fixed by the system. |
There is exactly one level of administrator. The console has no sub-roles: anyone with Admin sees and can change every page in it. Grant it sparingly and to as few people as the work allows.
The distinction that causes most confusion
The account role (User / Admin) is not the workspace role (Owner / Editor / Commenter / Viewer). They are independent. Being an Admin does not make you Owner of anybody’s workspace, and it does not by itself let you read their files — the workspace member list still governs that.
1.2. The two gates every user passes¶
Before anyone can use anything, two separate permissions must both be open. Almost every “I can’t get in” ticket is one of these:
The product must be enabled for the organisation
Set on the Entitlements page. If a product is disabled here, nobody gets it, whatever else you do.
The product must be granted to that user
Also on the Entitlements page, per user. A brand-new account has no product until you grant one, and will hit No entitled products are available for your account at sign-in.