Regpack

Current Page Help FAQ

Each page within Regpack, except within "Email Editor", provides an explanation on the functionality available to use and how to use it. The way this current page FAQ works is depending on where you are within the system, the FAQ changes relative to that page or module.

Navigating to Product Management changes the FAQ to Product Management related FAQ, for example.

The FAQ exists below the "Settings" button on the left-hand navigation. Clicking any of the prompts will send you to a page that explains how to perform each action displayed to improve productivity and reduce time spent performing an action.

Changes to Navigation

With the addition of the Current Page FAQ, the Icon for "Help & Support" is no longer the Question(?) mark and has been made "Support" with a conversation icon.

Sub-unit Login Improvements[Released]

Overview:

The recent updates to the sub-unit login system on the frontend aim to streamline its functionality while expanding email usage flexibility.

Key Changes:

Example of Changes:

Organizer can register using [email protected] and create additional sub-units with the same email [email protected] and the additional sub-units can use their own email. The only restriction is that the emails used have to be a valid email.

For detailed information about sub-unit login, refer to: Sub-unit Individual Login

Enabling Sub-unit with existing accounts

If sub-units have already been created and you would like to use sub-unit login, first make sure you enable the sub-unit login toggle within Project Settings and check that the sub-unit level form has an email field to use.

On the frontend the user can click "Go to next step" on the form that has the sub-unit email. Ideally this would be the first form within the sub-unit's form list, especially when used with child login trigger.

On the backend, you can click the form with the email field and while in their form, click "Save form".

Bulk Edit[Pending Release]

Selecting Multiple products now displays the ability to perform bulk actions for the following:

Bulk Edit allows you to make changes to multiple products and product types(Merchandise, events, sessions, discounts and subscriptions; discounts and subscriptions pending) with much less steps. This also includes moving multiple products into another category.

Session holder may also be changed with bulk edit through the same method of clicking one or more session holder and clicking edit.

If the system detects the same values it will allow those values to be edited by default, otherwise the system will gray out the option and require you to verify that you want to edit those specific values(names, start/end dates, etc) by clicking “Edit” by the section you want to make changes to.

Bulk Edit will also allow for Options tab in sessions to also be editable, which includes user visibility, admin assignment, description, etc.

Restrictions for Bulk Edit

Bulk edit cannot be performed on products with orders in order to prevent changes that would affect users that have already ordered an existing product.

Bulk edit can only be used on products of the same type. If changes need to be made to multiple products they have to be for example all sessions, merchandise, events, discounts or subscriptions. It cannot be a combination of each.

When making bulk edit on sessions, the selections made have to be of the same level.

Orders will NOT be displayed when bulk editing sessions. This also includes abandoned products(currently allowed, may change to prevent).

Additional Notes on Bulk Edit:

When choosing multiple sessions for bulk editing, the preset shown will be based on the session with the most settings. For instance, if one session is set for Monday, Wednesday, and Friday, and others for Monday and Tuesday, the default will include Monday, Wednesday, and Friday.

When re-enabling editing by clicking 'edit', the displayed default will apply to all currently selected sessions upon clicking 'Update X Sessions.'

The bulk edit operates using a point system, assigning a point for each setting change. Even if the default product is displayed, changes can still be made by clicking 'edit' if the option appears grayed out.

Bulk Edit on the session holder level will NOT display the sessions list.

Auto-Session Generation

When creating sessions, you will be presented with an option to specify how you would like to create sessions. The way this works is based on the Start and End date of the session. If you select a single session it will create the original session type with the date range.

If you select any other option beside the "Create a single session", you will be presented with a preview based on the date range and still have the option to create a single session if you decide not to create multiple sessions.

Bulk Copy

Clicking into a product displays an additional button beside “Delete Product”, called “Copy Product” within the "Settings" tab of the product. When the copy product button is clicked on, it will prompt the user for the number of copies they would like to create.

Creating a bulk copy performs a copy of the settings that are set after a product has been updated.

Bulk Copy can currently be used on the following product types:

Additional Notes

In order to use Bulk Copy, the product has to already be created before the option appears because you are making a copy of something that is currently existing. Copies of a product that have an order can be copied, but the order will NOT copy over.

When using Bulk Copy on Sessions, the copy product button only displays within the sessions within the session holder.

