View Plan Usage and History
Understand the job and member capacity shown in Settings, what counts toward each limit, and when usage resets.
Understand the job and member capacity shown in Settings, what counts toward each limit, and when usage resets.
The Usage page shows how much job and member capacity your company is using under its current plan. It also explains what counts toward a limit and, when available, shows recent monthly job usage.
Usage is separate from AI Usage. The Usage page covers jobs and members; AI Usage covers the company's monthly AI allotment and rolling 7-day throttle.
| Plan | Jobs created per UTC month | Active and pending users | Included AI credits per UTC month |
|---|---|---|---|
| Starter | 30 | 1 | 500 |
| Team | 100 | 10 | 1,500 |
| Business | 300 | 25 | 5,000 |
| Enterprise | Unlimited | Unlimited | 5,000 by default |
The Business trial uses the Business job, member, product, and AI limits.
If your role or subscription state does not allow access, JobsiteOn shows an access explanation instead of estimated or stale usage.
For plans with a monthly job limit, the main job card shows:
If the active plan has unlimited job creation, the page says Unlimited Jobs and does not show a monthly cap.
Job usage resets at the start of each UTC calendar month. This is the same for monthly and annual subscriptions. Paying annually changes when Stripe charges the company, not how often job capacity resets.
Creating a job counts as one job against the current cycle. These actions do not consume another job:
Deleting a job does not restore the job slot that was used when it was created. Unused job capacity does not roll into the next cycle.
The Active Users section counts:
Pending invitations count because accepting one would activate another member. Deactivated members do not count toward the active-member limit.
Pending seats are counted by normalized email address. An unexpired pending invite does not add another seat when that email already belongs to an active member, and repeated pending rows for the same email count once. Expired, accepted, canceled, and revoked invites do not reserve a seat.
For a plan with a member cap, the page shows the limit, active count, pending count, remaining slots, and utilization. An unlimited plan says Unlimited Users instead.
Usage History shows up to the six most recent billing cycles when the company has a limited monthly job allowance and is not in an active trial. Each row shows:
The newest row is marked Current. Open the dedicated Usage History link at
/settings/usage/history to go directly to the same history section.
If there are no completed or current cycle records to display, the table says No usage history yet. An active trial or unlimited job plan can omit the history table because the monthly limited-plan comparison does not apply.
The Usage page can show guidance when capacity is running low, a limit has been reached, or billing needs attention. Follow the action shown on the page:
Plan availability and included capacity come from the current billing catalog, so use the values displayed in your company rather than relying on an older screenshot or saved number.
Limit checks happen in the same database transaction as job creation or invite acceptance. If two requests compete for the final slot, only one can use it. Retrying the same request does not consume the slot twice.
Refresh the Usage page. If the count still does not update, confirm the job was created in the same company and environment, then contact support with the job number and approximate creation time.
Check for pending invitations. Active members and pending invitations both count toward a limited plan's member capacity.
The history table is not shown during an active trial or when the plan has unlimited job creation. It can also be empty until usage-cycle records exist.
Did this answer your question?