> ## Documentation Index > Fetch the complete documentation index at: https://docs.omni.co/llms.txt > Use this file to discover all available pages before exploring further. # Choosing your embed configuration > Select the right approach for your embedded Omni use case. [All guides](https://docs.omni.co/guides.md) Progress % Category embed Last updated October 2026 # Choosing your embed configuration ## Requirements Before working through the scenarios below, make sure you have: * An Omni instance with [external embed configured](https://docs.omni.co/embed/setup/standard-sso.md) and your embed secret * Organization Admin access to manage embed sessions and access connection settings * A test dashboard, workbook, and connection you can generate example URLs against ## Identifying the pattern you need Five embed patterns cover most deployment scenarios: a single dashboard, that same dashboard with AI, the standalone AI chat, and Create Mode with or without tenant isolation. Each one is a different combination of Omni embed parameters. To determine which pattern matches your desired end user experience, consider the following questions and then refer to the following table to jump to the right section: 1. Should embed users land on a specific dashboard? Or should they land in an AI chat? 2. Should embed users have access to an AI chat interface at all? 3. Should embed users have the ability to build and share their own dashboards? 4. Do embed users need to be automatically isolated from others, such as when embedding for multiple customer groups? | Landing area | AI access | Building ability | Content isolation | Approach | | - | - | - | - | - | | Dashboard | No | No | Automatic | [Dashboard, no AI](#dashboard-no-ai) | | Dashboard | Yes | No | Automatic | [Dashboard, with AI](#dashboard-with-ai) | | Omni Agent | Yes | No | N/A | [Chat only](#chat-only) | | Hub, AI, or Folder | Yes | Yes | Manual | [Create Mode without entities](#without-entities) | | Hub, AI, or Folder | Yes | Yes | Automatic | [Create Mode with entities](#with-entities) | ## Single-content embeds If you only want users to view a piece of content but not navigate or build, use `mode=SINGLE_CONTENT` to place one piece of content into the iframe with no app navigation or headers. The following patterns all use this mode, but you can customize the content and connection permissions that embed users have. ### Dashboard, no AI Use this pattern when you want to embed a single read-only dashboard without a chat surface. | Parameter | Value | Why | | - | - | - | | `contentPath` | `/dashboards/` | Lands users on a specific dashboard | | `connectionRoles` | `{"": "VIEWER"}` | Allows users to view the dashboard | | `mode` | `SINGLE_CONTENT` | Limits users to the specified content path | | `userAttributes` | `{...}` | Enforces RBAC and row-level security; pass in as needed | ![Embedded dashboard with no AI or navigation](https://mintcdn.com/omni-e7402367/6iClc3eMIcszANRc/guides/embed/images/embed-dashboard-no-ai.png?fit=max\&auto=format\&n=6iClc3eMIcszANRc\&q=85\&s=d84e6815d26abf34aec1baf00d9de7ed) Embedded dashboard with no AI and no navigation. ### Dashboard, with AI Like embedding a [dashboard without chat](#dashboard-no-ai), this pattern uses the same `contentPath`, but with a connection role that allows querying. This role grants users the minimum permissions required to use the Omni Agent on a dashboard. To use this pattern, you'll need: * A published dashboard * To enable the settings required to use the Omni Agent. See the [Omni Agent documentation](https://docs.omni.co/ai/chat.md#requirements) for more information. * To enable **Read data result** in **AI Hub > General** * To enable the **AI on dashboard** ability, either turned on by default for all content or per document (**File > Settings > Chat with Content**). | Parameter | Value | Why | | - | - | - | | `contentPath` | `/dashboards/` | Lands users on a specific dashboard | | `connectionRoles` | `{"": "RESTRICTED_QUERIER"}` | Allows users to run queries and use the Omni Agent on a dashboard | | `mode` | `SINGLE_CONTENT` | Limits users to the specified content path | | `userAttributes` | `{...}` | Enforces RBAC and row-level security; pass in as needed | ![Embedded dashboard with the inline AI chat panel](https://mintcdn.com/omni-e7402367/6iClc3eMIcszANRc/guides/embed/images/embed-dashboard-ai.png?fit=max\&auto=format\&n=6iClc3eMIcszANRc\&q=85\&s=79a56c3e38e709df682a973038fb089e) Embedded dashboard with the inline AI chat panel. ### Chat only Use this pattern when you want to embed a chat-first experience. This pattern points `contentPath` directly at [`/chat`](https://docs.omni.co/embed/setup/url-parameters/contentPath), with Restricted Querier permissions that allow the user to run queries through the Omni Agent. | Parameter | Value | Why | | - | - | - | | `contentPath` | `/chat` | Lands users directly in the Omni Agent chat interface | | `connectionRoles` | `{"": "RESTRICTED_QUERIER"}` | Scopes chat to a specific connection and model | | `mode` | `SINGLE_CONTENT` | Limits the Omni Agent to answering questions in chat. It can create charts, but users can't save them. | | `userAttributes` | `{...}` | Enforces RBAC and row-level security; pass in as needed | ![Standalone embedded chat interface](https://mintcdn.com/omni-e7402367/6iClc3eMIcszANRc/guides/embed/images/embed-chat-only.png?fit=max\&auto=format\&n=6iClc3eMIcszANRc\&q=85\&s=b54ca9c513c55bd83ca3cecc9e0dba0d) Standalone embedded chat interface. > [!TIP] > > **Want to fully customize the chat experience?** Instead of using this pattern, use the Omni API or MCP Server to create a fully custom experience. See [Connect a chat agent to Omni AI for embed experiences](https://docs.omni.co/guides/embed/ai-chat-agent.md) for more information. ## Create Mode embeds If you want to allow users to navigate and build content, use `mode=APPLICATION` to give them the full Omni app — navigation, the **Hub**, **My Documents**, the ability to build and save content — instead of a single piece of content. The patterns in this section differ in whether Omni handles tenant isolation for you, where tenants are typically your customers. For example, if you plan to provide several customer groups access to Omni, you may want to ensure that they don't know about one another, and that their content remains fully isolated. ### Without entities Use this pattern when you want to embed a single tenant, an internal tool, or any case where you're handling isolation yourself through existing groups rather than relying on Omni's per-customer folders. Pass in `mode=APPLICATION` and any group membership relevant to the user. Choose a content path based on where you want users to land after login: * `/my` lands users in their **My Documents** folder * `/root` lands users in the shared **Hub** * `/chat` lands users in the Omni Agent, where Create Mode lets them have the agent build and save content back to their personal documents folder | Parameter | Value | Why | | - | - | - | | `contentPath` | `/my`, `/root`, or `/chat` | Lands users in **My Documents**, the **Hub**, or the Omni Agent | | `connectionRoles` | `{"": "RESTRICTED_QUERIER"}` | Allows users to create content, not just view it | | `mode` | `APPLICATION` | Allows users to navigate accessible folders and content | | `groups` | `[""]` | Associates users with groups you manage | | `userAttributes` | `{...}` | Enforces RBAC and row-level security; pass in as needed | ![Embedded app in Create Mode with full navigation, landing on the Hub](https://mintcdn.com/omni-e7402367/6iClc3eMIcszANRc/guides/embed/images/embed-application-no-entity.png?fit=max\&auto=format\&n=6iClc3eMIcszANRc\&q=85\&s=652368a39f3341e6b38bb6a4c6053a4f) Embedded app in Create Mode with full navigation, landing on the Hub. ### With entities Use this pattern when you want to create a multi-tenant, self-service experience, where Omni automatically creates an isolated shared folder and group for each customer. Along with `mode=APPLICATION`, pass the [`entity`](https://docs.omni.co/embed/setup/url-parameters/entity) parameter to associate the user with an entity. The first time Omni sees a new entity value, it creates the shared folder and group. The shared folder is visible only to that entity's members and Organization Admins. You can then land the user directly in their entity's shared folder with `contentPath=/entity-folder`. | Parameter | Value | Why | | - | - | - | | `contentPath` | `/my`, `/root`, `/entity-folder`, or `/chat` | Lands users in **My Documents**, the **Hub**, their entity folder, or the Omni Agent | | `entity` | `` | Creates or looks up the tenant's dedicated shared folder and group | | `connectionRoles` | `{"": "RESTRICTED_QUERIER"}` | Allows users to create content, not just view it | | `mode` | `APPLICATION` | Allows users to navigate accessible folders and content | | `entityFolderContentRole` | `NO_ACCESS` \| `VIEWER` \| `EDITOR` \| `MANAGER` | Controls what users can do in the entity folder. `EDITOR` and `MANAGER` access allow saving to the folder. | | `entityFolderLabel` / `entityGroupLabel` | `` | Overrides the generated folder/group name. Useful for merging several entity values under one display label. | | `userAttributes` | `{...}` | Enforces RBAC and row-level security; pass in as needed | ![Embedded app in Create Mode with full navigation, landing on the Hub with an entity folder](https://mintcdn.com/omni-e7402367/6iClc3eMIcszANRc/guides/embed/images/embed-application-entity.png?fit=max\&auto=format\&n=6iClc3eMIcszANRc\&q=85\&s=de8e87d9db03e96bf97d47bbc554ebdc) Embedded app in Create Mode with full navigation, landing on the Hub, with an entity folder. > [!NOTE] > > **Sharing content with entity groups**. Regular folders in Omni behave as usual, even when intermingled with entity-specific folders. This means you can share content with entity groups and still maintain isolation. > > For example, share a **Template** folder with **Viewer** access to allow embed users to view other content and save their own version to their entity folder. ## Next steps * [Securing your embed](https://docs.omni.co/embed/best-practices.md) — permission guardrails before any of these go live * [Embed environment architecture](https://docs.omni.co/guides/embed/embed-development-production-setup.md) — staging and production setup once you've picked a pattern * [Create a custom sidebar and theme](https://docs.omni.co/embed/customization/themes.md) — style the embedded app to match your product * [Managing AI credits for embed entity groups](https://docs.omni.co/embed/admin/ai-credits.md) — relevant once the entity-based Create Mode pattern is live with real tenants For additional configurations or detailed setup guidance, reach out to your Omni support team. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.