With a POPin enterprise subscription, your organization gets:

As such, you'll need to make some configuration decisions. This article should help you wrap your head around those details! (Please note: Your organization's IT department may also want to check our POPin IT Checklist.)

📌 Determine which domains should be associated with your POPin enterprise account

It’s important to gather all unique domains and subdomains your organization will use when signing in to POPin. This information will need to be delivered to our Client Success Team so we can add it to your account settings. Once your domains are in the system, your designated POPin Administrative Account Owner and Admins can see how the system has been configured in the Account Basics section of the Enterprise Dashboard Settings screen.

Please keep in mind: failure to include all subdomains used in your environment can result in users not being allowed:

Into restricted or private POPin sessions.
Enterprise account privileges, such as being granted an Admin or session Creator role.
System access beyond the 14-Day Free Trial status.

If your organization needs to add or remove domains throughout the life of your subscription, your Administrative Account Owner can work with our Client Success Team to update this account configuration.

📌 Determine who will be your Administrative Account Owner

Let's start here: What exactly is a POPin Administrative Account Owner (a.k.a Owner)? When you have this role, it means you are the primary point of contact for POPin administration within your organization. As such, whenever any POPin org-level settings need to be considered or applied for your organization, you’re the 'go-to' person!

With this role, you might want to use the POPin admin settings to:

Review Enterprise Dashboard analytics for insights on POPin usage within your organization.
Add Account Administrators—if you want to share POPin administration responsibilities with others in your organization.
Designate 'authorized' POPin session creators—if you want to limit POPin session creation to specific people based on their role or POPin on-boarding/training status.
Test POPin email delivery to ensure our system-generated messages get to your team members.
Establish how your organization will authenticate to POPin.

You'll need to contact our Client Success Team to have the initial POPin Owner designated in the system. Once we enter that name, your POPin Owner can transfer their role to someone else (if needed) ... without our help!

To build your understanding of this role, check out this FAQ article!

📌 Designate other POPin Administrators (if appropriate)

The designated Administrative Account Owner can establish if other people in your organization should share POPin admin duties. When people are granted the Admin role, they have the ability to manage the same org-level settings as your POPin Owner (see above list). There are, however, two exceptions:

Only the POPin Owner can transfer admin account ownership. (One person per organization.) This is done by transferring the role/privilege to another Admin via the Enterprise Dashboard Settings screen.
Only the Owner's email address will be shared with POPin users in your organization—in the event session creation is restricted and the system needs to notify someone that they don't have proper permissions.

📌 Restrict POPin session creation to authorized users (if appropriate)

There are two ways of thinking for managing POPin session Creators when you have an enterprise subscription:

Let anyone be a POPin Creator—the more the merrier!
Restrict session creation to certain people— such as to those that hold a certain role (e.g., C-Level, Director, Project Manager, Business Analyst or Change Manager) or to those that have completed POPin training.

If session creation should be restricted in your organization: Your designated POPin Administrative Account Owner and Admins can toggle the 'Restrict POPin creation to authorized users' setting on in the Enterprise Dashboard Settings screen. Then, add the email addresses for the individuals you wish to grant session Creation privileges.

In the event this restriction setting is turned on: POPin users will receive a system notification when they try to launch a POPin session but they are not a named authorized POPin Creator.

📌 Ensure POPin system generated emails and screens can be accessed in your organization's IT environment

In today's world of cybersecurity protection, it's good to be proactive by ensuring POPin email and screens can be accessed from your organization's network.

Please work with your IT department to 'safelist' the below domains in your proxies, firewalls, and email systems:

All subdomains of popinnow.com (*.popinnow.com)
popinnow.com
popin.it

You can refer to our IT Checklist for more details. Once this step is completed by your IT department, your designated Administrative Account Owner (or another named Administrator) can send tests through the Enterprise Dashboard Settings screen.

📌 Configure Single Sign-On (if applicable)

Your organization can sign on to POPin with a single click (and avoid security headaches) thanks to available single sign-on for SAML 2.0 standard IdPs. Specifically, single sign-on will let your POPin team members access the app using your organization's user database or identity provider system—rather than POPin managing separate passwords that have to be remembered.

SSO authentication for POPin can be enabled by your designated Administrative Account Owner (or another named Administrator) through the Enterprise Dashboard Settings screen.

We are product ready with most major SAML 2.0 providers including: Azure, Okta, One Login, Ping Identity, and ADFS.

Please refer to our How to Configure SAML 2.0 Single Sign-On (SSO) article if your organization wants to enable SSO.

Use the live Help chat to contact our Client Success Team if you'd like additional support on any of these topics.