Welcome to the Practus Onboarding System (“LMS”) Admin Guide. Below we will outline the step-by-step processes that occur on the front- and back-end of the system, as well as linked technologies and responsible parties to reach out to for support.
Site is managed by Matt Adams and Valerie Spengler.
User Management
Users register for a login on this page. The password is Join@Practus!
Once registered, the system will send them a confirmation email required to login for the first time. The user may need to check their Junk folder.
Note: Only Module 1 will be available to new users. Module 2 & 3 will unlock once the Partnership Agreement is signed by both the Partner as well as by Practus. More on that below.
When a user is created on the Gravity Forms Registration Form, a Deal will be created in the Hubspot Onboarding Pipeline and assigned to Tracey Watson, using a Hubspot Workflow. These are all stored in an “Onboarding Workflows” folder for ease of access.
Module Access
Module access is managed by User Groups. There are two group categories – candidate or non-candidate (ie, “Partner Candidate” or “Partner”). The user category is determined by whether the individual has signed their Partnership Agreement or Employment Letter at the end of Module 1. Module 1 is the only module available to a “candidate” user type.
Once the appropriate agreement is signed in Docusign, this Hubspot Workflow moves the deal into the appropriate deal stage. Hubspot then triggers Zapier to then add them to the non-candidate user group, which unlocks Modules 2 & 3.
If the automation fails for any reason, or if a user signs outside of the Onboarding system, the user may manually be granted access to Modules 2 & 3 by moving them to the appropriate “non-candidate” user group here. Here is how to do this:
- Select the appropriate non-candidate user group, and click on it;
- Click on the “Users” tab;
- Under “Group Users”, click on the name of the person you are manually adding, and click the right arrow to move them to the Assigned Group Users window; and
- Click Update to save the changes.
All Zaps are created in an Onboarding Folder through Valerie Spengler’s login.
Membership access restriction
Restrict content to specific members
The shortcode can also accept an attribute to limit the content to specific members. We can add the “plans” argument to restrict this content even further to certain members: [wcm_restrict plans="gold, platinum"]Restricted Content[/wcm_restrict]
You must use the appropriate slugs for your membership plans, which can be viewed from the plans list or by editing the plan.
The non-member shortcode can specific plans if you want to alter its behavior slightly. If you add a “plans” attribute, this will no longer only target non-members; rather, it will target all visitors who are not active members of the specified plan(s). An example:
[wcm_restrict plans="gold"] Content only shown to gold members [/wcm_restrict] [wcm_nonmember plans="gold"] Content shown to anyone who is not a gold member, even other members [/wcm_nonmember]
You can enter a list of one or more plans in this shortcode:
[wcm_nonmember plans="gold, silver"] This is shown to anyone who does not have a silver OR gold membership active. [/wcm_nonmember]
Lesson & Content Management
What Module intro content and Lessons are seen by each User Group is controlled by Membership Plans. Information about what lessons need to be accessed by which User Groups is mapped in the Onboarding System User Module Mapping.
Module 1
Module 1 is setup as a linear module, meaning the user is required to complete tasks in a linear fashion. Technically, they can mark these tasks ‘complete’ to cheat the system, but we want to strongly discourage that. Subsequent modules do not have this requirement.