Quotas and usage

Plans

Admins manage token quotas in Quota management. There are three editable built-in plans, and you can add plans or set a quota for one person. SoduWork has no purchasing, billing or automatic renewal.

Plan	Starting monthly total
Trial	100,000 tokens for 7 days, granted once at sign-up
Standard	1,000,000 tokens
Professional	5,000,000 tokens

These are editable templates. Changing them doesn't change existing users automatically.

• Trial. A new email sign-up or first enterprise SSO sign-in receives a one-time trial. It starts at sign-up and doesn't renew with a new month, a new device, a reinstall or a re-sign-in. Changing the trial settings affects only future sign-ups.
• Monthly plans count by calendar month in Beijing time. All of a person's devices share one quota.
• Model limits. A plan can set a total, per-model limits and "only these models". The total and the model limits apply together; when one model runs out, other allowed models with quota left still work.
• null means no limit on the total; 0 pauses new AI requests.
• Changing or switching a plan doesn't reset usage already counted. A personal quota replaces the plan completely.

When a quota runs out, the person stays signed in, keeps business connections and can still browse history and the plugin catalog. The client explains the quota state, expiry and how to recover near the message box.

Usage

Usage and cost in the admin console reports tokens, requests, time and cost by person, organization, device, harness (runtime), provider and model.

• Each day's usage is recorded with who, which harness and which model it belonged to at that time. Reports never reinterpret history by the latest model.
• Cached input is counted once; reasoning output isn't added twice.
• Cost is recorded in US dollars to 0.000001. Without a trusted price, cost shows as "to reconcile", never as zero. Reports don't convert currencies.
• Monthly quotas use each day's usage within the month, not the month a chat started in.
• The client uploads usage in order and removes a record only after the Hub confirms it. Offline usage keeps its original date.

Session counts are distinct sources. A chat that spans days or models can appear in several groups, so don't add group session counts to get a total.

harness harnesses runtime runtimes 底座