Skip to main content
Create and customize user sessions by including URL parameters in your embed requests. For example, you can use embed URL parameters to:
  • Specify user content roles
  • Assign connection and model roles to users
  • Control the look and theme of your embedded application
  • Apply user attributes to users

How sessions update embed users

Each embed session syncs the embed user to the parameters in that request. Omni doesn’t merge the new values with the user’s existing values. This means that if you leave out a value, Omni removes what that value set before. To keep a user’s access the same for each session, send the same values for every session.
Embed MCP tokens follow the same rules. If your embed URLs and MCP tokens use the same externalId, see Embed user MCP tokens for how to keep the user’s access consistent.

Parameter inclusion and URL signing formats

The signing format you use for embed URLs determines how parameters are included:
  • In the v1 signed payload format, all parameters are carried inside a single payload parameter, and JSON-valued parameters such as userAttributes stay as JSON instead of being stringified and URL encoded.
  • In the legacy v0 format, each parameter is sent as its own URL parameter.
A v1 payload also carries an exp expiry that isn’t listed below as it isn’t something you set per session in the same way. See URL expiry for more information.

All parameters

Valid embed requests must contain all required parameters. Recommended parameters aren’t required, but we strongly suggest that you include them.