Skip to main content
This documentation is for the federal deployments of Devin. Back to Devin Docs
Read and manage per-user ACU cap overrides. A user override takes precedence over team and group limits — see ACU Limits for how the effective limit is resolved. These endpoints are available only on multi-tenant federal deployments. They use Teams Read-Only for reads and Teams Update for writes. Both endpoints select the user with a user object containing exactly one of:
string
The user’s email address.
string
The user’s stable ID, as returned by the API (for example in group member or ACU consumption rows).
Group-scoped service keys can only select current members of their assigned group; other users return not_found. See the API overview for authentication and errors. The cap object returned by both endpoints:

Get a user’s ACU cap

Set or clear a user’s ACU cap

Exactly one of the following must be provided:
number
Sets the user’s per-cycle ACU override. Must be non-negative; 0 blocks the user from consuming any ACUs.
boolean
Removes the user’s override so team and group limits apply again.
The response contains the updated cap object.
A user override of 0 blocks the user. The service-key group API does not accept a zero group cap: set_cycle_acu_limit must be positive and clear_cycle_acu_limit removes the group override. The portal’s separate group-limit operation treats 0 as clearing. See Zero and unset values.