Triggers on products are not copied by default. Triggers can be added through bulk triggering if needed.

If changes have been made, the product has to be updated before performing bulk copy in order to keep those settings on the bulk copies or you will receive an error message:

Bulk Delete Products

This new feature allows you to delete one or more products that do NOT have orders attached to it.

In Product Management select a product you would like to delete by checking the box adjacent to the product.

After selecting the product(s) you would like to delete, the "Delete" button appears at the top. By clicking "Delete" you will see a confirmation window to delete the selected product(s). If you have a combination of a product with and without an order you will see the following warning message to confirm:

Important Note:

Products that are deleted cannot be restored.

If you attempt to delete products with orders it will display an error and no action will be taken. Attempting to delete a parent product that has child sessions with orders will also prevent deletion.

Products:

Product triggered to show based on other products not showing when users change their product selection. 103183554_100910493, 103232458_100910493, 103236383_100910493, 103561707_100910493.

Emails:

Able to create user account with the following emails. 103662184_100910493, 103667011_100910493, 103669107_100910493.

Installment Plan Presentation

When a user reaches the checkout page on the frontend, the user will immediately see installment plans without having to click any other options IF installment options are enabled for the system plans and autobill is enabled.

If installment plans or autobill are not enabled it will display as it normally does.

Slight changes to the navigation bar on Desktop:

Before:

After:

Improvements to Mobile Appearance

Frontend:

Valid password recovery URL sent to end users. 103639277_100910493, 103651590_100910493, 103663339_100910493, 103667368_100910493, 103668237_100910493, 103667882_100910493, 103669832_100910493, 103671721_10091010493, 103671591_100910493, 103673748_100910493.

User management:

Option to view orders through tools on UM working. 103531874_100910493, 103452335_100910493, 103375999_100910493.

Positive valued filter not picking up abandoned carts. 103680137_100910493, 103533952_100910493.

Account Merging

Logging into a user that had an account previously created ports the users over and merges that information based on the email used it updates those specific users.

If you try to use an existing parent email within the same project, an error message displays. The message also displays if the email is already used for a sub account. If there is another email on the sub-unit it uses that as a fall back.

Sub-unit Individual Login

When a sub-unit from a group system registers when "Allow sub accounts to login on their own" is toggled to on from within Project Settings, the user is able to login to view and pay for ONLY their information.

Note that the sub-unit login setting only works with group systems where there is a head-level and sub-unit level.

Google sign-on

During the account setup for the sub-unit, authenticating through Google via Google Sign on allows you to bypass security token authentication on sub-unit login.

Sub-unit multiple emails

When a sub-unit account has forms with multiple email fields, the field that is mapped to "main_email" will be the email field that is prioritized and used for the sub-unit account. If that email does not work, it will use one of the other email fields as a fallback.

Sub-unit account creation flow

Creating a seamless experience for Organizers is further simplified by introducing Child Login trigger. The Child Login trigger is an event that happens after the sub-unit logs in through the account setup link that is sent out when the sub-unit is created while Allow for sub-unit login is enabled.

When a form has the trigger for child login on a child-level form, what you will notice is that the child does NOT have forms outside of the basic information form used to create the sub-unit account/child account. Once the sub-unit logs in, the forms are then added so that they can complete that information on their own.

This also allows for the following functionality to happen:

When the organizer is creating the sub-unit accounts for multiple people, it will flow from sub-unit account to sub-unit account without having to navigate back to the dashboard.

Enabling Sub-unit login

Allowing sub-units to register and login can be found in Project Settings > Registration within the sub-heading "Sub Account (children) Settings" under "Allow sub accounts to login on their own". By default this setting is set to "OFF".

Once the setting has been toggled, the last step is to add an "email" field to the sub-unit level form in order for them to be able to receive a login link.

Information Isolation

In order to keep each individual users payments , payment plans and information private and secure, we isolate the information for those sub-units who access the system.

Accessing the dashboard while logged in as a sub-unit allows for streamlined management of the following exclusive features:

Sub-unit Login Process

Head-level registrant registers the account and continues to the sub-unit level form with the email field. When this email field has had the correct sub-unit's email and submitted. The next form that appears will notify the registrant that the sub-unit has account enabled and an email has been sent out to allow them to login.

