How to Use a Registration Code for New Accounts

Registration codes are an excellent tool for providing learners with access to courses, subscriptions and learning paths. They enable you to distribute unique codes that can be redeemed up to a predefined limit of times.

If you're unfamiliar with registration codes or want to gain more insight into how they function, this article will guide you through the fundamentals.

Set Default Codes

When creating a new account, you can specify a registration code that will be used for all future transactions. This saves time and effort when setting up the new account.

To set this, navigate to either the Collect New Payment screen or Edit Customer page and check off the Set as default code box under Accounts. This will add your chosen credit card or bank account into the database, making it available on all subsequent transactions.

Registration codes on new accounts make it simpler to identify them when searching for payments or viewing payment records. They're especially helpful when you don't want to reenter all the information for a new account, such as when using the Collect New Payments application to collect funds from either new or existing customers.

You have two types of default codes you can set as your default: Index codes and Default Codes. Unlike Index codes, which can be assigned to any Fund Type and typically correspond with an Organization or Program code, a default Code is unique for each Fund Type.

When a user enters a Fund Code that has default Codes assigned into Banner, those fields will be filled with those assigned codes. Due to how State and ICR Funds are structured, you cannot establish default Codes for them.

You can set up Index codes for non-State and non-ICR funds at your request. These six digit codes are generated by University Accounting and Financial Reporting at a user's request and begin with the unit's three digit Organization code.

The user can then select an Index code and assign it to one or more Organization, Program, Activity or Location codes. These default codes can then be entered into Banner pages when creating transaction forms.

Users can restore all registered defaults for an application by associating its Start menu registration with its Default Programs registration. This action automatically returns the application to its default position in the Start menu if chosen as a default by that user.

The Collective uses the default or SAML default registration code if new users don’t specify one

SAML authentication is a security measure that permits users to access cloud resources with just one log-in. It helps protect applications from storing user credentials in their own databases, which could be vulnerable to hacking or theft.

Once logged into The Collective, users are presented with an application catalog displaying icons representing web-based applications and services they can access. Each icon represents a resource trusted by the portal.

Clicking an icon directs users to a specific application or service. That application or service then requests verification from the identity provider (IdP) that the person they are is who they say they are.

An Identity Provider (IDP) generates an XML document known as an assertion, which uniquely identifies each user and contains pertinent information about them. Additionally, this assertion includes authorization and attribute data which the IdP and SP have agreed to share for authentication purposes.

Bob, for instance, may need his first and last names included in an assertion to help identify him; thus, he will be required to supply those details during registration.

In the sign-on process, the IdP sends an assertion to the SP which matches it against user attributes in its database. If this match is successful, then Bob can access desired applications or services.

If the match is unsuccessful, the SP will send an error message to the IDP that outlines why and how it was made. This may involve removing the incorrect assertion from user's directory and reencoding it with correct attributes.

In some instances, an IdP may require the SP to supply additional attribute data, such as a department or job title. In these instances, they will specify the attribute name and name format they desire the SP to utilize.

Configuring your organization to support SSO requires having members registered under organization-specific email aliases. Doing this ensures they can login to Figma even if their company's email address isn't linked with an existing account in the Collective.

There’s not at least one

Registration codes are an ideal way to grant multiple users access to the same content item or subscription. For instance, you could give a math coach a one-time use code so they can redeem their own copy of the best math curriculum available. But it is essential that these codes are redeemed and used appropriately through labels and other administrative controls. A well-designed labeling system will guarantee smooth roll out of your latest innovation - you can learn more about this in our helpful guide on labels for the Thrive Health community.

Set a custom code

Custom codes are code snippets you can embed into your site's pages to verify ownership, monitor traffic and monitor user activity. You have the freedom to add them to all pages or just specific ones. Moreover, you have the option of loading them only once per visitor or on each page they open.

To add a code snippet, go to Elementor > Custom Code. Paste the desired snippet into the text box and choose where you would like it displayed on your site. You have two options: save as a draft or publish.

Your custom code can also include a property, which will allow your visitors to display information. With one single code, you have the capacity to include up to 50 properties.

Once your custom code is ready, test it to confirm its functionality. To do so, click the Test action button located at the bottom right sidebar.

When testing your code, you can select a record to compare it against. Alternatively, you may use previously formatted property values in your workflow to test the code against them.

Once your code has been tested, you can edit it and delete any unnecessary properties. Additionally, you can adjust the scope of your custom code so it excludes any properties already covered by another custom code with the same name; this is useful if you have multiple codes with identical names that must ensure their scopes do not overlap.