This article explains how admins with the Portal Manager role can configure a portal with User Eligibility as the authentication type. (To learn more about User Eligibility in general, go to the User Eligibility article.)

To configure a portal for user eligibility, go to the Settings section in the admin website. From there, select the Portal Management module and choose the portal you are configuring for user eligibility. From the portal management dashboard, navigate to the User Authentication section with the menu at the left-top of the page: 

Once in the User Authentication section, first select "subscriber validation" and then select the "Configure settings" link:

Overview

A user eligibility file is used to determine which of your users have access to your portal. The file must contain all users who are eligible to access the portal. Information in the files is used by your members to validate their eligibility to register for your portal. When a file is loaded, the users in the file are compared against existing user accounts in your portal:

• A member's portal account is disabled if they do not exist in the file 
• A member's portal account is enabled if they exist in the file (and were previously disabled)

Learn more about file specifications and formatting. 

Configure the Subscriber Validation Page

Select the Validation Fields to Use

The Engagement Rx system needs to be able to identify members before allowing them to register and enter the system. This is done through a process called "validation." Validation occurs when members go to the validation page and enter two pieces of personal data into predetermined fields. You get to decide which two pieces of data will validate members AND what the textbox will display to members so they understand what information to enter. 

Note: At least two fields must be mapped in order to enable the validation process, and not all fields are validation fields. To read about field mapping for user eligibility, see this article. See below for the list of validation fields you can use.

Here is an example of a completed validation field section where the fields were selected and the label to display differs from the system field names:

Validation fields

Validation fields are initially set as default to "Birthdate" and "Email," but you can set them as any two of the following options that appear in the drop-down:

• First name
• Last name
• Birthdate
• Email
• Phonenumber
• Keyfield (uniquely identifying ID like Employee number, for instance) 
• CustomField1
• CustomField2
• CustomField3
• CustomField4
• CustomField5

To view the full list of member attributes and details on values for each field, see this article. 

Note: It is advisable to use fields that are most likely to singularly identify each member.

Add a Custom Message to Your Users (Optional)

You have the option to apply a text communication and/or graphic to the validation page to assist your members in filling in the validation fields. In some circumstances, a validation field might require a piece of company-specific information (like a company ID number on an employee form or card). In a case like this, you might include a message and graphic that reminds the member where this information is located. 

Custom messages can be up to 1,000 characters long. Here is an example:

Add a Custom Image for Your Users (Optional)

In addition to a custom help message, you can add a graphic that appears on the validation page as well. Here is an example of a graphic that can work in conjunction with the message in guiding the member to the correct information:=

Add an image by clicking the "SELECT A NEW FILE" button. When it appears in the bounding box, simply use the slider to size the image so it fits within the confines in the white space. Then click "SAVE." File ouput dimensions are 500x250. Accepted file formats are .jpg and .png. 

You can change images using the "CHANGE IMAGE" button and repeating the process with a different image. 

Subscriber Validation Page Example

By setting up the validation page, you have determined what the users will see when they go to it. Here is an example of a validation page after customization: