Skip to main content
Cassidy gives you two layers of credit visibility: organization alerts that track your team’s total usage against the allowance for your billing period, and per-user alerts and limits that monitor and cap individual consumption. Both are configured in Organization Settings → Limits & Alerts.
Only Admins can configure credit alerts and limits.

Organization alerts

Organization alerts notify admins when your organization’s total credit usage crosses a threshold you define. They are informational only — they don’t restrict usage. Every organization starts with a default alert that notifies all admins at 85% of the organization’s credit limit for the billing period. It’s labeled (default) in the alerts table, and you can edit or remove it like any other alert.

Add an alert

1

Open organization settings

Open your account menu from the sidebar and select Organization Settings.
2

Navigate to Usage Limits

In the left sidebar, click Limits & Alerts under the Usage section.
3

Open the Organization Credit Alerts section

Find Organization Credit Alerts at the top of the page, then click Add alert.
Organization Credit Alerts on the Limits & Alerts page
4

Choose a threshold type

Select how the threshold should be measured:
Percentage thresholds automatically scale if your credit allowance changes. Absolute thresholds give you a precise spending target.
Adding an Organization Credit Alert
5

Set the threshold value

Enter the percentage (1–100) or credit count that should trigger the alert.
6

Choose who to notify

Select either All Admins or Specific Admins. If you choose specific admins, use the selector to pick who should receive the alert email.
Selecting admins to notify when the alert triggers
7

Save

Click Add to activate the alert.
The alert will fire the first time your organization’s credit usage crosses the threshold within each billing period.

How organization alerts work

  • Each alert fires once per billing period. Usage dropping below the threshold and climbing back above it will not re-trigger the alert until the next billing period resets.
  • You can configure multiple alerts at different thresholds — for example, one at 50% and another at 90% — to get early warnings and final notices.
  • To change a threshold or notification recipients, click the pencil icon next to an alert. To remove an alert, click the trash icon.
Editing an alert’s threshold resets it so it can fire again in the current billing period. If your organization is already past the new threshold, the alert will trigger immediately.

Per-user alerts and limits

Per-user controls let you notify admins when individual team members exceed a credit threshold, and optionally enforce a hard cap that blocks users from consuming additional credits once their limit is reached.

Check your usage remaining

When per-user credit limits are active and usage visibility is enabled, open your account menu in the sidebar and point to Usage Remaining. The flyout shows the percentage of your credits remaining, the credits used, and when the limit resets. For limits that do not reset, the flyout shows All time instead of a reset date. If you reach your limit, the flyout directs you to an admin or, if you can manage usage limits, to Organization Settings → Limits & Alerts.

Set up per-user credit usage alerts

Credit usage alerts notify selected admins, the user whose activity triggered the alert, or both when a team member crosses a configured threshold. You can create multiple alerts with different thresholds and periods. Alerts are informational only — they don’t block users from consuming additional credits.
1

Open organization settings

Open your account menu from the sidebar and select Organization Settings.
2

Open user credit alerts

In the left sidebar, click Limits & Alerts under the Usage section. Find User Credit Alerts, then click Add alert.
User credit alerts section on the Limits & Alerts page
3

Set the threshold and period

Enter the number of credits that triggers the alert, then choose whether Cassidy measures usage by day, week, month, or billing period.
4

Choose recipients

Turn on Notify the user who triggered the alert to email the team member whose usage crossed the threshold. Choose All Admins or Specific Admins for the admin recipients.
5

Add an optional message

Enter a message to include extra context or instructions in the alert email. Each alert can have a different message.
User credit limit modal showing credit limit, period, recipients, and optional message
6

Add the alert

Click Add to activate the alert. Repeat these steps to create more thresholds.
Each alert sends one email per user during its configured period. Editing an alert lets the updated alert fire again if the user is already above its threshold.

Set up per-user credit limits

Per-user credit limits set a hard cap on how many credits each team member can use per day, week, month, or billing period. When a user hits their limit, they are blocked from credit-consuming actions and shown an explanation. The User Credit Limits section is organized into four tabs:
1

