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

# Email-only users

> Learn how email-only users work in Omni, including how they're created, managed, and used with deliveries and embedded analytics.

<Note>
  **Organization Admin** permissions are required to manage email-only users.
</Note>

An email-only user is a delivery recipient who doesn't have an Omni account. Unlike [Standard or Embed users](/administration/users), email-only users can't log in to Omni — they only receive scheduled [email deliveries](/share/deliveries/email).

## Creating email-only users

Omni automatically creates an email-only user when an [email delivery](/share/deliveries/email) recipient has an email that can't be matched to an existing Omni user. When the delivery is saved, Omni creates an account for the recipient to track delivery usage and related metadata.

Email-only users can also be created programmatically using the [manage email-only user API](/api/schedule-recipients/manage-email-only-user) or the [bulk manage API](/api/schedule-recipients/bulk-manage-email-only-users).

<Note>
  Email-only users aren't counted towards any [licenses](/administration/users/permissions#license-types).
</Note>

## Managing email-only users

To view and manage email-only users, navigate to **Settings > Users** and click the **Email-Only** tab. This tab only appears if there is at least one email-only user in your organization.

<img src="https://mintcdn.com/omni-e7402367/7pKirqXgL1UiAJKn/administration/images/users-email-only.png?fit=max&auto=format&n=7pKirqXgL1UiAJKn&q=85&s=7708ebfec3cb89b40cdad383679a5a43" alt="The Email-Only tab in the Users settings page, displaying a list of email-only users with their names and schedule counts." width="1165" height="428" data-path="administration/images/users-email-only.png" />

The tab displays each user's **Name** and the number of **Schedules** they are included in.

### Inviting email-only users to your organization

Email-only users can be invited to join your organization as a [standard user](/administration/users/invite). The email-only user's user attributes will be retained and they will remain recipients of schedules.

1. In the **Settings > Users > Email-only tab**, locate the user you want to work with.
2. Click the <Icon icon="ellipsis-vertical" iconType="solid" /> in the same row as the user.
3. Click **Invite to Standard User**.

Omni will move the user to the **Standard** tab and display an <Badge color="gray">Invited</Badge> next to their display name.

### Deleting email-only users

<Warning>
  **Heads up!** Deleting an email-only user removes their email from all deliveries where they are a recipient.
</Warning>

1. In the **Settings > Users > Email-only tab**, locate the user you want to work with.
2. Click the <Icon icon="ellipsis-vertical" iconType="solid" /> in the same row as the user.
3. Click **Remove Scheduler User**.

### Assigning user attributes

You can assign [user attribute](/administration/users/attributes) values to email-only users. This is useful when you want to personalize the content of a delivery for each recipient using the **Personalize delivery with recipient user attributes** option in the [email delivery settings](/share/deliveries/email).

For example, you could assign a `region` attribute to each email-only user and deliver a dashboard that filters to only their region's data.

To assign user attribute values to an email-only user, refer to the [Assigning values to individual users](/administration/users/attributes#assigning-attributes-to-users) section of the **User attributes** guide.

## Email-only users and embedding

When using Omni in an [embedded context](/embed), the [`email` parameter](/embed/setup/url-parameters/email) associates an embed user with an email address — typically their known work email.

This association is important for email deliveries: if an embedded user adds their email as a delivery recipient and no existing Omni user has the same email address, Omni treats the embedded user as the recipient. This includes their [user attributes](/administration/users/attributes), which is especially useful when **Personalize delivery with recipient user attributes** is enabled.
