Branches is one of our favorite features because it can do so much for your training. Branches essentially let you plan and implement a broad range of training scenarios.

For example:

• Company A uses TalentLMS to train employees from various departments, where each department has a different manager in the portal.
• Company B uses TalentLMS to train its employees, customers, and partners in separate training environments.
• Company C uses TalentLMS to sell its training courses or offer courses to third parties for free.
• A B2B agency uses TalentLMS to provide training courses for different clients.

Branches make such training settings and many more possible.

To help you with that, here’s a brief guide with our best practices to using Branches for multi-purpose training.

A. Stop using your main URL for training

When you decide to use Branches to organize your training, it’s best to stop using your main URL for training purposes. Here’s why:

• Your main portal is a repository for every piece of information regarding all your users, groups, courses, categories, etc. Branches restrict admin access to branch-specific information only.
• Through your main portal, you can generate reports that include your entire user base, regardless of what branch a user or a course belongs to. Branches let your managers generate branch-specific reports (including Custom reports), to better supervise and record user progress and activity.
• Your main course catalog includes all your courses regardless of what branch they belong to. Branches have their own separate course catalogs tailored to their specific audience.

If you already use your main URL for training, you can still make the transition to a branch-based scheme. Just move your existing users and courses to a new branch. You can do it without losing any critical data (e.g., course progress) by using the TalentLMS Import feature (i.e., usertobranches;branch, coursetobranches;branch) or the Mass actions in the Custom reports feature.

The only thing that might change for your users is the sign-in process if you decide to restrict it by checking Restricted branch (1) on the branch Info page. In that case, non-Superadmin users will be able to access only the branch URL. The only change your users may experience is during the sign-in process. Since Restricted branch is enabled by default, users assigned to that branch must sign in through the branch URL.

B. Assign Branch administrators

When you divide your main portal into branches to segment your training, it’s best to assign separate administrators to your sub-portals too.

Branch admins can be set to have access to branch-specific information and settings only, and absolutely no access to your main domain and the overall platform data. When assigned with the default Admin-type user type, a branch admin is allowed to:

• Create and edit branch users, courses, and groups.
• View reports on branch users (and reset course tests for branch users).
• Communicate with branch users through messages and discussions.
• Create and lead ILT units and conferences in branch courses.
• Grade the branch users’ assignments.

By default, a branch admin cannot access:

• Categories
• Branch settings
• User Types
• Import-Export
• Account & Settings

C. Know your global settings

There are specific settings that apply to all branches, and can only be set up centrally by a SuperAdmin (or an admin with the respective permissions).

These settings are:

Notifications

Notifications are created and configured from the main domain. Their event, recipient, and filter settings are also controlled from the main domain and cannot be changed from within a branch.

When creating a notification, you can use the Branch filter to make it available to one or more specific branches. If no branch filter is applied, the notification is available to all branches. Depending on the notification type, additional filters may also be available, such as Group, Learning path, or Courses.

Once a notification is available to a branch, Branch Administrators can manage it directly from that branch. They can change its status, subject, and message body, as well as add Smart Tags. These changes apply only to users of that branch.

To learn more about managing notifications in branches, see this article.

When the event that triggers a notification is associated with a specific branch, the URLs included in its body point to that branch. For example, if a user is added to a branch upon creation from the main portal, created by a Branch Administrator, or signs up through the branch login page, the notification includes the branch URL (2).

User Types

When you want specific features (e.g., discussions, gamification) to be accessed by the users of a branch (e.g., your employees) and not the users of another (e.g., your customers), create a custom user type. Here, you can apply restrictions and then assign the user type you created to the appropriate training audience.

Import - Export

To assign multiple users to a branch at once, you can use the Import feature (i.e., usertobranches;branch or coursetobranches;branch) on your main portal. 

Account & Settings

Most of the general settings have to be set up through the main domain by the SuperAdmin (or an admin with the respective permissions), and they apply to all branches.

These are:

• Security settings
• Password settings
• Terms of service
• Social options
• Default user type
• Visible user format
• Specific eCommerce options
• Badge set
• AI features availability

If you’re using a mapped domain, branches have to be mapped separately (see this article) as sub-domains of your custom domain.

When you add a custom field to users or courses, you have the option to make it branch-specific (i.e., it’s visible only to the branch admin). Just toggle the Selective availability (3) switch to enable it and choose a single branch from the respective drop-down list (4).

Gamification rules for when points, badges, and levels are awarded to learners are configured centrally and apply to all branches, but each branch has its own user leaderboard and default badge set. When activated, gamification applies to all portal users. To deactivate it on a specific branch, you have to create a custom learner type (i.e., without gamification permissions) as mentioned above. You also have the option to reset the points, badges or levels for the users of a specific branch (5).

Settings that can be configured separately for each branch, are those available on branch pages:

• Branding (Logo, Favicon, Branch theme, Custom homepage)
• Language and Τime zone
• Announcements
• Default group and sign-up method
• SSO (you can enable or disable SSO on a branch or use different SSO methods on different branches)
• eCommerce payments and subscriptions
• Badge set
• AI features availability

Course settings and availability rules

For courses that are shared between branches, any training programs (i.e., prerequisites) or specific settings (i.e., time limits, certifications, prices, etc.) apply to all those branches.

Any changes made to a course apply to all enrolled users, across the branches sharing that course. A simple workaround for that is to clone a course and assign a different copy to each branch. Also, you could revoke permission to update or delete courses from the user types assigned to branch admins and instructors.

Alternatively, if you want to keep the courses separate while maintaining shared content, you can create a course for each branch and use linked units from a main course. This way, any changes made to the original units are automatically reflected in their linked versions across the branch-specific courses. Keep in mind that tests, surveys, assignments, and ILT units cannot be linked. 

Branch-specific associations and configuration 

From the main portal, you can also manage certain resources and settings separately for each branch:

• Skills (6): Assign specific skills to a branch and manage which skills are available within it. How to use Skills in Branches in TalentLMS.
• Learning Paths (7): Assign specific Learning Paths to a branch so they are available to that branch’s users. 
• Files (8): Upload and share files specifically with the users of a branch.
• Integrations (9): Configure supported integrations separately for each branch.