The sub-unit clicks the button or copies the URL to access the system for ONLY their account. They will be prompted to input a security token so that if anyone else had the URL they would not be able to access their information.

Once the user has been verified via security token the user will be able to continue through their own registration based on their isolated information from the rest of the sub-units or head-level.

Note that there is a 10 minute delay before the email is sent out to the sub-units, so that if there are multiple sub-units created it will give time for the system to batch those emails to send for each sub-unit within that 10 minute time span.

Sub-units after having enabled the sub-unit login will be able to use login and forgot password through the normal flow.

Backend Sub-unit Charging

Sub-units can be charged in advance by the admin. When charged in advance, the system will charge the sub-unit using ONLY their payment method and autobilling plan. If the sub-unit does not have a saved payment method and an attempt to process is made, the admin is presented with the screen to add a payment method.

User Management:

Super admin owner able to purge in bulk. 103612669_100910493, 103612671_100910493.

Payments:

Bluesnap account changing to approved.

Products:

Sub- units can add products to their cart. 103625849_100910493, 103629478_100910493, 103629453_100910493, 103629304_100910493, 103629245_100910493, 103629232_100910493, 103629216_100910493, 103629043_100910493, 103629067_100910493, 103629072_100910493, 103629128_100910493, 103629138_100910493

Payments:

Triggers:

Email:

Payments

Bulk User Purge Tool

Required permission level to use tool - Super Admin Owner/RP Dev

To purge a user/users first select which user you would like to completely remove information for. Please note that if you do decide to purge a user, their information will be permanently deleted and this action is irreversible.

Once the user(s) are selected, click Tools within User Management > Purge all user information under "Forms". Once clicked on it will prompt you with a warning explaining the actions that will take place once you have entered your password and security token.

After both the password and token have been inputted, the system will begin to purge all the user information. This includes their information, payment details and login.

If you select a head-level user within a family system, it will also select all child units within that family to purge.

Product/payment information will also be deleted and recalculated for both User Management/Payments/Org totals.

Users purged will also not be able to be searched for after purge.

Users marked as inactive that are selected can also be purged.

Payment & Autobill Notification email frequency

Admin Management now allows you to adjust the frequency of the emails from your admin profile via the Notifications tab.

Note that the Notifications tab only appears for admins with access to financial information.

Payment Email Frequency Options

Daily, Weekly, Weekly/Monthly, Monthly, Never

Autobill Expected Charge Frequency Options

Daily, Never

Payment emails

Payment email reports of your project can be sent on a chosen frequency. By default emails will be sent Weekly/Monthly that was processed to give you an idea on the stats behind your project. Note that if you are in a different project currently, the system will automatically move you to the correct project.

The emails for payment statistics will display a green background and the emails for autobill statistics will be in a blue background

The information visible will be based on:

Each statistic listed will allow you to "view" where that information is coming from by moving you to your project and filtering for that specific criteria.

Payment statistics

Below main information in the email sent out will be statistics on the percentage of users who still need to close their balance and how much of it is secured, or on autobilling.

The statistics are listed as follows:

Email

Projects

Autobill Upcoming charges

An email will be sent out every 24 hours displaying the autobill information on upcoming charges for the next day on all projects that have active autobilling. The autobilling email will provide you with statistics and quick links to navigate to the project specifically mentioned in the email. This email will only be sent out and/or accessible by Super Admins/Financial Admins.



Project access request

With the implementation of the autobilling emails, we have also added the ability to request project access for the project mentioned in the email. You will notice there are buttons with the label "View" in the email. When any of these buttons are clicked, you will be prompted to login, if you are not logged in already and sent to the specific project these autobilling details relate to. If the admin does NOT currently have access to this project and obtains a link from another admin to view the information, they will submit a request to the Owner of the Organization.

Requesting access to a project within the organization will send an email to the owner asking if they would like to "Grant access" to "X" project. The owner can choose whether to grant it or ignore it. If the admin grants the access, the project will be added to the list of projects for the admin who requested access.

When the admin requesting access attempts to use the shared link again, they will be redirected to the project for which they have been granted access, if granted.

Important note on Project access request

We take security seriously and will only allow users within the same Organization to request access. The request email will be sent from our [email protected] domain email.

They also will not be able to request access if they have been given a link to view the project with that filtered search query. If someone attempts to request access outside of the Organization, they will automatically receive an error.

