Skip to main content
Omnifact uses two controls to manage AI usage across your organization:
  1. Organization Usage Credits: A shared monthly credit pool for your entire team.
  2. Per-User Spending Limits: An optional monthly cap on how much a single user can spend from that shared pool each billing cycle.
This guide explains how both limits work, what you see in chat when a limit is reached, and how to keep working or request a higher limit.

Organization Usage Credits vs. Per-User Spending Limits


Part 1: Organization Usage Credits

What are AI usage credits?

Every organization subscription includes a shared monthly AI usage credit that your entire team draws from across Chat, Spaces, and the AI Gateway. On self-serve Pro subscriptions, each paid seat adds €5/month in shared AI usage credits (included in the €25/user monthly price, or €20/user/month billed annually). On invoiced Pro and Enterprise contracts, your organization receives the fixed monthly credit total agreed in your contract (ordering additional seats does not automatically change a contract’s monthly credit total unless you also increase credits).
  • No rollover: Unused credits expire at the end of each monthly billing cycle and do not carry over to the next month.
  • All tiers draw from the budget: Every AI model, including Base, Standard, and Premium tier models, draws from your shared monthly budget (and your per-user spending limit) while credits remain. Base-tier models are much more cost-effective per message, while Premium and reasoning models consume credits faster.

What happens when organization credits run out?

If your organization’s pooled credits reach zero before the end of the billing cycle, your team is automatically switched to Base-tier models for the remainder of the cycle so work is not interrupted:
  • Standard and Premium models appear grayed out in the model selector until credits reset (or an administrator adds more credits).
  • You can keep working in chat using any enabled Base-tier model (such as GPT-6 Luna, Claude Haiku 5.5, Gemini 3.5 Flash Lite, or Mistral Small 4), as well as any custom self-hosted endpoint models your organization has configured in Providers.
  • Administrators receive in-app banners and email notifications at 75% and 90% of monthly credit usage (Review Usage), an in-app pace-based forecast banner (Review Usage) whenever usage is projected to run out before the cycle ends, and an exhaustion banner (Billing & Usage) plus email once 100% of credits are used.
You will only see Base-tier fallback models for providers your organization has explicitly enabled in Models. If no Base-tier model is enabled, chat prompts your administrator to enable one.
AI Gateway: Unlike the Chat interface, the AI Gateway has no Base-tier fallback when organization credits run out: requests to platform-managed models (including Base-tier models) are blocked until credits reset or increase, while custom self-hosted provider models remain available.

Part 2: Per-User Spending Limits

How per-user spending limits work

To prevent one heavy user from draining the shared organization budget, your administrator can set a default monthly per-user spending limit for everyone in the organization and assign individual spending limits for specific team members.
Per-user only (no per-group limits): Spending limits are configured either as an organization-wide per-user default or on individual user accounts. Per-group spending limits are not currently supported.
  • Private Usage Tracking (Works Council Compliant): You can check your own daily spend, message count, and model breakdown at any time in Account Settings > Model Usage. By design, only you can see your usage page. Administrators never see per-person spend or usage history.
  • Turn-Start Enforcement: Spending limits are checked at the start of each chat turn. If you are in the middle of a response when your spend reaches the limit, the active response always finishes cleanly.

What happens when you reach your per-user spending limit?

When your chat spend in the current billing cycle reaches your monthly spending limit, a warning banner appears above the chat input and a limit card appears at the top of your Model Usage page.
Chat input showing the yellow warning banner when a user reaches their monthly AI spending limit, with a Request Limit Increase button.
What you can do next depends on your organization’s setting:
  1. If base models are not allowed (default): The banner states “You’ve reached your AI spending limit until . Ask an admin to raise it.” Sending new messages is paused until your limit resets or an administrator raises your limit.
  2. If base models are allowed after the limit: The banner states “You’ve reached your AI spending limit. Only base models are available until .” Standard and Premium models are grayed out in the model selector, and you can continue chatting with Base-tier models. Note that Base-tier usage after a per-user limit still draws from your organization’s shared monthly credit pool.

How to request a higher spending limit

If you need additional capacity before your monthly cycle resets, you can ask an administrator to raise your limit:
1

Click Request Limit Increase

Click Request Limit Increase in the banner above the chat input, or click Request a limit increase on your Model Usage page.
2

Provide a brief reason

Enter a short Reason explaining what you are working on and click Send request. Your administrators see your reason and current limit in Team Settings > Requests, never your usage history.
3

Wait for email confirmation

While your request is open, the chat banner notes “Your request is with an admin.” You will receive an email as soon as an administrator approves your request with a new monthly limit or declines it.

When do credits and spending limits reset?

Both your organization’s pooled credits and your per-user spending limit reset on the same schedule:
  • Automatically at the start of your organization’s next monthly billing cycle (unused credits do not roll over).
  • Immediately for organization credits on active invoiced contracts when an administrator places a credit increase order via Add More Credits in Billing & Usage (self-serve Stripe plans scale credits automatically when adding seats or can submit a request via Add More Credits).
  • Immediately for your per-user limit when an administrator approves your request in Requests or raises your limit in User Management.

Frequently Asked Questions

Yes. On the self-serve Pro plan (€25 per user per month billed monthly, or €20 billed annually), the €5 monthly AI usage credit per seat is included in the seat price. All seats pool their €5 allowances together into a single shared monthly budget for your organization (for example, 25 seats on a self-serve Pro plan provide €125/month in shared AI usage credits). Invoiced contract plans have a fixed monthly credit pool agreed in your contract.
No. Your organization’s monthly usage credit resets at the start of each monthly billing cycle, and any unused budget from the previous cycle does not carry over.
Base-tier models are not free while you have budget. They draw from your organization’s shared credit pool (and your per-user spending limit), just at a much lower rate than Standard or Premium models. However, if your organization’s shared monthly budget reaches zero, Base-tier models remain available as a fallback so your team can continue working until the next billing cycle.
If no per-user spending limit is set, any user can draw from the shared organization pool. To prevent a single heavy user from exhausting the team’s budget, administrators can configure a default Per-user spending limit in Team Settings > Plan & Billing (for example, €15 or €20 per user) and set higher individual limits for power users in User Management.
No. Spending limits are available at the organization level (total pooled credits) and per user (an organization-wide per-user default plus individual user overrides). Per-group spending limits are not supported, though you can control which groups have access to costlier Standard and Premium model tiers in Group Management.
Administrators receive in-app warning banners and email notifications at 75% and 90% of monthly credit usage (Review Usage), an in-app pace-based forecast banner whenever current consumption is projected to exhaust the pool before the cycle ends, and an exhaustion banner + email at 100%.
No, by design. To protect employee privacy and meet works council (Betriebsrat) requirements, administrators only see organization-wide credit totals on Billing & Usage and whether a user has reached their cap (Limit reached badge). Individual users can view their own personal spend and model breakdown privately under Account Settings > Model Usage.