> ## Documentation Index > Fetch the complete documentation index at: https://docs.traversal.com/llms.txt > Use this file to discover all available pages before exploring further. # Usage limits > Set credit limits for investigations across your organization, members, and Workers. Traversal meters every investigation in credits. Usage limits cap how many investigations Traversal can run, separately for your people, your automation, and your [Traversal Workers](/using-traversal/workers). There are three kinds of control: * **Organization limits** — cap total usage by how an investigation starts. * **Member and Worker limits** — cap how much each member and each Worker can use. * **Usage alerts** — email your admins before a limit is reached. ## Finding the usage page Go to **Settings → Usage**. The page has three views: * **Organization** — usage against each organization-wide limit. * **Members** — usage and limits for each member. * **Workers** — daily and cycle usage for each Worker. > [!NOTE] > > Usage limits are available to organization admins. If you do not see the Usage page, > contact an administrator in your organization. If usage limits aren't enabled for your > organization yet, contact your Traversal representative. ## What Traversal meters Every new investigation is metered, and which limit it counts against depends on how it started. | Investigation source | Usage type | | - | - | | Traversal web app | Human-triggered | | `@mention` or DM in Slack or Teams | Human-triggered | | Alert or escalation | Auto-triggered | | Scheduled or automated trigger | Auto-triggered | | [Public API](/api/overview) or [MCP](/using-traversal/mcp), called with a user's credentials | Human-triggered | | Public API or MCP, called by a service account | Auto-triggered | | Investigation started by a Traversal Worker | Worker-triggered | Follow-ups to an existing investigation are not new investigations and are not metered again. Traversal also does not meter its own test traffic, or users your organization has excluded from analytics. ## Available limits | Limit | Applies to | What it does | | - | - | - | | **Human-triggered** | Organization | Limits investigations started by people. | | **Auto-triggered** | Organization | Limits investigations started automatically from alerts, schedules, and service-account API or MCP calls. | | **Worker-triggered** | Organization | Limits investigations started by Traversal Workers. | | **Per-member** | Every member | One limit, applied to each member separately. | | **Per-Worker** | Every Worker in a mode | One limit per Worker mode, applied to each Worker separately, for a day and for a cycle. | Per-member and per-Worker limits are not shared pools. Each member and Worker gets the full applicable limit. ### Per-member limits The per-member limit is a single limit that applies to every member. Set it to 50 and each member can use 50 credits, independently of everyone else. It counts only investigations with a person behind them: * Anything a member starts in the web app * An `@mention` or DM to Traversal in Slack or Teams * API or MCP calls made with that member's credentials * Investigations started by a private chat Worker that member owns It does **not** count auto-triggered or Worker-triggered investigations. Those are capped by their own organization-wide limits, so an alert storm cannot consume a member's limit. The per-member limit has two important rules: * **You can't set a different limit for each member yet.** One value applies to every member. Custom limits for an individual member are coming soon. * **The organization-wide Human-triggered limit still applies.** A member with usage remaining can't start an investigation after the organization limit is reached. ### Worker limits Worker limits are configured separately for each Worker mode: * [Incident Workers](/using-traversal/incident-workers) * [Alert Workers](/using-traversal/alert-workers) * Custom Workers Each has two periods: * **Daily limit** — resets at the start of each day * **Cycle limit** — resets at the start of each month Resets happen in the time zone configured for the limit. A Worker must have usage available under both limits to start a new investigation. Unlike members, a single Worker can be given its own limit. Set it from the [**Workers** view](/using-traversal/workers-console) and it applies to that Worker only; every other Worker stays on the limit for its mode. Clear it to put the Worker back on the default. ## Organization ceiling Traversal sets an organization ceiling based on your contract. Your Human-triggered, Auto-triggered, and Worker-triggered limits cannot exceed this ceiling. Per-member limits don't count toward it. Contact your Traversal representative if you need a higher ceiling. ## How limits are enforced Traversal checks usage before a new investigation starts. Two checks can apply: 1. The organization-wide limit for that type of investigation. 2. The limit for the member or Worker starting it. Both must have usage available. ## What happens when a limit is reached Traversal stops new investigations covered by that limit. The message names the limit and when it resets. This work continues: * Investigations already running * Follow-ups to existing investigations * Reading and searching past investigations * Work covered by a different limit Workers keep working when a limit is reached. A Worker stays in its channel, answers from the channel and from investigations it has already run, and can still follow up on an existing investigation. It just can't start a new one until the limit resets. For example, reaching the Auto-triggered limit does not stop a person from starting an investigation if the Human-triggered limit still has usage available. ## Worker behavior at a limit Workers can read the limits that apply to them. A Worker will: * Warn the channel when it's approaching a limit * Explain when a limit prevents a new investigation, and when the limit resets * Keep answering from the channel and from existing investigations * Turn down a schedule its usage can't support, and suggest a lower frequency * Pick up a limit increase while it's running ## Usage alerts You can get email alerts as usage approaches a limit. For each alert, configure: | Setting | Options | | - | - | | **Limit** | Any configured usage limit | | **Threshold** | A percentage, or a number of credits | | **Recipients** | Organization admins; admins and the affected member; or selected users | | **Channel** | Email | You can set more than one threshold on the same limit — 50% and 80%, for example. Traversal sends a separate notification when the limit is reached. Each threshold sends at most one email per usage window. If you raise the limit so the threshold is no longer met, that alert can fire again later in the same window. Alerts stay attached to a limit when you change it. You don't need to recreate them. ## Changing a limit Changing a limit does not reset current usage. If a limit is 500 credits and 400 are already used, raising it to 800 leaves 400 available. Set a limit to **0** to block all new usage covered by it. Set a limit to **Unlimited** to remove it. Organization-wide limits that count toward your ceiling can't be set to Unlimited. ## Frequently asked questions ### Who can change usage limits? Organization admins. The ceiling itself is set by Traversal. ### Does reaching a limit stop an investigation that is already running? No. Limits are checked before a new investigation starts, so work in progress finishes. ### Are follow-up questions metered again? No. A follow-up to an existing investigation is not a new investigation. ### Can one member exceed the organization-wide limit? No. Both the member's limit and the organization-wide limit apply. ### Is a per-member or per-Worker limit a shared pool? No. Each member and Worker gets the full applicable limit. ### Can I give different members different limits? Not yet — custom limits for an individual member are coming soon. For now, raise the per-member limit for everyone, or raise the organization-wide Human-triggered limit. Individual Workers can already have their own limit. ### Does a member's limit cover investigations that alerts or Workers start? No, except for a private chat Worker, whose investigations count against its owner's limit. ### What is the difference between Auto-triggered and Worker-triggered usage? Auto-triggered covers alerts, schedules, and service-account API or MCP calls. Worker-triggered covers investigations Traversal Workers start. An investigation counts against one, never both. ### What happens when a Worker reaches its daily limit but still has cycle usage left? It stops starting new investigations until the daily limit resets. Remaining cycle usage does not override the daily limit. ### Can I give one Worker a different limit? Yes. Set a custom limit from the **Workers** view. ### What happens if Traversal can't read our limits? The investigation runs. A problem reading your limits is never reported as a reached limit, and unmetered usage still appears in your session history. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.