Skip to content
Help Center

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

View Markdown Contact support Contact support 2 min read
On this page

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 help with this one. As a prerequisite, you must have Okta single sign-on enabled for each Persona organization/instance that you want to configure access for.

Example setup

  • These setup instructions use these references:
    • Email: alex@domain.com
    • Persona Organization One: First Acme Fintech
    • Persona Organization Two: Second Acme Fintech

With this setup, the user with the email alex@domain.com can log in to two Persona Orgs with these emails:

Organization NameLogin Email
First Persona Organizationalex@domain.com
Second Persona Organizationalex+secondacme@domain.com

Configure Application username

  1. With your Okta admin account, go to the Applications section of the Okta account of the email.

  2. Because of the prerequisites, you should have an application with the name Second Persona Application that is set up with SSO. Click Second Persona Application > General.

  3. Under the SAML Settings, click Edit to change the configuration.

  4. Click Next to go to the Configuration SAML section.

  5. Change the Application username to Custom.

    ExistingNew
    Application usernameEmailCustom
  6. In the custom rule field, enter this expression:

    • String.replace(user.login, "@{company_domain}.com", "+{desired_string}@{company_domain}.com")
    • For example, from the setup: String.replace(user.login, "@domain.com", "+secondacme@domain.com")
  7. Go to Attribute Statements. Update user_email to this value:

    NameName formatValue
    user_emailUnspecifiedString.replace(user.email, "@{company_domain}.com", "{desired_string}@{company_domain}.com")
  8. Save the updated changes.

  9. To complete the provisioning, Alex (the employee or user that you set this up for) must do one of these options:

    • Option 1 — Log in to each Persona Org through Okta Tiles.
    • Option 2 — Log in to the two Persona Orgs with the Persona Organization Slug at least one time.
  10. The setup is complete. Alex can now use each email to log in to the applicable Persona Organization.

This does not change the Okta username that the end user uses to log in to their Okta Dashboard. It also does not change the email address in other downstream applications that are connected 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 .

Was this page helpful?If something is missing, let us know and we will take a look.
Thanks for the feedback. It helps us improve these docs.