Additional Autobill control with Payment Pause/Resume

Regular admins will have the ability to control which users they do not want to charge by navigating to User Management > Autobill of user. While in the autobill tab of a user, select "Pause auto-payments". A warning will be displayed to the admin with what will happen and all of the autobill will display "Paused" for each payment date in Autobill.

Since admins will be able to pause, we also allowed for the ability to resume payments as well. We allowed for filtering for users with a paused autobill in order to make this process easier.

Filtering for Paused users

User Management select the search, Payments and Autobill > Autobill > Autobill Payments Paused. Here you will see a filtered user list of users that have payments paused in Autobill. In order to resume payments, near the bottom of Autobill tab for the user, select "Resume Auto-charging payments"

Note: By pausing autobill for a user you are understanding that autobill will not be run on these users until autobill is resumed for the user(s).

Updated Autobill control for Financial/Super Admin

Super Admin and Financial admins are now able to "Edit Start date" for Autobilling plans. This option can be found by selecting a user in User Management and opening their autobill tab.

Form field (?) hover fixed

Hovering over form field that has a (?) will now correctly allow the user to hover over the question mark in order to view the use of that specified field.

User information now ports child basic information forms from the backend

If a user copies a project and wants to port a users information into the new project, this will now allow the admin to port the basic information on the backend for both the head/child unit from the backend.

The forms will populate with the users information after creating a new user with the previously existing email address. Previously this was only porting the child user if the user on the front-end ported the information themselves by logging in.

Note on porting information as an Admin:

When an admin ports information by creating a user on the backend, the forms that were completed by the user are now marked as completed.

Purchase Protection

Front-end

Projects

Triggers

Admin management

Products

Payments

User management

Device recognition re-added

We have re-added device recognition in order to make logging in to the same device easier. Note that constantly changing devices will lead to an increased time between security token emails in order to to make sure that security for your account is maintained.

Autobilling installments in RP Billing

Admins/Organization owners will now be able to split the payments for licenses into smaller payments using Autobill. As long as a payment has been made fulfilling the Autobilling plan to the license, access will be granted.

Number of Installments shown by user balance in User Management

When a user has been assigned an Autobilling plan, the number of installments displays by the users total balance. This displays on wherever the Autobilling has been assigned(Both on Child/Head-level units if there is a cart and Autobilling plan attached to that specific user)

The User Interface for the installments is shown in varying colors according to the following:

Update to Payment Snapshot to improve accuracy

Emails

Autobill

Discounts

Forms

Projects

Products

Admin access

Condensed Update Notes

Automated Autobilling updates

System generated autobilling plans are no longer editable in order to keep the installment options simple for the end user to understand and select. The system generated autobilling plans are also hidden from the "Payment options" form to simplify the checkout process for the user making the payment as the option is now displayed when making a payment.

Selecting an autobill option when making a payment for an individual user now adds that selected autobilling plan to all users in that family. The idea is to keep everyone on a consistent payment structure while also limiting the number of actions the user has to take. This also means that newly created children under an existing family now also has the previously selected autobilling plan added to them. The user also has the option to pay in full or pay based on the installment plan chosen.

Removing autobilling plans can now be done within the Autobill tab of the user selected without requiring the admin to "Edit Autobill plan" and remove it from that window, although the option still exists.

Note that Installment plan options ONLY appear when it is larger than $50 and the end of the date program has not yet passed on the last installment.

Conditions for Autobilling Installments to appear

In order to ensure autobilling installment options appear for users make sure:

Autobilling Installment selection on Checkout

On the checkout form with autobilling installments on checkout enabled, the "Pay $X Amount now" and "Pay as little as.." options when selected display the installment options available for the user to select. It's important to note that the number of installments available depending on the date range of the products start/end date and the cost of the product. The autobilling installments range from 3, 6, 9 and 12 installments.

Autobilling updates

From the autobilling page, the autobill can be disabled/enabled. When disabled, the autobill does not display for either the admin/user on the front end until re-enabled. Users that are currently on that autobilling plan, will remain on it until they have completed all the payments. If the plan is removed by accident after disabling, the plan will need to be re-enabled in order to re-add it to the specific user(s).

Updates to Project Settings for the new Autobilling options

