Usage and tokens
Select a workspace and open Usage to see its token balance, billing period, and total occupied storage. The table below the tiles lists each action and its Tokens used, including zero-token entries. Actions are ordered by tokens used, highest first, with alphabetical ordering for equal amounts. Sorting uses precise amounts before display rounding. The Tokens and Storage tiles show used and available amounts with a quota bar. Displayed token amounts are rounded down to whole tokens; accounting and quota bars retain fractional precision.
Monthly allowance
Each plan includes tokens. Personal Free renews monthly from its initial period date. Paid plans renew with their verified paid billing period. Business Trial receives one allowance for its single month. Unused tokens expire; they do not roll over or transfer between workspaces.
| Plan | Monthly price (USD, excluding taxes) | Included tokens | Storage |
|---|---|---|---|
| Personal Free | $0 | 1,000 per month | 1 GB |
| Personal Pro | $20 | 50,000 per month | 10 GB |
| Business Trial | $0 for one month only | 10,000 once | 1 GB |
| Business Pro | $100 | 300,000 per month | 100 GB |
What uses tokens
Token rates are:
| Action | Tokens |
|---|---|
| Upload | 1 per MB |
| View or download a file | 2 per MB |
| Workflow email | 5 per recipient |
| Submit or resubmit a request | 10 |
| Create a task | 2 per task |
Reading request and task details or lists, completing tasks, and cancelling requests are not metered and do not consume tokens. Submission and resubmission use the same rate.
Transfers use decimal MB (1,000,000 bytes). Small files consume fractional tokens, rather than rounding up each file to one MB. File previews also transfer data. Viewing a copy already cached by your browser does not cause another server transfer. Successful file transfers are charged for document bytes, without the data-URL encoding overhead.
Requests and tasks are charged to the originating workflow workspace, even when an approver uses a personal inbox. Uploads from task and discussion pages belong to the request's workspace, which pays for their upload, storage, and downloads. Uploads made while preparing a new request belong to the selected workspace. Account verification, password resets, security notices, billing emails, and public branding assets do not consume workspace tokens.
Example workflow
A workflow with 10 MB uploaded, 10 MB viewed or downloaded, five workflow email recipient deliveries, one request submitted, and five tasks created uses 75 tokens:
| Activity | Calculation | Tokens used |
|---|---|---|
| Upload 10 MB | 10 × 1 | 10 |
| View or download 10 MB | 10 × 2 | 20 |
| Deliver five workflow emails to one recipient each | 5 × 5 | 25 |
| Submit one request | 1 × 10 | 10 |
| Create five tasks | 5 × 2 | 10 |
| Total | 75 |
Completing those tasks does not itself consume tokens. Further file transfers, emails, resubmissions, or tasks created by later workflow steps are charged separately at the rates above.
Charging and insufficient tokens
Uploads, downloads, and workflow emails check available tokens before starting and charge completed work directly. Failed uploads and unsent emails are not charged. Interrupted downloads are charged for document bytes transferred. Attaching or deleting an uploaded file does not refund its upload charge.
Simultaneous actions can take the balance below zero; further charged actions are blocked until tokens are available.
Burst and concurrency limits also protect the service. A temporarily rate-limited action can be retried later.
When tokens are insufficient, new charged actions are blocked. Existing request and task records remain accessible; file viewing still requires tokens. Completing a task may create tasks for the next step, which requires tokens at the task creation rate. Open Plans to review your allowance. Deleting a record does not refund tokens already consumed.
Storage is a separate limit
Storage measures files currently occupying space, including scheduled files awaiting cleanup. It is not a new upload allowance each month. Keeping a file does not consume additional tokens, but counts against your plan's storage capacity until it is removed.
Choose retention around how long you need records. A scheduled plan change keeps the current paid entitlement until it becomes effective. A paid upgrade activates after verified payment; it does not grant tokens merely because Checkout was opened.