Credit spend limits FAQ
Answering questions about the credit spend limits feature.
Credit spend limits let workspace admins control credit usage by setting spending caps on workbooks and tables. This helps teams manage budgets, prevent overspending, and allocate resources across projects and users.
Who can set and manage credit limits?
Who can create and modify credit spend limits?
Only workspace admins can create and modify credit spend limits. While Admins and Editors can both create workbooks and tables, only Admins can control the spending limits applied to them.
Can Editors set limits on workbooks they create?
No, to maintain clear governance, only Admins can set credit limits. If an Editor creates a workbook and no default limits exist, the workbook will operate without spending restrictions until an Admin applies one.
How do limits apply to Viewers?
Since Viewers can't create workbooks, an Admin must create one on their behalf and set a spending limit for their use.
What can have credit limits?
What resources can have credit limits applied?
Credit limits can be applied to:
- Workbooks (primary level)
- Standard tables
- Signal tables
- Campaigns
All of these exist within workbooks, making workbook-level limits the primary control mechanism.
What about legacy tables created outside of workbooks?
Credit limits aren't available for legacy tables created before the workbook architecture. To set a limit for a legacy table, move it into a workbook first.
How do credit limits work?
Can Admins set default limits for all workbooks?
Yes. Admins can set default limits that apply to new workbooks or existing legacy tables created by Admins or Editors. They can choose whether to apply these defaults to all existing workbooks or only to new ones created after the default is set.
Can limits be increased or decreased after they're set?
Yes. Admins can adjust limits up or down at any time for both workbooks and legacy tables.
How long does a credit limit last?
Limits are designed with a monthly cadence in mind, aligning with how most enterprise customers plan their budgets and credit usage. Final confirmation on the cadence (monthly vs. lifetime limits) is pending user research.
What happens when a billing cycle resets?
Limits don't automatically reset or reapply when billing cycles reset. Admins maintain full control and can modify limits as needed. The system is designed with a monthly cadence in consideration.
Are limits set as a percentage or fixed number of credits?
Limits are set as a fixed number of credits rather than a percentage. This provides clearer control since credits don't reset, and all new workbooks are automatically assigned predetermined limits by the Admin.
What happens when limits are reached?
What happens when a workbook hits its credit limit?
When a limit is reached:
- All credit-consuming processes stop
- Users see a message that the limit has been reached
- Any recurring spends are canceled
- Users are notified of canceled processes
Can users request a limit increase?
Users can request higher limits from their Admin outside of Clay. Since Admins can modify limits directly, there's no in-product flow for requesting increases in the initial scope. Team members should reach out to their Admin directly.
What happens if an Admin lowers a limit below what's already been spent?
If a workbook originally had a 200-credit limit with 100 credits spent, and an Admin lowers the limit to 80 credits, users will immediately see a message that the limit has been reached. Any recurring spends will be canceled, and users will be notified.
What happens if a source is running when the limit is hit?
The process will stop, similar to how Clay handles other credit exhaustion scenarios today. Future enhancements may include options to pause and resume later.
Notifications and communication
Who receives notifications when a workbook approaches or hits its limit?
Notifications are sent to:
- Workspace Admins (who can modify limits)
- Any users explicitly added to that specific workbook
Notifications will be delivered via both email and in-product UI across various surfaces.















