Release 2026.10.10-2
Saved model keys always encrypted with the deployment's own key, deployment administration by AI agents, and processing deadlines that take effect.
- Cloud, United States
- Cloud, Australia
- Self-hosted image
- Not in this release
Security
- Model API keys your organization saves are always encrypted with the deployment’s own key, never with a key built into the application. Keys saved before were re-encrypted when this release started; nobody enters them again.
New
- Deployment administration by AI agents: on a self-hosted deployment, an AI agent can administer settings, organizations, single sign-on, models and the audit log, and any agent finds its way in from
/llms.txt. See System Administration. It reaches the self-hosted image in 2026.10.14-1.
Improved
- The Assistant can read out a Classify step’s rules.
Fixed
- Processing deadlines (SLA) set on a project now take effect, and a deadline is set once, so resuming a transaction does not move it.
- A business calendar that a Review step’s deadline uses can no longer be deleted.
- Confirming ground truth no longer fails on some documents in the cloud service.
API
/llms.txt: the entry point an AI agent reads first, for every job it can do on a deployment.da skill showprints a playbook. See AI agents.da admin credentials status: shows, on a self-hosted deployment, whether every saved secret is under the current encryption key. See Standalone (Single Node).