> ## Documentation Index
> Fetch the complete documentation index at: https://ai-kb.automationanywhere.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 2.0.0

> Released 2026-04-01

## New Features

### Tool descriptions in the builder

Workflow and agent steps can show richer **tool descriptions** in the UI (including the **trigger config** panel), with **tool names synced** from the backend where applicable.

### Connect another OAuth account

For OAuth-based toolkits, use **Connect another account** to link additional identities without replacing your existing connection. **Test Connection** for OAuth toolkits is more dependable end-to-end.

### Sign-in, consent, and terms

Sign-up and login support configurable **consent** copy, **single sign-on (SSO)**, and **shared terms of use** so policies and branding stay aligned across the application.

### Team branding on the landing page

**Team branding** (logo and theme) extends to the **landing page in agent mode** for a consistent first impression.

### On-prem API keys

**API keys** can be enabled for **on-premise** deployments where that matches your security model.

### License and billing visibility

**Team-based license expiry** behavior and a **license validity** view on billing make plan status and limits easier to see.

### Database toolkit write permissions

The **database toolkit** includes clearer **write permission** handling for safer automation against your data.

### Vault-aware toolkit configuration

Toolkit connection fields can use **vault-backed secret inputs** so sensitive values are not stored or shown as plain text in the UI. **Vault-backed variables** can feed **datastore cache** and toolkit connections on the backend.

### Project export (modal + KB skip)

**Project export** uses a dedicated **modal** flow, with an option to **skip knowledge base** export when you only need configuration and metadata. **Super Admin** template export validation handles modern agent shapes correctly.

### Chatbot widget: resizable window & SSO

The **embedded chatbot widget** adds a **resizable window**, **popup-based SSO**, alignment with the main app's SSO checks, and **Supabase** integration where used for email capture. **Public chatbot feedback** controls are available where applicable.

### New and expanded toolkits (agents & workflows)

* **Amazon S3**, **Trello**, and **Zoho CRM** toolkit surfaces (aligned with backend registration).
* **Google Calendar** and **Google Forms** **v2** for Automator, with **OAuth reconnect** where needed.
* **Facebook Pages**, **File Helpers**, and **platform tools** migrated toward **v2**; **v2 migrator** for platform tools.
* **Duplicate Sheet** (Google Sheets), **Newer Jira** toolkits, and **Slack** UI updates (**channel search** / **message search** arguments) building on channel search capabilities.
* **Crypto** toolkit UI (**HMAC Signature** tool) and **Notion** step UI refinements (custom API call form).
* **Zoho People**: **leave management** tools and **pagination** notes on employee listings (extends the People integration).
* **Fetch metadata** tool for the **KB toolkit**; optional **metadata-based filtering** configuration.
* **Platform / Node.js** toolkit execution improvements on the backend; **GitHub** tools: **filters** on list pull requests and **date filtering**.
* **M365** toolkits: ongoing **refactor** of remaining tools for consistency.

### Approval workflows

**Approval** nodes in workflows support **signals / wait** behavior, **approval URL host** configuration, and smoother handling of **nested approvals** and multi-step approval flows.

### Templates & installation

**Project name** prompt when **installing a template**; **templates info** surfaced in **Super Admin**; **templates info** page in the app.

### Images in chat

**Image upload**, **paste-to-upload**, and **images in chat** for **dashboard** flows.

### Roles & permissions

Role UI adds **upload\_files** and **run\_tools** **chat permissions** so you can govern file uploads and tool execution per role.

### Per-user Python sandbox isolation

Project settings support **optional per-user isolation** for **Python sandboxes** (UI + backend), configurable per deployment.

### Project & team administration

* **Project ownership transfer** and related **user/project** management improvements.
* **Team Admin** entry on the **user dashboard**; APIs expose **team owner** and **team admin** views; **admins** can inspect **team logs** where enabled.
* **Restrictive SAML** team/project assignment rules, optional **continuous SAML-based reassignment**, and clearer workflows when **deleting users** who **own projects** or teams (**transfer** / cleanup).
* **Target project ID** and **workflow request metadata** propagated for agent/workflow creation and tracing.

### Analytics

* **Agent interactions** tab for reviewing agent activity.
* **Chat audit** UI hooks (where the feature flag allows).

### MCP servers

**API key authentication** for **MCP servers**, **New Relic quick-add**, and improved **MCP OAuth** and **tool inputSchema** handling in custom models.

### Knowledge base: decryption & downloads

**Definable decryption** for **KB items** (UI + backend endpoints). **Direct download** flows use **new download endpoints** without exposing raw storage URLs where applicable.

## Improvements

### Dashboard

Default project behavior, navigation, and **context-aware search** are tuned for the dashboard. **Sidebar** layout, typography, and onboarding copy are refined for the latest UI.

### Chat & embedded widget

Streaming, **SSO**, and session behavior are smoother across the **chat widget** and main app—including **on-prem** sign-in, **project switching**, and **citations** (including **page-based PDF** citations where configured). **Smart tables** in the builder get a cleaner right-panel layout and steadier editing experience.

### Knowledge base & themes

**Knowledge base** setup—**Settings**, **Connections**, and **Sync & Schedule**—is now in **Project settings** under **Knowledge Base**, next to your other project options. Previously, these were only available from the knowledge base **Settings** page.

**Custom searchable metadata** and **external link** metadata on items; crawler can use **Crawl4AI (V2)** instead of **Diffbot (V1)** where configured.

### Data store, builder & tools

**Data Store** scope and vault-aware downloads are more predictable across flows and runs. **Automation Anywhere**: **Get Bot Status** default **timeout** extended to **24 hours** for long bot runs. **JsonBuilder**, **API tools**, **SQL** inputs, **Google Sheets**, **Python tools**, **MCP** counts, and **multi-tool confirmation** flows are clearer and more consistent.

### Security & privacy

Stronger protection for **API keys** in exports and previews; **sensitive data** kept out of URLs where possible; **public** vs **restrict chat** rules are mutually exclusive for clearer access control; hardened **file download** and **sandbox path** policies on the backend.

### Automator & custom models

**PDF** piece progress toward **v2**; **custom LLM** support for **Google AI**-style messages, **non-streaming** mode, and **Anthropic** tool-call shapes. **Automator auth tokens** use a **24-hour** lifetime on the backend. **Project clone** and **WhatsApp** configuration updates for agents.

### Billing & admin

**Super Admin**: **CSV/XLSX export** for LLM metrics and usage dashboards. **HTML preview** can be enabled per project so HTML-oriented behavior stays consistent in chat and citations. Analytics and provider configuration UI updates.

### Backend & platform (release 2.0)

This application release pairs with the **2.0** backend: stronger **sandboxes**, **triggers** and **scheduling**, **workflows** and **tasks**, **knowledge & search** (including multilingual and HTML content), **Google & OAuth**, **SSO**, **usage reporting**, **credits**, and **security / operations**—so the product stays fast, secure, and ready to scale.

## Upgrading from older versions

<Note>
  If you are on an **older release**, we strongly recommend moving to a **recent intermediate version** first—for example [**1.9.0**](/changelogs/1.9.0) or [**1.9.1**](/changelogs/1.9.1)—**testing** your projects and integrations there, then planning your upgrade to **2.0.0**. Stepping through a nearer release makes unexpected behavior easier to isolate than jumping several versions at once.
</Note>
