portal

How to Define the Portal Settings:

1. Go to Edit > Preferences
2. Click on the “Portal Pages” tab
3. Enter the following settings:
   

   Login ‘Back’ Button Name	Enter the text that should appear on the ‘Back’ button on the first page. Note: Unless the ‘back’ button is inserted into the login page template, it will NOT appear.
   Login ‘Back’ Button URL	The web address that the user should be directed to when they click on the ‘back’ button on the login page.
   Login ‘Next’ Buttom Name	The text that should appear on the ‘Next’ Button on the login page. Note: By default, unless the ‘next’ button is inserted into the template, it will NOT appear.
   Login ‘Next’ Button URL	The web site that the user will be directed to if they click on the ‘Next’ Button. Note: This is NOT the button to login to the portal.
   Portal ‘Back’ Button	The text that will appear on the button on the Step 2 (user-information) page.
   Portal ‘Back’ Button URL	The URL of the login page.
   Portal ‘Next’ Button Name	The text on the button that directs the user out of the user-information screen.
   Portal ‘Next’ Button URL	The address of the web site that the user should be directed to when they leave the portal, e.g. step 1 of a connecting merchant account.
   Portal Step 1 Page ‘state’	The number of the M-level that may be connected to the portal login. For example, if the “next” button on the portal page should connect the user to an event registration, enter the M number. If it should go directly to the registrant page for an event, enter “step2direct”.
   Portal Step 1 Page ‘mid’	The number of the connected M-level.
   Portal Step 1 Page ‘eid’	If a specific event should be connected to this portal login, enter it’s ID number. This is especially important if the “next” button connects the user directly to that event’s registration form.

4. Click on  

Introduction

A portal allows your customers to log in to view and change their personal information. The administrator has the authority over which data can be viewed and changed. From the login, customers can linked to registrations in different M-levels (using Common Links). The portal is based out of the C-level.
Primary Keys

Each person from the M-level is identified uniquely to the C-level by matching any primary keys. For example, a camp collects a registrant’s healthcard number. The registrant’s profile is stored in the C-level. If the same registrant were to register the next year using the same healthcard number, a match between the new registration and the old registration in the C-level would occur. The new information will be added to the profile, so no new profile is created. This eliminates duplicates of people in the C-level. Some primary keys, such as email addresses, are default primary keys. The administrator of the C-level can define up to 5 custom primary keys, such as a student or employee number.
Pin Numbers

A pin number acts as the password for the portal log in. When a new registrant attempts to log into the portal, he can request that a new pin number be emailed to him. A new profile will be created for the registrant in the C-level. An administrator can manually enter or change a pin number for any profile. It is also possible to disable new registrants so that only registrants with an existing pin number can log in.
Portal Log In

In order to log in, a user must provide a primary key value (e.g. their email address or student number) and a pin number. If the pin number matches the pin number in the profile for that primary key value, they are allowed to continue. Otherwise they are presented with an error page.

Post Log In

When a users logs in, they see their own data that is stored in the C-level. Like in the C-level, the information can be displayed on different pages. To get from one page to another, they can click on different tabs. Each tab contains a screen displaying different fields of information. For example, clicking on the “Home” tab may displays the user’s address, home phone number, etc. Each tab must be defined by the C-level administrator. Three tabs are default: email, home, and business. These tabs can be disabled.

Once users are logged in, they can be directed to other pages to register for events within multiple M-levels. This is strength of the portal log-in as it can be used to allow only members of an organization access to online registration.