For Providers¶
If you sell QVOICE Platform to other people, Desk Center is something you give an account — along with how much disk its files may use and how long it may keep them. All three live in one place in the admin portal, and none of them is visible to the account itself.
Configuration → Accounts → the account → Desk Center
The switch¶
Enabled gives the account Desk Center: the boards, the work items, the CRM and the tickets. It is off by default — this is a product being sold, not a surface every account already has.
Switched on, the account's administrators and agents find Desk Center in their sidebar on their next load. Nothing else needs doing: the account starts with a sample board so that nothing is empty on the first open.
You decide the entitlement, they decide who uses it
Giving an account Desk Center does not say which of their people may see which board. That is their administrator's decision, inside Desk Center — see Who Sees What.
Attachment Limit (MB)¶
How much the account's attachments may add up to. Attachments are stored on the cluster, so this is the disk you are handing out.
| What you type | What it means |
|---|---|
| a number | that many megabytes, and uploads are refused past it |
| 0 | this account may attach nothing at all |
| empty | follow the cluster's own limit, set in Desk Center's configuration file |
Empty and zero are not the same answer, and the field keeps them apart deliberately. An empty box hands the decision back to the deployment; a zero is a decision.
Above the field you also see what the account has already stored. It is the same number its own administrators see, shown here because your action is the different one: raise the limit, or decide not to.
- With a limit set, a bar and both figures — "400 MB of 1000 MB stored" — from the first byte, so you can judge the number you are about to type against it.
- With no limit and something stored, the figure without a denominator. The limit in force is then the cluster's own, which lives in Desk Center's configuration file; the portal does not read it and will not invent one.
- With nothing stored at all, it says so. An empty space would be indistinguishable from a screen that failed to load the counter.
What your own provider allows you¶
If your account was itself given a limit, you cannot hand out more than you were given. The field then states the maximum under it — "Maximum 15000 MB, inherited from this account's reseller" — and refuses a larger number before it is saved.
The ceiling is checked against the account's own provider, not against whoever is editing. A limit raised on a grandchild account is held to what that account's own provider has, which is what keeps the rule meaningful more than one level down.
Three cases have no ceiling, and they look the same on screen: a top-level account, a provider that was never given a limit of its own, and the rare case where that provider's record cannot be read. In all three the field is simply unbounded.
A ceiling is per account, not a pool
If you have 15 GB, each of your accounts may be given up to 15 GB — ten of them is 150 GB promised. The ceiling stops any one account from being given more than you have; it does not add up what you have given out. Watch the usage figures.
Retention (days)¶
The longest the account may keep attachments before they are deleted automatically.
| What you type | What it means |
|---|---|
| a number, 31 or more | files on work closed longer ago than that are deleted |
| empty | nothing is ever deleted automatically |
This is the opposite default from the limit above it, and on purpose: the worst case of a missing limit is a refused upload, and the worst case of a guessed retention is somebody's evidence gone.
The account's own administrator can choose to delete sooner, never later: the shorter of the two numbers is the one applied. If they have chosen nothing, your number is what runs — so a retention set here is not only a ceiling, it is the schedule until they set their own.
Below 31 days nothing is accepted, which is the same floor call recordings defend.
The deletion runs on its own, account by account, against when the work closed. It leaves the work items and the note saying a file was attached. Only the file goes, and it cannot be recovered.
Seeing which accounts are filling up¶
You do not have to open a modal per account to find out. On the Accounts list itself, the Desk Center circle in the Features column says how that account is doing:
| The circle | What it means |
|---|---|
| green | Desk Center is on, and either has room or has no limit set |
| amber | 80 % or more of its limit is used |
| red | the limit is reached — the account cannot attach anything else |
Hover it for the figures: "Desk Center — 86 % of 1000 MB". Clicking it opens the same modal described above, which is where you would raise the number.
On this list, green means enabled
It does not mean healthy. An account at 86 % is still enabled — the amber is saying something else about it, on the same circle.
The filter¶
Beside the name and status filters there is a Desk storage one:
| Option | What it finds |
|---|---|
| Any | everything (the default) |
| Over 80 % | the accounts the amber and red circles mark |
| Full | only the accounts that can no longer attach anything |
| No limit set | accounts with Desk Center and no limit of their own |
The last one is not an alarm. An account with no limit has no percentage — it follows the cluster's own number, which the portal deliberately does not read — so it can never be marked and can never appear under the first two. That option is the only way to find those accounts, and until you start setting limits it is where all of them are.
Accounts that do not have Desk Center at all never appear under any of these.
What this does not control¶
- Which boards, columns, fields or automations the account has. Those are theirs — see Initial Setup.
- Who in the account sees which board. Also theirs — see Who Sees What.
- The per-file limit, which is a fixed 20 MB everywhere.