Enable user credit limits

On the Limits & Alerts page, toggle on User Credit Limits.
User Credit Limits section enabled, with the Limits tab open
2

Set the default limit

On the Limits tab, under Default Limit Per User, enter the number of credits each user can use, then choose how often the limit resets: every day, week, month, or billing period.
Default Limit Per User field with a credit amount and a reset interval selector
3

Choose whether users can see usage remaining

Leave Show Usage Remaining to Users on to show the Usage Remaining flyout in each user’s account menu. Turn the setting off to hide the flyout from users. The setting is on by default.
4

Select admins to notify

Under Admins to Notify, choose which admins receive an email when any user hits their credit limit.
Admins to Notify selector for user credit limits
5

Save

Click Save at the top of the page.
User credit limits are now active. Each user’s usage resets at the start of every interval you chose.

Set custom limits for specific users

Custom limits override the default limit for individual users. They take effect as soon as you add, edit, or remove them; you don’t need to click Save.
1

Open the Custom limits tab

Open the Custom limits tab to see every user with a custom limit, along with their limit and reset interval. Click Add Custom Limit to add one.
Custom limits tab showing users with custom credit limits and the Add Custom Limit button
2

Configure the custom limit

Select the user, then choose an override mode:
  • Custom Limit — Enter a Credit Limit and choose how often it resets under Reset every. If you don’t choose an interval, the custom limit resets on the same schedule as the default limit.
  • Unlimited — The user has no credit limit.
Add Custom Credit Limit modal with a user, credit limit, and reset interval selected
Click Add to apply the custom limit. To change or remove a custom limit later, click the pencil icon or trash icon next to it.

Exclude usage from user credit limits

Open the Exclusions tab to choose which usage doesn’t count toward user limits. Organization limits still apply to all usage.
  • Exclude All Agent External Deployments — Credits used by externally deployed Agents won’t count toward user limits.
  • Exclude All Workflows — Credits used by Workflows won’t count toward user limits.
User Credit Limits section with the Exclusions tab open, showing the exclusion toggles and the Excluded Agents and Workflows table with each Agent's and Workflow's icon next to its name
To exclude individual Agents or Workflows, click Add Exclusion, choose Agent or Workflow, and select it from the list. Only published Agents and Workflows you have access to appear in the list. Credits used by an excluded Agent or Workflow don’t count toward user limits, and users who have reached their limit can keep using it.
Add Exclusion modal with an Agent selected and a warning listing a Workflow the Agent can run that isn't excluded
Excluding an Agent doesn’t exclude the Workflows it runs. If a user who has reached their limit asks an excluded Agent to run a Workflow that isn’t excluded, that Workflow run still stops at the limit. When you select an Agent that can run Workflows that aren’t excluded, the modal lists them so you can exclude them too.
The Excluded Agents and Workflows table lists every exclusion in your organization, with each Agent’s or Workflow’s icon, name, and creator. Exclusions for Agents or Workflows you don’t have access to show a default icon and no name or creator, and you can still remove them. Remove an exclusion to apply limits to that Agent or Workflow again. Removing an exclusion only affects usage from that point on; credits used while it was excluded stay excluded, so users won’t suddenly exceed their limit.
Excluding Workflow and deployment credits is useful when those are shared team resources, not individual consumption. Exclude individual Agents or Workflows that users must always be able to reach, such as support or onboarding Agents.
The exclusion toggles apply when you click Save. Individual exclusions apply as soon as you add or remove them.

Monitor users over their limit

When any user has reached their limit, a warning appears above the tabs. Click View, or open the Over budget tab, to see each of those users with their current usage, limit, and reset interval.
Over budget tab listing users who have reached their credit limit
Click a user to add or edit their custom limit, for example to raise it or make them unlimited.

Comparison

All three can be used together. For example, set an organization alert at 80% to track overall spend, per-user alerts to catch high individual usage early, and per-user limits to enforce a hard ceiling.

Next steps

Manage credits

Understand how credits work and check your balance.

Monitor usage

Track credit, storage, and meeting usage across your organization.