Docs · LLMs and developers
Version3.14.0Administrator reference for assistant capability configuration, limits, and troubleshooting.
Managing assistant capabilities
Use this page when you need to manage assistant capabilities in the app.
An EA's capabilities are in its Settings tab, at https://{your-slug}.achiral.ai/assistants/{assistant-slug}/settings/capabilities, which only the EA's owner can open. The Capabilities section sits beside Behavior, Knowledge, and Retire.
What capabilities are
Capabilities control which assistant actions or behaviors are enabled for a given assistant.
The app exposes:
- a capability registry;
- enabled capability lists per assistant;
- assistant-specific capability configuration; and
- validation based on assistant type and organization tier.
See Assistant capabilities API for the route-level reference.
Who can manage capabilities
- Owners and admins of the organization can change any assistant's capabilities through
PATCH /api/assistants/{assistantId}/capabilities. - Members of the organization can read an assistant's capabilities, and see their own EA's in its Settings tab. Saving a change returns an error unless you are an owner or admin.
Basic flow
- Open your EA's settings and choose Capabilities.
- Review the assistant's currently enabled capabilities.
- Enable or disable the capabilities you want.
- Fill in any required configuration fields.
- Save the changes.
Plan limits
The app enforces capability limits by plan tier.
| Tier | Capability limit |
|---|---|
| Free | 3 |
| Spark | 3 |
| Seed | 7 |
| Rise | 7 |
| Boost and above | Unlimited |
The app also treats some capabilities as always enabled.
Required configuration
Some capabilities require extra configuration before they can be saved.
Examples from the current registry include fields such as:
allowedOrderTypesmaxOrdersPerDayrequiresApprovalemailProviderallowedChannels
If a required configuration block is incomplete, the save should fail until the missing values are added.
Good operating practice
- Enable only the capabilities a team actually needs.
- Start with conservative settings for actions that can create side effects.
- Prefer approval requirements for sensitive actions.
- Revisit capability choices as the organization's workflow changes.
Common problems
The UI will not let me enable another capability
You may have reached the limit for your current plan tier. Disable an existing optional capability or move to a higher tier.
A capability will not save
Check whether it requires extra configuration fields.
A capability change does not show up in an existing conversation
Start a new conversation or retry from a fresh assistant session if the current session does not pick up the change.