> ## 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/setup/index",
  "feedback": "Description of the issue"
}
```

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

</AgentInstructions>

# Generating embedded user sessions

> Set up your embedding infrastructure and generate user sessions.

You have two options when it comes to generating embedded user sessions:

## Easy: Standard SSO

With [**standard SSO**](/embed/setup/standard-sso), you 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.

## Advanced: 2-step SSO

With [**2-step SSO**](/embed/setup/two-step-sso), you start by sending a `POST` request to generate the embed user and session. Then, you'll 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.