An additional heading is now available to make the new autobilling options more organized. This will be displayed under Project Settings > Payments as "Autobill And Revenue Security". The options listed display the toggles for enabling Autobilling payments, securing revenue by offering Installments on checkout and Limit the number of installments offered to the first completion date of the program.

Enable Autobill payments - This option allows for autobilling to work in the project.

Automatically secure revenue by offering installments on checkout - Allows for installment options to be presented when the user is checking out on the front end.

Limit the number of installments offered to the first completion date of the program - When enabled, this setting will offer installment options based on the program the user selected.

Payment submission enhancement

Now when users make a successful payment, a confetti animations appears congratulating them for making a payment.

Autobilling/Payment Snapshot stored states

Expanding or minimizing either the Autobilling or Payment Snapshots will now be remembered by the system when moving around in Regpack.

Text changes

Payments

Autobill Snapshot

Autobill now has a quick snapshot of information that will allow you to easily view metrics for your project that has users with autobill. These metrics can also be interacted with to view points of interest. One example of this is users with overdue payments. When you click the overdue section it will take you to User Management and filter for those specific users.

What can you expect to see on Autobill Snapshot?

Within this quick view you will be able to see:

Overdue Payments

Users with overdue payments that includes the total amount that is overdue, the amount of users with overdue payments and the latest overdue payment.

Next Upcoming payment

This will display how much money that you can expect based on users on Autobill. This includes a breakdown of the amount of users and payments.

Projections

The projections are different timeframes and the amount of money expected

Overall Future payments

The overall future payments includes every single payment expected from all the users on an autobill plan and when the latest date of payment is.

Bug fix for payment related filters

Filters for Close balance, Paid in Full, On Autobill, Not on Autobill, needs to be refunded, paid something, paid nothing, has payment method, has no payment method now display the correct information.

Products

This tool was created in order to make managing a user's information easier. Selecting a user and navigating to the "info" tab of the user allows admins to delete all information permanently pertaining to that user. If the purge button is used from the head-level of a group, this will delete all information pertaining to the group that was selected.

Note that selecting users and then using purge on one user will only result in the user who was selected to get purged from the system. To remove a group, the head-level account has to be selected, then in the "info" tab the purge option selected and confirmed.

Important Note

User information that is purged cannot be retrieved. A confirmation window is displayed which requires a password input to perform the action. Purging a user requires Super Admin level access.

Instead of having to select the more commonly used filter from the search bar, we have added Quick Filter options to click. Each filter is separated by their functionality.

Quick Filter Default behavior

Quick filters will display all filters by default, if the caret pointing down is clicked it will minimize the Quick Filter display through out the projects. This can be turned back on by selecting "Show quick filters" on the right hand-side where it was initially minimized. Your preference will be stored for displaying the quick filter minimized or expanded through either the Payments or User Management pages.

Info pop-up on Filter

Toggling between different accounts, such as the head-level or child-level displays text on why the numbers or users displayed may be different. For example, if viewing the application date of "last month", only specific accounts that satisfying the filter condition will be shown. The overall result will be displayed on the child-level account.

Filter Link Sharing

When you or another admin apply a filter from User Management or Payments, you will now see a URL that displays at the top of the page. If you want to share a specific filtered view with someone else within your Organization you can send them the link while they are logged in to view that same filter!

Filter Link Usage

Filters can be used across any project within your organization, but filters with specific products that do not exist across projects will NOT display.

Filter results

If a filter contains no results, a description of why there are no results will display to make it more clear.

Filter restrictions

These are restrictions which are made to prevent usage that would not make sense to use in combination.

Paid in full will not stack with:

Needs to close balance

Needs to close balance will not stack with:

On Autobill will not stack with:

Not on Autobill will not stack with:

Cart is empty will not stack with: anything.

User management

Products

Help button is now labelled as Help & Support. In order to make it easier for admins to communicate with our support team we have changed how support is contacted from within Regpack. Instead of "Try Another way", the form to contact support now opens below the "Find Answers" section.

Purchase protection has been updated to allow for users or admins to add purchase protection to all users using a single click of "protect my order" at the bottom of the checkout page/form when purchase protection is opt-in.

Purchase protection can also be individually added/removed to each user for a family payment by selecting remove plan/add plan depending on the project settings.



Emails

Payments

Admin management

User management