> ## 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.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.omni.co/feedback

```json
{
  "path": "/embed/quickstart",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# Embedding Omni quickstart

> Get up and running with your embedded Omni application.

<Note>
  **Organization Admin** permissions are required to follow the steps in this guide.
</Note>

<Steps>
  <Step title="Contact Omni support">
    First, reach out to Omni support to have the **Embed** feature enabled for your instance.
  </Step>

  <Step title="Set up session generation">
    You have two options when it comes to generating embedded user sessions:

    1. [**Standard SSO**](/embed/setup/standard-sso): Generate and use a single URL to create an embed user and session. This is the simplest way to embed Omni for your external users.
    2. [**2-step SSO**](/embed/setup/two-step-sso): First, send a `POST` request to generate the embed user and session. Then, generate and use a URL to authenticate into the session. This requires more setup, but has a few advantages over the standard SSO embed experience:

       * **Sensitive user data**: If using the `userAttributes` parameter with sensitive user data, you may prefer creating SSO embed users and sessions via `POST` request for added security.
       * **URL length**: While generally unlikely, there is more risk of standard SSO embed URLs exceeding a browser's URL character limit. 2-step login URLs are more compact and thus have no risk of hitting the limit.

    Follow the guide for your preferred approach to complete the implementation.

    <Warning>
      While Omni is where permissions and content are managed, the application where the content is embedded should dynamically map users to the right underlying data. Refer to the [Embedding best practices](/embed/best-practices) to make sure Omni is set up correctly before you begin developing.
    </Warning>
  </Step>

  <Step title="Customize your application">
    Once you successfully set up your embed infrastructure, you can:

    * Change your application's look and feel with [custom theming](/embed/customization/themes)
    * Add interactivity with [events](/embed/events)
    * Implement [vanity domains](/embed/customization/vanity-domains) for a fully whitelabeled experience
  </Step>
</Steps>