# How do I enable employees to access multiple Persona organizations configured with Okta single sign-on?

> Let an employee log in to multiple Persona organizations using Okta SSO by setting a custom Application username, like alex+secondacme@domain.com.

Source: https://help.withpersona.com/articles/3PtQ5iKfJFj7JUR7wPFD3v/
Section: Admin > Single sign-on (SSO) and Authentication > FAQ

This question came from a member of the Persona community, a team manager who was trying to configure use of Persona for their employees. This is useful for those who want to understand how to manage Okta single sign-on for multiple Persona instances with the same set of users or employees.

## Question

How do I enable employees to access multiple Persona organizations configured with Okta single sign-on?

## Answer

Thank you for your question, we can definitely help with this one. As a prerequisite, you'll need to have [Okta single sign-on enabled](/articles/3A0ZoW5ozu1k17n7bOrVuE/ 'SAML-based single sign-on (SSO) with Okta for Persona Dashboard') for both (or all, if more than two) of the Persona organizations/instances that you'd like to configure access for.

**Example setup**

- In the following setup instructions, we’ll be using the following references
  - Email: [alex@domain.com](mailto:alex@domain.com)
  - Persona Organization One: First Acme Fintech
  - Persona Organization Two: Second Acme Fintech

With this setup, user with the email [alex@domain.com](mailto:alex@domain.com) can log into two Persona Orgs using the following:

| Organization Name           | Login Email                |
| --------------------------- | -------------------------- |
| First Persona Organization  | alex@domain.com            |
| Second Persona Organization | alex+secondacme@domain.com |

### Configure Application username

1.  Using your Okta admin account, navigate to the **Applications** section of the email’s Okta account
2.  With the prerequisites, you should have an application called, Second Persona Application set up with SSO, click on the **Second Persona Application > General**
3.  Under the **SAML Settings**, click on **Edit** to modify the configuration
4.  Click **Next** to land on the **Configuration SAML** section
5.  Modify the **Application username** to Custom

    |                      | Existing | New    |
    | -------------------- | -------- | ------ |
    | Application username | Email    | Custom |

6.  Enter a custom rule field use the following expression
    - `String.replace(user.login, "@{company_domain}.com", "+{desired_string}@{company_domain}.com")`
    - e.g. from setup: `String.replace(user.login, "@domain.com", "+secondacme@domain.com")`
7.  Navigate to **Attribute Statements**, update `user_email` to the following:

    | Name         | Name format | Value                                                                                          |
    | ------------ | ----------- | ---------------------------------------------------------------------------------------------- |
    | `user_email` | Unspecified | `String.replace(user.email, "@{company_domain}.com", "{desired_string}@{company_domain}.com")` |

8.  Save the updated changes.
9.  To finish the provisioning Alex (the employee or user who you are setting this up for) he needs to perform the following
    - Option 1 — Login to the respective Persona Org via Okta Tiles
    - Option 2 — Login to both Persona Orgs using the Persona Organization Slug at least once
10. You are done, Alex can now use either email to log in to their desired Persona Organization.

ℹ️

This does not impact the Okta username that the end user uses to log into their Okta
Dashboard, nor does it impact the email address in other downstream applications tied to Okta.

This answer was reviewed by Justin Sayarath, a product manager at Persona. FAQs, unlike other articles, are written to provide Persona Community members more specific answers to common questions. While we periodically review responses and answers, please note when this FAQ was last updated as information may have changed since then.

_Last updated on July 29, 2025._