--- title: "Single Sign-On (SSO) Overview" slug: "single-sign-on-sso" description: "R365 SSO supports Okta and Microsoft Entra. Covers unique email requirements, login experience, welcome email settings, and user management." updated: 2026-04-22T20:57:55Z published: 2026-04-22T20:57:55Z canonical: "docs.restaurant365.com/single-sign-on-sso" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.restaurant365.com/llms.txt > Use this file to discover all available pages before exploring further. # Single Sign-On (SSO) Overview SSO (Single Sign-On) allows users to securely access systems with a single set of login credentials across multiple applications and services. Instead of managing separate usernames and passwords for each system, SSO centralizes authentication and improves security. Single Sign-On streamlines authentication by letting supported providers verify the identity of existing users, while Restaurant365 remains the system of record for user accounts and permissions. SSO does not create or manage Restaurant365 users; it works alongside existing user management to provide a secure sign-in experience. Once SSO has been enabled, connections can be made with [Okta](/doc/docs/okta-sso-integration) or [Microsoft Entra (Azure)](/doc/docs/microsoft-entra). The established connections can be viewed or [disconnected](/doc/docs/delete-sso-connection) from the [Single Sign-On page](/doc/docs/single-sign-on-page). ### Email Requirements for SSO Before Single Sign-On (SSO) can be enabled, all existing users must have unique email addresses. During SSO enablement, users with duplicate email addresses are identified and listed for [review](/doc/docs/enable-single-sign-on-wizard). After SSO is enabled, unique email addresses are enforced when creating or editing users. ### Login with SSO When connected, users have the option to [login](/doc/docs/log-in-to-r365) with SSO or by using their R365 instance credentials. ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-3299XNAG.png?sv=2026-02-06&spr=https&st=2026-11-10T17%3A09%3A56Z&se=2026-11-10T18%3A09%3A56Z&sr=c&sp=r&sig=xxrd3XRT58%2BnF%2Bx1m8xIUcvIbSd6qD2GuD05Dk5%2FBvU%3D) > If an SSO provider is configured but the connection is not established, the SSO option is not displayed on the R365 login screen. --- ## SSO Integrations ### Okta The Okta Single Sign-On (SSO) integration allows R365 to authenticate users through [Okta](https://www.okta.com/). When connected, users sign in to R365 using their Okta credentials instead of a separate R365 username and password. ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-RFIFOGXC.png?sv=2026-02-06&spr=https&st=2026-11-10T17%3A09%3A56Z&se=2026-11-10T18%3A09%3A56Z&sr=c&sp=r&sig=xxrd3XRT58%2BnF%2Bx1m8xIUcvIbSd6qD2GuD05Dk5%2FBvU%3D) ### Microsoft Entra (Azure) The Microsoft Entra (Azure) Single Sign-On integration allows R365 to authenticate users through [Microsoft Entra (Azure)](https://learn.microsoft.com/en-us/entra/fundamentals/what-is-entra). When connected, users sign in to R365 using their Microsoft Entra credentials instead of a separate R365 username and password. ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-W8ZDDNP5.png?sv=2026-02-06&spr=https&st=2026-11-10T17%3A09%3A56Z&se=2026-11-10T18%3A09%3A56Z&sr=c&sp=r&sig=xxrd3XRT58%2BnF%2Bx1m8xIUcvIbSd6qD2GuD05Dk5%2FBvU%3D) --- ## SSO Setup ### Enable SSO Single Sign-On (SSO) must be [enabled](/doc/docs/enable-sso) before a connection with an SSO provider can be configured. Single Sign-On is enabled from the [Single Sign-On page](/doc/docs/single-sign-on-page). > Before Single Sign-On (SSO) can be enabled, all R365 users must have **unique email addresses**. If duplicate email addresses are found, the users are listed for [review and resolution](/doc/docs/enable-single-sign-on-wizard). ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-729R23Z0.png?sv=2026-02-06&spr=https&st=2026-11-10T17%3A09%3A56Z&se=2026-11-10T18%3A09%3A56Z&sr=c&sp=r&sig=xxrd3XRT58%2BnF%2Bx1m8xIUcvIbSd6qD2GuD05Dk5%2FBvU%3D) ### R365 Welcome Emails The [**welcome email delivery setting**](/doc/docs/configure-welcome-email-delivery-for-new-users-sso) on the [Single Sign-On page](/doc/docs/single-sign-on-page) determines how initial login emails are handled for new users. By default, initial login emails are sent to all new users. This setting allows email delivery to be adjusted to align with Single Sign-On authentication workflows. > This setting controls how initial login details are communicated for new R365 users; it does not change how users are created in Restaurant365. > [!WARNING] > Suppressing welcome emails without configuring Single Sign-On (SSO) prevents newly created users from receiving login credentials or access instructions. ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-Y3EAQLV8.png?sv=2026-02-06&spr=https&st=2026-11-10T17%3A09%3A56Z&se=2026-11-10T18%3A09%3A56Z&sr=c&sp=r&sig=xxrd3XRT58%2BnF%2Bx1m8xIUcvIbSd6qD2GuD05Dk5%2FBvU%3D) > For [instances managed by one or more brands](/doc/docs/brand-managed-instances-overview), this setting may be controlled by the brand and displayed as read-only. > > > > **When brand enforcement is applied:** > > - An additional welcome email delivery section appears for each enforcing brand. > - Brand settings are read-only and reflect the value set at the corporate level. > - If multiple brand-level welcome email settings apply to a user, the system uses the setting that allows the greatest level of email delivery. > > The **Other users** setting applies to users who are not associated with a location linked to a brand that enforces welcome email delivery. ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-RV1E4WYC.png?sv=2026-02-06&spr=https&st=2026-11-10T17%3A09%3A56Z&se=2026-11-10T18%3A09%3A56Z&sr=c&sp=r&sig=xxrd3XRT58%2BnF%2Bx1m8xIUcvIbSd6qD2GuD05Dk5%2FBvU%3D) ### User Creation and SSO When Single Sign-On is enabled, team members authenticate using existing company credentials, simplifying the login experience across the organization. - Restaurant365 remains the system of record for users and permissions. Administrators create and manage users directly in Restaurant365, maintaining visibility and control over who can access the system and what they can do. - SSO streamlines authentication. Once a user exists in R365 and an SSO connection is configured, they can sign in using their SSO credentials instead of managing a separate R365 password. --- ## SSO Pages and Screens ### Single Sign-On Page The [Single Sign-On (SSO) page](/doc/docs/single-sign-on-page) displays available third-party SSO provider connections and their connection statuses. This page is where supported SSO provider integrations are managed. Before SSO is enabled, the page displays the option to [enable SSO](/doc/docs/enable-sso). From this page, users can: - [Enable SSO](/doc/docs/enable-sso) - Manage SSO connections for: - [Okta](/doc/docs/okta) - [Microsoft Entra (Azure)](/doc/docs/microsoft-entra) - [Configure when initial login emails are sent to new users](/doc/docs/configure-welcome-email-delivery-for-new-users-sso) - [Disconnect the SSO provider](/doc/docs/disconnect-sso-connection) ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-WY0GR6V8.png?sv=2026-02-06&spr=https&st=2026-11-10T17%3A09%3A56Z&se=2026-11-10T18%3A09%3A56Z&sr=c&sp=r&sig=xxrd3XRT58%2BnF%2Bx1m8xIUcvIbSd6qD2GuD05Dk5%2FBvU%3D) ### SSO Connection Screen The [SSO Connection screen](/doc/docs/single-sign-on-sso-connection-screen) contains the single sign-on integration settings for a third party SSO provider. This screen has a consistent layout across supported providers, including [Okta](/doc/docs/okta-sso-integration) and [Microsoft Entra (Azure)](/doc/docs/microsoft-entra-azure-configuration-page), with provider-specific fields where applicable. From this screen, users can: - View and configure the SSO provider connection - [Connect to Okta](/doc/docs/okta-sso-integration) - [Connect to Microsoft Entra (Azure)](/doc/docs/microsoft-entra) - [Disconnect the SSO provider](/doc/docs/disconnect-sso-connection) ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-5OG6MXAR.png?sv=2026-02-06&spr=https&st=2026-11-10T17%3A09%3A56Z&se=2026-11-10T18%3A09%3A56Z&sr=c&sp=r&sig=xxrd3XRT58%2BnF%2Bx1m8xIUcvIbSd6qD2GuD05Dk5%2FBvU%3D)