> ## Documentation Index > Fetch the complete documentation index at: https://docs.getcollate.io/llms.txt > Use this file to discover all available pages before exploring further. # AI Mode in Collate 2.0 | Official Documentation > Collate 2.0 introduces AI Mode, a new AI-native interface where the new capabilities live. Learn what is in it and how to turn it on for yourself, for a persona, or for the whole tenant. # AI Mode **Collate 2.0 introduces AI Mode: a second, AI-native interface for the whole platform.** Classic Mode is the Collate you already know: the catalog-first navigation with Explore, Govern, Observability and Settings. AI Mode puts an assistant at the centre and rebuilds the same estate around conversation, agents and automations. Both modes run against the same data, the same permissions and the same APIs. Switching modes changes the interface, never the content or what you are allowed to see. Collate 2.0 AI Mode home, showing the AI sidebar, Platform Health, Pending Approvals, Announcements and Recommended Improvements alongside the Ask anything prompt AI Mode is where every new 2.0 experience lands first. If you upgrade and stay in Classic Mode, you won't see AI Automations, AI Analytics dashboards, AI Studio, the Inbox, or the conversational surface at all. Nothing is lost, but the new capability isn't visible until someone switches. *** ## What is in AI Mode The AI sidebar is the entry point to every module in the mode. Every item is a full module, not a shortcut. | Module | What it gives you | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **New Chat / Conversations** | Collate AI about your estate in natural language. Conversations are shareable, with collaborators and roles. | | **Home** | Platform Health, Pending Approvals, Announcements, Action Required, Recommended Improvements, Data Products and Top Tier Assets, with AI-written summaries. | | **Explore** | The full 2.0 Explore experience, redesigned. See [Discovery & Search](/ai-2-0/release-2.0/discovery-and-search). | | **Connections** | Services, connections and ingestion agents, with live job progress and streamed logs. | | **Governance** | Glossary, Ontology Explorer, Tags, Metrics, Column Bulk Operations, Workflows, plus the new **AI Governance** registry, shadow-AI triage, approvals, frameworks, policies and reports. | | **Observability** | Data Quality, Incident Manager, Alerts, Test Library, and pipeline observability, reworked for AI Mode. | | **AI Analytics** | AI Dashboards and AICharts, with provenance, scheduled refresh and sharing. | | **AI Automations** | Scheduled agent work, the replacement for the old agent apps. See [AI Agents & Automations](/ai-2-0/release-2.0/ai-agents-and-automations). | | **Data Marketplace** | Domains, Data Products and **Data Access Requests**. | | **Context Center** | Articles, documents, memories and the archive, the knowledge layer the assistant reads from. | | **Inbox** | Activity and Tasks in one place, with assign/reassign and incident root-cause support. | | **AI Studio** | Author your own agents, personas and skills. | Two things sit outside the sidebar and are worth knowing: * **`Cmd`/`Ctrl` + `K`** opens the Ask box from anywhere in AI Mode. * The **prompt input** carries persona-aware suggestions and quick actions such as *Tag Column*, *Add Descriptions* and *Tag PII Fields*. *** ## How to turn AI Mode on Three levers control this. They resolve in a strict order, highest priority first: ``` user preference → persona app mode → tenant default → Classic ``` Any user can switch themselves, at any time, from the profile card at the bottom of the sidebar (AI Mode) or from the profile dropdown in the navbar (Classic Mode). The Switch Interface menu showing Classic and AI options, with AI marked Current and an Open in AI when I log in checkbox * **Classic / AI** switches the current session immediately. * **Open in AI when I log in** persists the choice. This is the per-user preference and it wins over everything else. Switching is the only sanctioned way to change mode. No URL forces the switch. A persona can pin the interface for everyone assigned to it. Set `appMode` on the persona to `AI` or `classic` (default `classic`). Use this to roll AI Mode out to a pilot group (for example a *Data Analyst* persona) without touching anyone else. A user's own preference still overrides the persona. Admins can set a tenant-wide default under **Settings** > **Preferences** > **App Mode**. Three options: | Option | Effect | | -------------- | ------------------------------------------------------------------------------ | | **No default** | Users land in Classic unless a persona or their own preference says otherwise. | | **Classic** | New users start in Classic. | | **AI** | New users start in AI Mode. | The same value can be seeded at first boot with `APP_DEFAULT_MODE=ai` (or `classic`) in `openmetadata.yaml`. After first boot the database row wins and the YAML value is ignored. The setting is admin-mutable at runtime. The switcher only appears when the AI application is installed. On a deployment without it, users stay in Classic Mode and the toggle is hidden rather than shown in a broken state. It is also hidden in the Collate desktop app, which manages its own shell. ### Recommended rollout Leave the tenant default at **No default**. Switch yourself with the interface switcher and tick **Open in AI when I log in**. Nobody else is affected. Create or reuse a persona for the pilot group and set its `appMode` to `AI`. Members land in AI Mode on login, and any individual can still switch back to Classic for themselves. Set **Settings** > **Preferences** > **App Mode** to **AI**. Existing users who have already expressed a preference keep it. The tenant default only decides for users who haven't chosen. *** ## AI Mode URLs changed **Breaking.** AI Mode routes dropped the `/askCollate` prefix in 2.0. | 1.13 | 2.0 | | ----------------------------- | ------------------ | | `/askCollate/conversations` | `/conversations` | | `/askCollate/ai-studio` | `/ai-studio` | | `/askCollate/connections/...` | `/connections/...` | Legacy `/askCollate/*` links are redirected, but anything that parses or constructs those paths (bookmarks in a team wiki, deep links in a Slack workflow, browser extensions) should be updated. AI Mode also **no longer auto-engages** from a URL. In 1.13, visiting certain paths would silently flip you into the AI experience. In 2.0 the mode is explicit: it comes from your preference, your persona or the tenant default, and navigating to an AI-only route while in Classic Mode doesn't change it. *** ## What this means for existing users **Nobody is moved automatically.** The 2.0 upgrade doesn't set anyone's app mode. Every user stays in Classic Mode until they switch, are assigned a persona that pins AI, or an admin sets the tenant default. Practical consequences: * **Training and screenshots**: if you maintain internal enablement material, it now needs to cover two interfaces, or state which one your organisation standardises on. * **Support**: "where is X" questions now depend on the user's mode. The mode is visible on the profile card, so ask for that first. * **Automation**: nothing changes. Both modes call the same REST APIs. App mode is purely a UI concern and is never sent to the server as part of a data request. *** ## Related The agent apps are gone. What replaced them and what you must do after upgrading. Conversation sharing, collaborators, and the reworked credit model. The redesigned Explore experience, shared by both modes. The full 1.13 → 2.0 breakdown, component by component.