Actions16
Location (Sub-Account) → Update Features & Limits
AI-generatedSummary
Replace a sub-account’s complete enabled-feature set by sending PUT /locations/{locationId}/permissions. Supply every feature that should remain enabled; omitted features are turned off.
Inputs
- Sub-Account (required) — The target location ID, selectable from the agency’s locations or supplied as an expression.
- Enabled Features — Select the full set of feature slugs to keep enabled from the 25 supported options. An empty list is rejected; omitted features are disabled.
- Enabled Features (JSON) — Optional JSON array of feature slugs; when non-empty, it overrides the picker. Invalid JSON, non-arrays, non-string entries, or unknown slugs throw an error. Use the complete desired list.
Output shape
A single item per input item containing the API response object, or a fallback object with success, locationId, and permissions if the API returns no body.
The location’s read-side
permissionsbooleans use a different vocabulary and have no documented one-to-one mapping to these feature slugs. Build the desired feature list explicitly.