- 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.
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.
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
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
@mentionor 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
- 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
- Alert Workers
- Custom Workers
- Daily limit — resets at the start of each day
- Cycle limit — resets at the start of each month
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:- The organization-wide limit for that type of investigation.
- The limit for the member or Worker starting it.
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
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:
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.