Arena offers several options for members to access the member pages of your external Arena website. Each option has certain trade-offs. The two primary trade-offs are security versus ease of use. If your organization currently uses Shelby WebView, make a plan to establish new logins and access to your Arena-managed website features.
Administrator creates logins by automated process
Distribute logins to members via email
Logins are assigned to existing records
Logins share specific login format
Member-Requested Logins HTML Email Form
Members request specific login via email
Designated person receives an email for each request
Members create their own logins
Logins are assigned to new records
Logins are known only by the user
Optional email verification
Administrator must manage possible duplicate records
Option to add registered users to a Tag for ease of managing users. This Tag can be synced with a security role.
Option to set default campus for multi-campus organizations
Option to set default Member Status
Option to send email verification to confirm new user is not a robot
Regardless of the login option you select for your organization, the All Users security role must be able to view your Member Login page, as all visitors count as members of the All Users security role until they have passed through the Login page. It is also important to give view rights to the Login page to every security role with any permissions on this page tree, as certain modules may attempt to re-verify the identity of a user by passing their login and password to the Login page.
Evaluate your process for managing duplicate records that are generated as new users access the member pages of your Arena-managed website. Be sure to factor in the available module settings for each login option that helps minimize and manage duplicate records. Duplicate records are unavoidable and being able to merge records in a timely manner ensures your member have proper access.
In addition to customizing the Member Login pages, use the below checklist to configure Member Login:
Start the Sync Role Agent, if you are synchronizing a tag of web users with a security role.
Customize the Login Request, New User | Email Verification, Password Request and User Confirmation Notification System Emails.
Once you determine the member login option for your organization, you are ready to customize the required pages and modules. There are four required pages and one optional page you need to review and customize as needed.
The page requires the User Login module. Set the Allow Remember module setting to true to display the Remember Me check box. Set the Create Account Page to the page to redirect users to login. Set the Redirect page to the page to direct users to after logging in. Set Send Account Info page to the page for users to request login credentials.
New Login Request
This page requires a new user module.
Implement Pre-Generate Logins
When the Sync Role Agent runs, Arena applies the security role permissions to the records in the specified Tag and email the new user. If a user is an existing user, the email includes the user name. If the user is new, Arena creates one based on first name initial and last name (BJones) and create a random password. The user is required to reset the password at first login.
•Start the SyncRole agent.
•Add records to a Ministry Tag.
•Customize a security role.
•Click the Notify New Member check box.
•Enter a subject.
•Complete the email message. Be sure to add the [login_information] merge field to the security role message.
•Sync the tag with the security role.
Implement the Member-Requested Logins HTML Email Form
•Add the HTML Email Form module to the New Login Request page.
•Customize this module
•Add an email to the Email From module setting.
•Add a name to the From Name module setting.
•Enter instructions in the respective module setting.
•Enter a redirect URL to direct prospective users to once they complete the HTML form.
•Enter an Email Address in the Recipient module setting.
•Enter a Subject for the email in the Subject module setting.
•Start the SyncRole agent.
•Customize the New User Account | Email Verification System Email, if using the email verification option.
Implement Member-Created Logins
Use this option to allow new users to create logins and immediately access member pages. If the email address the new user enters already exists, the user is redirected to the Request Information page to have login credentials sent to the existing email address. Arena attempts to match existing records by last name, first name, birth date and email address. (This option can create duplicates so use the registered users Tag to identify and manage duplicates.)
•Create a Ministry Tag to which Arena adds new registered users.
•Add the New Account Request module to the New Login Request page.
•Set default Campus, if applicable for your organization.
•Set the default Member Status. Consider creating a List for this member status to manage duplicate records.
•Select the optional Email Verification if your organization uses the email option for new users to verify they are not a robot.
•Select a Profile ID Tag to add the new users. This is also a tool to manage registered users and duplicate records. Consider synchronizing this tag with a Security Role that gives the new registered users the desired permission.
•Set the redirect page.
•Set the Request Login Info Page for new registered users whom already have a login.
•Select the Source ID Tag Status for new registered users. Users can use this parameter in conjunction with the Tag and Member Status to manage potential duplicate records and registered users.
•Select the Status ID Tag Status for new registered users added to the Tag.
•Customize a Security Role for users and add the above referenced Tag to the Security Role.
•Customize the New User Account | Email Verification System Email, if using the email verification option. The optional Email Verification page requires the Verify New User Account. If using this option, you also need to set Email Verification to "True" and the New User Verification page on the New Account Request module, and customize the New User Account | Email Verification System Email. Be sure to include the ##VerificationURL## merge field code in the System Email so that users can be directed to the correct page for verification. The verification URL link is valid for five days.
New Account Request Matches an existing record
When a current user completes the New Account Request form and the email address matches an existing record, the below message displays to email the credentials to the existing record.
The Request Information page requires the Request Login Information module to allow users to have their login information sent to their email address if they forget it.