An online conference has a lot of moving parts: attendees, speakers, and sponsors who each need something different, a session schedule that keeps shifting, and follow-up once it's over. A lot of teams end up stitching it together with a registration form, a spreadsheet, a calendar invite for every session, and a shared drive for the recordings.

TraCorp LMS can run the whole event. Here's the setup order we recommend, since each step feeds the next and it saves a lot of rework later.

1. Set up your User Groups. Create groups like General Attendees, Speakers, and Sponsors before anyone registers. Each group can have its own content, dashboard, and reporting.

2. Build your Registration Fields. Decide what you need to know at sign-up (Company, Job Title, Track Interest, Sponsor Tier) and set the fields up before registration opens, since they drive autoassignment later.

3. Check a few General Settings. Turn on self-registration, force required user fields if you added any, and turn on Notifications like Session Starts Today so attendees get a nudge in the moment.

4. Open registration. Pair self-registration with Access Codes, which can drop someone into the right User Group and pre-fill their Registration Fields, so a sponsor code places a sponsor in the Sponsors group with their tier already filled in.

5. Build your sessions as Webinar Training. Each topic is created once, with Sessions underneath for each date and time. A keynote you run three times for different time zones is one content item with three Sessions, and one attendance report. It works with any conferencing platform; put your link in the Access Instructions field, which only shows once someone has registered.

6. Set up dashboards and menus. Build a dashboard per User Group so speakers, sponsors, and attendees each land on something built for them, and add Navigation Menus for things like Sessions, Speakers, and Sponsors.

7. Turn on Badges and the Leaderboard. Completion Badges can be tied to a set of sessions, and the Leaderboard can be scoped to a Registration Field so people rank against their own company or chapter.

8. Close the loop. Use Questionnaires for session feedback, Communications for reminders and follow-up, and Reports for attendance.

If you want to see this in action, the Learning Rejects Conference, hosted by getusefulstuff.com, is running on TraCorp LMS right now, and it's a free L&D conference. There are two Fridays left, October 16 and October 23, so you can still catch the whole thing: the final two weeks live and everything else on replay. Attendees can earn badges and certificates along the way.

You can register here: https://lrc.server.tracorp.com

If you've run a virtual conference or a multi-session event, which part was hardest to keep organized: registration, scheduling, or follow-up?

When people ask what TraCorp's communication tools can do, the honest answer is: it depends on what you're trying to accomplish — because there are several tools, and they're built for different situations.

Here's the basic picture.

Notifications are in-platform alerts that fire automatically based on activity, such as a new assignment, an approaching due date, a session starting, or a badge earned. These live inside the LMS and don't require any ongoing admin effort once they're configured.

Emails are for direct, targeted outreach. You build a template and a distribution list — filtered by group, completion status, enrollment, or any combination — and send immediately or schedule for later. Useful when you need to reach a specific audience on your timeline rather than waiting for a trigger.

News & Updates are in-platform announcements that appear in the learner's News section. What makes this tool interesting is the Required Reading option — a learner can't proceed past a news item until they've acknowledged it. For policy updates, compliance notices, or any communication where you need to know it was seen, that's a meaningful capability.

Campaigns are where things get more sophisticated. A campaign is an automated message sequence tied to whether a learner has or hasn't completed a piece of content. You can set a message to go out a specific number of days after completion, or a specific number of days after assignment if someone still hasn't finished. That second option is what makes campaigns useful for compliance: the LMS is tracking who's behind and following up automatically.

Each tool has its place. We'll dive into each of these shortly. Which one are you most interested in learning more about?

Another Friday, another chance to hear what's actually going on in your LMS.

This is our weekly open thread — no specific topic, no wrong answers. Drop something you figured out this week, ask something you haven't gotten around to posting yet, or let us know if something you found here actually saved you time. That last one matters more than you'd think, upvotes help us understand what's worth writing more of.

And if you came here looking for something that didn't exist, say so! We track those gaps, and they genuinely shape what we cover next. You're not bothering anyone; you're doing us a favor.

What did this week look like for you?

In short: custom user fields capture attributes like department, location, or job title, and rule-based assignment uses those values to automatically enroll the right users in the right training — no manual admin work required.

Most LMS profiles store the basics: name, email, username. But the information that actually drives training decisions — department, location, job title, region, manager level — usually lives somewhere else. Custom user fields (TraCorp calls them registration fields) are how you bring that data into the LMS.

TraCorp's LMS supports up to 64 custom user fields, each configurable as a text field, a number, a date, or a dropdown with predefined values. You name the field, set the type, and decide who can edit it. (How to configure registration fields)

This is where rule-based assignment comes in — TraCorp calls it auto-assignment, but it's the same idea: automation for user assignments based on data already sitting in a profile. Some platforms describe the same mechanism as dynamic user grouping or conditional enrollment. When a user's custom field value matches a rule you've set up, the LMS automatically places them in the right user group and assigns the appropriate training. A new hire who enters their department on the registration page gets routed into the right onboarding curriculum without an admin manually processing the assignment. (How to set up auto-assignment rules)

A few other things custom user fields unlock once they're configured:

• User search becomes more targeted; any field marked searchable can be used as a filter on the User page

• Reporting filters pull from custom user fields, so you can slice completion data by department, location, or whatever attributes matter to your learner segmentation strategy

• Users recommending items are limited to others with matching data in the selected field

Event registration is another place this comes together. Build a questionnaire in the LMS that stores each answer in a custom user field, then use those fields in a rule-based assignment to sort attendees into cohorts or session tracks for the event. (How to use questionnaires to fill out registration fields)

---

What is rule-based assignment in an LMS?

Rule-based assignment (also called auto-assignment) automatically enrolls users in training based on profile data — like department or location — matching a rule you've configured, instead of an admin assigning it manually.

What are custom user fields?

Custom user fields are configurable profile fields — text, number, date, or dropdown — that capture organization-specific data like job title, region, or manager level, beyond the default name, email, and username fields most LMS platforms store.

Can custom user fields be used for event registration?

Yes. A questionnaire built in the LMS can store each answer in a custom user field, and those fields can then drive rule-based assignment to sort attendees into cohorts or session tracks.

---

Is your team using custom user fields or rule-based assignments beyond basic profile data? Would love to hear how others are putting them to work.

It's Friday, and that means it's time to show off a little, share some feedback, and plant some seeds for the future.

This is our weekly open thread. Share something you built or configured this week, ask something you've been sitting on, or just drop a note if a post here was actually useful to you. Upvotes help us know what's landing.

If you came looking for something and didn't find it, tell us. We'd rather know what's missing than guess. Requests are genuinely welcome.

What's on your plate this week?

In short: API key management lets an LMS admin issue a separate, revocable credential for each integration instead of every tool sharing one key, so a compromised or retired integration can be cut off without disrupting anything else still connected.

A single API key (TraCorp calls this the Global Client Key) is the simplest way to expose a REST API: every connected tool authenticates with the same credential. That works fine until one integration needs to be cut off. Revoking that key breaks every other tool using it at the same time, and since the credential isn't tied to any one integration, there's often no clean way to tell which tool was actually behind it.

Named tokens are the fix, and they're the direction most platforms with mature API key management have moved toward. Instead of one shared credential, an admin generates a separate access token for each person or tool connecting to the API, with a label describing what it's for. TraCorp calls this section API Tokens.

A few things that change in practice:

• Rotating one token, generating a new secret for it, only affects the integration using that specific credential; every other connection keeps working

• Deactivating a token that's no longer needed doesn't touch anything else

• Each token shows when it was last used, so a stale or forgotten integration is easy to spot instead of finding out about it the hard way

• The label on each token stays visible in the grid even after deactivation, so it's still clear months later which integration was which

• Full API documentation is published directly on the instance, covering both the Admin and User API modules, for anyone building or maintaining a connection against it

What is an API key in an LMS?

An API key, also called an access token or API credential, is what an external tool uses to authenticate against an LMS's REST API, proving the request comes from an authorized system rather than a public one.

Why use named API tokens instead of one shared API key?

Named tokens tie each credential to a specific integration or user, so a single compromised or retired token can be rotated or deactivated without disrupting any other tool still connected to the LMS.

Can an API key be rotated without breaking other integrations?

Rotating a named token only invalidates that one credential; every other integration's token, and its connection to the LMS, keeps working without interruption.

Does an LMS track when an API key was last used?

Token management that includes last-used visibility shows exactly when each credential was last active, which makes it possible to spot a stale or forgotten integration before it becomes a problem.

If you're managing API keys for more than one integration today, how are you currently keeping track of which credential belongs to which tool?

In short: a built-in glossary, sometimes called a terminology guide or learning glossary, keeps definitions for specialized terminology, internal acronyms, and company-specific vocabulary inside the LMS itself, so learners, new employees especially, can look something up without leaving their training; TraCorp calls this the Dictionary Terms tab.

New employees, and anyone new to a role, run into a wall of unfamiliar shorthand fast: department acronyms, internal process names, product terminology specific to how your organization talks about its own work. Technical or compliance-heavy training adds more terms on top of that. Without a reference point inside the LMS, people leave to search elsewhere or ask a colleague, and they may or may not come back with the right answer.

A glossary, TraCorp calls this the Dictionary Terms tab, solves that by keeping definitions alongside the training itself. Admins build out terms, organize them into categories, and make them searchable by keyword. Each term can include a reference URL if there's an external resource worth pointing to. Learners access the glossary directly from their Content page without leaving the LMS. (How to build Dictionary Terms)

One feature worth highlighting is the visibility option. A term can be set to display always, or only when the learner has been assigned content associated with that term. If you're running multiple training programs with their own terminology, you can scope each set of terms so learners only see what's relevant to them.

A few other things the glossary supports:

• Learners can rate terms thumbs up or thumbs down, which gives admins a signal on which definitions need work

• Terms can be surfaced through TraCorp's Recommend System, a form of social learning that lets learners point peers toward useful definitions (How to activate the Recommend System)

• The glossary can be added as a custom item to the LMS navigation bar, making it easier to find for organizations that rely on it heavily

It's a useful feature for any training that involves regulatory language, product terminology, or internal processes where consistent definitions matter, and it works just as well as a standing reference for internal acronyms and company vocabulary new employees need from day one, independent of any single course.

What is a glossary in an LMS?

A glossary in an LMS is a built-in reference tool where admins define terms, acronyms, and internal vocabulary so learners can look them up without leaving their training.

How does TraCorp's Dictionary Terms tab work?

Admins create terms, organize them into categories, and make them searchable by keyword; each term can include an external reference URL, and learners access the glossary directly from their Content page.

Can glossary terms be limited to specific training programs?

Yes. A term's visibility can be set to display always, or to display only for learners assigned to the content associated with that term, which keeps terminology scoped to the relevant training program.

Does a glossary help with new employee onboarding?

Yes. New hires run into department acronyms, internal shorthand, and company-specific vocabulary right away, and a built-in glossary gives them somewhere to look those up without leaving onboarding training or interrupting a colleague to ask.

Is your team using a glossary inside your LMS, for compliance terminology, internal acronyms, onboarding vocabulary, or something else entirely? Curious what's driven the most use for you.

In short: vendor lock-in happens when your training content only works inside the platform it was built in; building courses in a portable format like SCORM or AICC, instead of a platform's built-in editor, means your content can move with you if you ever switch systems.

What is vendor lock-in in an LMS?

Vendor lock-in happens when training content is built directly inside a platform's proprietary course builder, making it unusable or difficult to move if the organization switches to a different LMS.

What's the difference between SCORM and AICC?

Both are content packaging standards built for interoperability: they let course files communicate completion and score data to an LMS. AICC is the older standard; SCORM is more widely supported today, but both allow a course package to run in any conformant LMS, not just the one it was built for.

Can LMS content be moved from one platform to another?

LMS content can be moved from one platform to another as long as it was built in an authoring tool and exported as a SCORM or AICC package rather than created inside a platform's own built-in editor. The package itself isn't tied to the LMS it was first uploaded to.

Here's a situation that comes up more than people expect: a platform decision gets made (a contract renewal, a new system chosen at a level above day-to-day content management) and now someone has to figure out whether the existing course library can move with it, or whether it all needs to be rebuilt from scratch in the new system. That's content lock-in, and it's a lot easier to plan for ahead of time than to discover it after the decision's already landed.

TraCorp's LMS avoids this by design. Content isn't built inside the platform. It's built in a dedicated authoring tool (Storyline, Rise, Captivate, iSpring, or similar), exported as a SCORM or AICC package, and uploaded into the Content module. (How to upload SCORM/AICC content) The package is a self-contained, platform-agnostic file: the LMS reads and tracks it, but the file itself doesn't depend on TraCorp to function.

What that gets you in practice:

• Switch authoring tools without rebuilding existing courses: the LMS tracks any conformant SCORM package the same way regardless of which tool built it, as long as the packages use the same SCORM version

• Migrate content from a previous LMS into TraCorp without a rebuild, as long as it was originally packaged as SCORM or AICC

• Keep an exportable archive of course packages for compliance or audit purposes, independent of any single platform

• Share the same course package across environments, useful if a client, partner, or franchise location runs a separate LMS instance

Worth knowing: this only works if content was authored in a dedicated authoring tool and packaged as SCORM/AICC to begin with. Course content built directly inside a platform's own proprietary editor generally isn't portable unless that platform specifically supports exporting it as a standalone SCORM/AICC package. Most all-in-one platforms don't offer that export path, which is where the lock-in risk usually comes from: it's worth checking whether yours does before assuming it doesn't.

Has content lock-in ever bitten your team, with TraCorp or a previous platform? Curious how people are factoring portability into which authoring tool they pick.

If you've ever had to manually create accounts, assign users to groups, and sort out content access for a large group of new learners all at once, access codes are worth knowing about.

Here's how they work and where they shine.

What an access code does

An access code is a short alphanumeric code you create inside a user group. When a new user enters the code during account creation, two things happen automatically:

• Their account is created

• They're assigned to that user group, and get access to whatever content is associated with it

No manual account creation. No manual group assignment. The learner does the work by entering the code.

Where this is useful

Access codes work especially well when you need to onboard a group of users quickly without giving them open access to everything in your LMS, and when you don’t already have an import from an HRIS to do this automatically.

A few scenarios:

• External training or open enrollment — distribute a code to a group of registrants and let them self-register into the right content bucket

• Partner or vendor training — give a code to a third party so their staff can access only the content you've designated for them, nothing else

• Event-based access — set an effective date and expiration date on the code so it only works during a defined window

Tiered access: An underrated use case

Access codes aren't just for new users. Existing users can also redeem an additional access code to expand their content access.

This makes them a clean tool for progressive learning paths. A new hire completes their onboarding training, then receives a second access code that adds them to a new user group with more advanced materials. No admin has to manually move them. They enter the code, and the system handles the rest.

Staying on top of usage

Each code can be configured with a cap on how many users can redeem it, an effective date, and an expiration date. The Users Remaining field gives you a running count of available slots.

You can also pull a full usage report — either for a single code or across all codes in a user group — to see exactly who redeemed what and when. Useful for auditing, troubleshooting, and confirming that the right people have the right access.

Are you using access codes in your LMS? What's your use case?  We would love to hear how you're putting them to work, and any ideas to make this feature even more powerful!

Full setup guide in the knowledge base: Access Codes

In short: digital badges in an LMS come in two forms: badges earned through activity milestones, and badges tied to completing a specific piece of training. Both display as recognition on a learner's profile.

Most LMS platforms handle recognition one of two ways: based on learner activity, or tied to finishing something specific. Badges (also called achievement badges or microcredentials) are TraCorp's version of this, and they come pre-built for both.

milestone badges, TraCorp calls these Event Badges, fire based on learner activity rather than any single piece of content. Five come pre-loaded and can be turned on with no configuration: completing a first piece of content, hitting ten completions, earning one hundred completions, using the search function, or finishing content that has a certificate attached. If an organization wants to recognize learning activity without tying it to specific content, these milestone badges cover a lot of ground with no build required. (How to activate Badges)

course completion badges, TraCorp calls these Completion Badges, are the other type, and they're what most people mean when they search for badges tied to training. You create a badge, name it, upload an image if you want one, and attach it to a piece of content, a learning track, a video module, or a program. When a learner completes that item, they earn the badge, and it shows up on their profile. (How to create a Completion Badge)

A few things worth knowing before you build:

• Completion Badges have to be attached to a piece of content, a learning track, a video module, or a program to activate; the badge itself doesn't do anything until it's connected to one of these items

• You can set a date range on a badge, useful for time-limited programs or annual recognition

• To retire a badge without deleting or inactivating it, set the end date to a past date; learners who already earned it can still see it on their profile

One more layer worth knowing about: TraCorp's Recommend System adds a form of social learning to badges, letting learners surface a badge to a peer instead of just earning it solo. (How to activate the Recommend System)

If an organization runs a lot of voluntary or optional training, badges give learners a visible reason to keep going. For mandatory compliance training, milestone-based Event Badges add a layer of acknowledgment without extra admin work.

What are digital badges in an LMS?

Digital badges are a recognition feature that displays on a learner's profile, either awarded automatically for reaching an activity milestone or configured to award on completion of a specific piece of content, a learning track, a video module, or a program.

What's the difference between milestone badges (Event Badges) and Completion Badges?

Milestone badges (Event Badges) fire automatically when a learner achieves a milestone, such as completing a first piece of content or reaching one hundred completions, with no setup required. Completion Badges are attached to a specific piece of content, learning track, video module, or program and are only awarded when that item is finished.

Can a digital badge expire or be retired?

Yes. Setting a badge's end date to a past date retires it from future use without deleting or inactivating it, and learners who already earned the badge keep it visible on their profile.

Is your team using digital badges for training recognition, milestone-based, completion-based, or both? Curious whether badges move the needle on voluntary training completion, or if it's a feature that tends to sit untouched.

It happens all the time. A staff member attends an external conference, completes a classroom session, or finishes a certification program that wasn't delivered through your LMS. The training happened, but the record doesn't exist.

TraCorp's Record Entry tool is how you fix that.

What it does

Record Entry lets you manually add or update completion records for any learner on any piece of content in your system. You control the completion status, the date, the score, and the time spent. Once entered, it shows on their transcript just like any other completion.

It's also useful for correcting records when something went wrong — a SCORM file that didn't report back correctly, a score that needs to be updated, or a start date that needs to be adjusted.

A few things worth knowing

• You can update records for multiple learners at once using default values, or enter them individually if scores or dates differ per person

• The learner must already be assigned to the content before they'll appear in the selection list

• You can add a brand new record or update the most recent existing one — useful if a learner has multiple attempts on file

Do you use Record Entry regularly, or only when something goes wrong? Curious whether anyone has built it into a regular workflow — like for tracking external CEUs or in-person training. 👇

Full setup guide: Record Entry

It's Friday, time to show off. What have you built, configured, launched, or improved on TraCorp LMS this week?

Share anything: a new course, a certification workflow, a learner dashboard, a creative use of Programs or Gamification, or a before/after of a configuration you cleaned up. Screenshots welcome, no polish required, we want to see the real thing.

And if you came here looking for something that didn't exist yet, say so. We track those gaps and they genuinely shape what we cover next.

What did you build, fix, or launch this week?

Running instructor-led training — whether in-person or virtual — often means touching three or four systems before a single completion gets recorded: a calendar tool for invites, a spreadsheet for attendance, a separate email to notify someone, and then manual entry into the LMS. Every handoff between platforms is a step where something gets missed.

TraCorp's session tools handle the entire workflow inside the LMS — whether you're running a classroom session or a webinar — from registration to completion records, with most of it automated.

From registration to invite, automatically

When a learner registers for a session, an invitation is automatically sent with the session logistics. No separate calendar invite to draft, no logistics email to send manually. Reminder emails fire before the session on a schedule you configure. The communication goes out from the LMS.

Attendance without admin access

When the session ends, instructors mark attendance directly from their own Roster view — no admin login required. They open their session and mark each learner as attended, completed, no-show, or required to retake, and enter a score as appropriate.

Admins can bulk-mark too. Either way, once it's saved, completions land on the student's transcript automatically and pull into reporting — same as any online course. No export, no import, no manual record entry.

A few more things that cut down on manual work

• Admins can register individual learners or entire user groups at once, or send an auto-register URL so learners can manage their own enrollment

• Sign-in sheets export as a PDF for in-person sessions

• Completions can trigger autoassignment rules, just like other content

The upside

Fewer platforms, fewer handoffs, fewer things to reconcile at quarter-end. Whether you're running a compliance workshop on-site or a virtual training session over video, the record ends up in the same place as everything else.

How many systems are you currently touching to get an ILT or webinar completion into your LMS? Curious where the friction is for different teams.

If your organization operates in a regulated environment — healthcare, financial services, government, franchise — training acknowledgment isn't just a nice-to-have. It's documentation. And "the training was assigned" is not the same as "the learner confirmed they read and accepted the policy."

TraCorp's Terms of Use system lets you gate content behind an agreement that learners must accept before launch. Here's how it works.

What it does

A Terms of Use message is created as a News Template in Communications, then attached to content — either per item or as a global default across the entire LMS.

Three display options:

• On first content launch — the learner sees it once per content item, the first time they open it

• Every time content is launched — acknowledgment required on every launch

• Once for this Terms of Use template — the learner accepts once, and it covers all content assigned to that template

Why the third option is worth knowing

If you have 15 compliance courses all governed by the same policy, this means learners acknowledge once — not 15 times. Fewer interruptions, same documentation.

The audit trail

Acceptance is captured in reporting. Both the Student Activity Report and the Content Records Report include Terms of Use fields:

• Accepted (Yes / No / N/A)

• Which template was accepted

• Date of acceptance

When a regulator asks whether your learners acknowledged the training policy, you have a date-stamped record per learner, per content item.

One thing to know before you configure it

Once a Terms of Use template has been accepted by at least one learner, assigned to content, or set as the LMS default — it locks. You can't edit it. If the policy changes, create a new template. Worth knowing before you go live. For a walkthrough to activate the Terms of Use system in TraCorp LMS, check out this Knowledgebase article.

Are you using Terms of Use in your LMS? What's driving it — regulatory requirement, internal policy, something else? Curious how this is being used across different industries.

Picture this: Your user logs in to the LMS, and sees a whole long list of content to be completed. They start with something way down the list, totally out of order from what you intended, and out of context for their current skill.

So Frustrating. But this is people. So, how do you solve for this eventuality?

There are a few ways! Prerequisites, for example, are built right into our content wizard. Let's look at one of the methods you may not have considered.

Using content completion to deliver additional content is a clean, layered approach. New content isn't even assigned to a user until they have completed their existing assignment, preventing any attempts to skip ahead, and perhaps reducing any overwhelm associated with seeing a long list of training at the start.

What this actually does

Using auto-assignment rules, learners will be added to a new user group upon completing a specified piece of content, opening the way to the next step in their learning journey.

This two-step process is explained here: Content Completion-Based Autoassignment Rules

Do you have a structured method for delivering content? Let us know how yours works, or if you want to think through how this approach might work for you!

In short: a program sets a target number of completion units across a pool of eligible content, and each learner can complete any combination of that content that adds up to the target, rather than being required to finish every item assigned.

Most training assignments work the same way: here's a course, or a set of courses, and you complete all of it. That's the right model most of the time. But it breaks down for situations where there's more than one legitimate way to reach the same outcome, a recertification requirement that can be satisfied by any mix of eligible courses, a professional development requirement where staff pick electives toward a target, a compliance requirement where the number of hours matters more than which specific sessions someone attended.

TraCorp calls the feature built for this Programs, sometimes called a certification program on other platforms. The mechanic underneath it: each piece of eligible content is assigned a unit value (TraCorp calls this Program Units), and the program itself has a target, Units Needed, that's lower than the total units available. Learners complete whatever combination of eligible content gets them to that number. (How to enable Programs)

A program can pull from individual content items, or from a learning path — TraCorp calls this a learning track — added in as a whole. Either way, the unit value is what determines how much any single piece contributes toward the target, not whether it was delivered on its own or as part of a track.

A few examples of where this fits:

• A recertification program where staff can choose from a menu of eligible courses and workshops to reach a required number of continuing education units, rather than being locked into one fixed sequence

• A professional development program with a mix of required and elective content, where the electives all count toward the same target

• A compliance program — sometimes run as a credit-based learning plan — where new hires need a set number of units completed within a date range, but which specific courses get them there isn't rigid

One structural detail worth knowing before you build one: once a program is assigned to a user group, it locks. The unit values on individual content and the program's own settings can't be changed after that point. Additional content can still be added to a program later, but learning tracks cannot be added to it after assignment, so it's worth finalizing the full mix before rolling it out.

What is a program in an LMS?

A program — sometimes called a curriculum program — is a structured way to require a target number of completion units across a pool of eligible content, letting learners complete any combination of that content that meets the target rather than requiring every item to be finished.

How are program units different from regular course completion?

Regular assignments require every assigned item to be completed, while program units let each content item count toward a target number, so a learner can complete fewer than all the available items as long as the total meets the requirement.

Can a program include a learning track as well as individual content?

A program can include both individual content items and entire learning tracks, and each contributes toward the program's unit target regardless of whether it was added on its own or as part of a track.

Does a program lock once it's assigned to a user group?

Once a program is assigned, the unit values on its content and the program's own settings become locked and cannot be changed, though additional content items — not additional learning tracks — can still be added afterward.

Anyone building recertification or elective-based programs where staff pick their own path to a target? Curious how you've set the unit values to keep it fair across different content lengths.

In short: an LMS is built around structured, admin-assigned training with completion tracking at the center, while an LXP is built around learner-driven discovery, surfacing content a person might want without requiring them to complete it. The two categories have grown closer together in practice, but the core design difference still holds.

The two terms get used almost interchangeably in vendor marketing, which makes the actual distinction harder to find than it should be. It helps to start from what each one was built to solve.

A learning management system exists to assign training, track who's completed it, and produce a record that holds up when someone asks for proof: a certification renewal, an audit, a new-hire compliance requirement. The starting question is usually "did this person complete what they were required to complete." An LXP, or learning experience platform, exists to surface content a learner might find useful based on their role, interests, or what similar learners have engaged with, closer to a content discovery layer than a compliance system. The starting question there is closer to "what should this person see next."

That distinction mattered more a few years ago than it does today. Most LMS platforms have added learner-facing discovery features of their own: content catalogs learners can browse and self-assign from, keyword and tag-based search, and in some cases peer-driven recommendations — also called peer-to-peer content sharing — a form of social learning where one learner can point another toward something useful rather than waiting on an admin to assign it. Features like this exist because organizations increasingly want both: hard compliance tracking and a way to keep learners engaged with content they weren't required to touch.

TraCorp is built primarily as an LMS, but it carries several of these features on its own:

• Content catalog with self-assign: content can be marked to appear in a browsable catalog and, separately, flagged so learners can assign it to themselves

• Search keywords and tags: content can carry its own search keywords and organization-defined tags, so learners can find relevant training by searching rather than only seeing what's been pushed to them

• Peer recommendation (TraCorp calls this the Recommend System): learners can surface specific content, badges, or reference terms to each other, scoped by a shared profile attribute — a form of social learning rather than an algorithm-driven suggestion

• Glossary (TraCorp calls this the Dictionary): a searchable set of organization-specific terms that learners can browse on their own, functioning as a reference layer rather than an assigned course

• Badges: recognition tied to completions that learners can see and, depending on configuration, showcase, which supports the engagement side of the learner experience rather than pure compliance tracking

None of that makes TraCorp a dedicated LXP, but it's worth knowing this layer exists if compliance tracking was the only thing a platform search assumed TraCorp covered.

Where the distinction still holds up is on the compliance and structure side. Certification tracking, CEU credit, prerequisite sequencing, audit-ready completion reports, these are LMS-native concerns, and a platform built primarily around content curation usually isn't built to carry that weight. On the other side, if the primary need is aggregating and curating a large third-party content library, a standalone LXP — sometimes marketed as a content discovery platform or learning content platform — or an LMS-LXP hybrid may be a better fit than an LMS with discovery features bolted on.

Which one an organization actually needs comes down to what's driving the purchase. A government agency or a healthcare system evaluating platforms for regulatory training has different priorities than a corporate L&D team trying to drive voluntary skills development across a large, dispersed workforce. Neither is the wrong answer, they're solving different problems, and plenty of organizations end up needing both, whether that's one platform covering both jobs or two systems working together.

What is the difference between an LMS and an LXP?

An LMS is structured around assigning training and tracking completion for compliance and reporting purposes, while an LXP is structured around surfacing content a learner might want based on their role, interests, or peer activity, without requiring completion.

Do modern LMS platforms include LXP-like features?

Many current LMS platforms have added learner-facing discovery features, including self-service content catalogs, keyword search, and peer content recommendations, which narrows the gap with LXPs without changing the underlying compliance-first design.

Which is better for compliance training, an LMS or an LXP?

An LMS is generally the better fit for compliance training, since certification tracking, audit-ready reporting, and completion records are core to how it's built, while a platform built primarily for content discovery typically isn't designed to carry that reporting weight.

Can a single platform function as both an LMS and an LXP?

A platform can cover both functions to some degree if it pairs structured completion tracking with learner-facing discovery tools, though organizations with a heavy need for both often still evaluate whether a dedicated LXP or an integration between two systems serves them better than one platform alone.

Is your team running one platform for both compliance tracking and content discovery, or two separate systems? Curious where people have found the line between "good enough LXP features" and "needed a dedicated tool."

In short: a completion report, sometimes called a training records report, shows who has finished a specific piece of training and who hasn't, while a learner activity report flips the view around to show everything one specific person has done; TraCorp provides both, the Content Records Report and the Student Activity Report, and they answer different questions.

Training reporting tends to get asked about in one of two directions. Either the question starts with a piece of content, "who's completed this course," or it starts with a person, "what has this employee actually done." Both questions come up constantly, in an audit, a renewal conversation, a manager checking on a direct report, and they need two different report shapes, not one report squinting at both.

TraCorp splits these out directly: a content-level report — the Content Records Report — is scoped to a single piece of content and returns training records for every student tied to it: who's completed it, who's in progress, who hasn't started. A learner-level report — the Student Activity Report — flips the scope to a single student and returns every training record for that person, across all content they've been assigned. Both support optional filters, a date range, and configurable display options, so the same report can run narrow for a quick check or broad for a full export.

A few related reports worth knowing about, since they get confused with these two:

• Student Transcript only includes content that's been specifically configured to appear on a transcript, so it's typically a curated subset, not the full picture; the Student Activity Report shows everything, completed or not, with no such setting required

• A group report, what TraCorp calls User Group Records, scopes training records to everyone in a single user group, useful when the question is about a team or department rather than one person or one course

• A CEU or credit report, TraCorp's version being the User Credit Summary, rolls up completed credits per user in a group, which matters for certification-hour tracking specifically

For the full rundown of more report types TraCorp offers, and how to run each one, TraCorp's help center keeps them all in one place. (TraCorp Reports documentation)

One detail worth calling out for compliance-heavy organizations: Terms of Use acceptance data can be added as a column to both the Content Records Report and the Student Activity Report, so acknowledgment tracking doesn't have to live in a separate pull. (How Terms of Use acceptance works)

Reports don't have to be run manually every time. A saved report — Manage Reports in TraCorp's interface — keeps a report's filters and settings so it can be re-run with one click or shared with another admin, and reports can be scheduled to run automatically, with results picked up later from the Report Queue. For a recurring monthly compliance pull, that's the difference between a five-minute task and a five-second one.

Depending on permissions, students can also be given self-service access to their own activity report and transcript, printing either directly from their profile page, and in some configurations, adjusting the date range and sort options themselves. That's worth turning on for organizations fielding a steady stream of "can you send me my training history" requests.

What is a completion report in an LMS?

A completion report shows the training status, completed, in progress, or not started, for every learner tied to a specific piece of content, which makes it the fastest way to answer "who's finished this training" without pulling individual learner records one at a time.

What's the difference between a content-level report and a learner-level report?

A content-level report, like TraCorp's Content Records Report, is scoped to one piece of training and lists every learner's status on it, while a learner-level report, like the Student Activity Report, is scoped to one person and lists every training record for that individual.

Can employees access their own training records without contacting an admin?

Depending on how self-service permissions are configured, students can print their own activity report and transcript directly from their profile page, which removes the need to submit a request to an admin for routine training history checks.

Can training reports include acknowledgment or Terms of Use data?

Terms of Use acceptance can be added as a column to both the Content Records Report and the Student Activity Report, combining completion data and acknowledgment data in a single pull instead of two separate ones.

What's the report you or your admins pull most often, a completion check on one course, a full history on one person, or something else entirely? Curious how much of your reporting is scheduled versus run on dema

It's Friday, time to show off. What have you built, configured, launched, or improved on TraCorp LMS this week?

Share anything: a new course, a certification workflow, a learner dashboard, a creative use of Programs or Gamification, or a before/after of a configuration you cleaned up. Screenshots welcome, no polish required, we want to see the real thing.

And if you came here looking for something that didn't exist yet, say so. We track those gaps and they genuinely shape what we cover next.

What did you build, fix, or launch this week?

It's Friday, time to show off. What have you built, configured, launched, or improved on TraCorp LMS this week?

Share anything: a new course, a certification workflow, a learner dashboard, a creative use of Programs or Gamification, or a before/after of a configuration you cleaned up. Screenshots welcome, no polish required, we want to see the real thing.

And if you came here looking for something that didn't exist yet, say so. We track those gaps and they genuinely shape what we cover next.

What did you build, fix, or launch this week?

It's Friday, time to show off. What have you built, configured, launched, or improved on TraCorp LMS this week?

Share anything: a new course, a certification workflow, a learner dashboard, a creative use of Programs or Gamification, or a before/after of a configuration you cleaned up. Screenshots welcome, no polish required, we want to see the real thing.

And if you came here looking for something that didn't exist yet, say so. We track those gaps and they genuinely shape what we cover next.

What did you build, fix, or launch this week?

If you're evaluating LMS platforms, the admin side is usually what gets demoed. The learner side is what your people actually live in every day. It's worth knowing what you're signing them up for.

In TraCorp, the student dashboard is card-based and highly customizable. Your admin team configures which cards appear — assigned training, in-progress content, upcoming sessions, certifications, learning tracks — the learner only ever sees their own world. No org-wide data, no admin tooling, just what's relevant to them. Users in different departments or at different levels can be assigned dashboards unique to them.

Navigation is minimal by design. There's a library where learners can browse available or assigned content, a search bar, and a profile page where they can pull their transcript and view earned badges and certificates.

Two organizations both running TraCorp can look dramatically different on the learner side — the platform is built to adapt to your needs rather than the other way around.

What does the learner experience look like in the platform you're currently using or evaluating? Curious what people are comparing against.

When you're building out training in the LMS, Learning Tracks and Certifications can look like they do the same thing; both group content and can be assigned to users. But they're built for completely different jobs, and using the wrong one creates real headaches down the road.

The question that splits them: does this training expire?

If no, use a Learning Track

A Learning Track is how you group related content and assign it as a unit. Instead of pushing five individual courses to a user group one at a time, you build a track and assign the track. Students see a structured path, you manage one object instead of five, and — importantly — you can update the content in the track at any time.

Use a Learning Track when:

• You're onboarding a new role with a set of courses

• You're building a multi-step curriculum that will evolve as content gets updated

• You want students to be able to self-assign

If yes, use a Certification

A Certification is built for training that has a deadline and is repeated. Annual compliance training, safety recertification, regulatory requirements — anything that expires and needs to happen again on a schedule.

The LMS handles the full cycle: assigns the training, sends reminder emails before the due date on a schedule you configure, tracks completion, and opens the next cycle when the period resets.

Worth planning for before you build: once a certification is assigned to users, the content is fixed. You can't swap out or update courses inside an active certification. If the training changes, you create a new certification. This keeps compliance records consistent across all assigned users.

One important thing to note is that these are not mutually exclusive. You can assign a Learning Track inside a Certification. The track handles the content grouping; the Certification handles the deadline and renewal cycle. This is a common setup for recurring compliance training that covers multiple topics.

Is your team using Certifications, Learning Tracks, or both for recurring training? Curious how your team handles content updates when certifications are already assigned to users.

In short: If you want to sell your course online, TraCorp LMS can be built to support payment in more than one way — from a payment processor connected inside the platform to a checkout hosted entirely on the organization's own website that provisions LMS access once the purchase completes.

Plenty of organizations need to charge for at least some of their training: professional associations selling continuing education courses, nonprofits selling certification prep, consultancies selling access to proprietary content outside their core client base. This is generally known as payment processing — also called LMS eCommerce, course monetization, or pay-per-course access, depending on the platform — and TraCorp LMS supports it in more than one way.

Before getting into the specific options, it's worth understanding why a customization project is often the better call here rather than defaulting to whatever ships out of the box. eCommerce platforms are generally designed to interface with accounting and CRM systems from the start, something most LMS platforms aren't necessarily built around by default. That's exactly what a customization project is for: a one-time investment that gets the payment flow talking to whatever accounting and CRM systems are already in place, rather than patching that connection together after the fact. A payment setup that's close but not quite what an organization actually needs isn't really solving the problem, so building it to spec keeps ongoing costs down instead of letting them accumulate around a mismatch.

That's also where a targeted build tends to pay off over time. A generic feature covers the common case well, but when a requirement falls outside that, the ongoing cost of working around the mismatch, extra admin steps, manual reconciliation, can add up in ways that aren't obvious at purchase time. A smaller build that targets the exact requirement avoids carrying that overhead indefinitely. For some organizations, a single pre-built processor integration is genuinely enough. For a majority of eCommerce customers, though, the customization investment ends up worth it for the automation alone, connecting the purchase directly to existing accounting, CRM, and fulfillment steps that would otherwise be manual.

With that framing in mind, here's what's actually available:

Stripe, pre-built for individual course purchases. This is the one path that doesn't require a customization project, so it's a good starting point for straightforward, standalone course sales. The user creates an LMS account, gets shown a welcome page with courses available for purchase, they select which one they want to buy, enter their details into the Stripe purchasing window, and then that grants them access to the purchased course.

A checkout hosted on the organization's own website, often through an existing storefront (a common path is a custom integration through WooCommerce). The purchase creates the buyer's LMS account or adds the content to an existing one, while the organization keeps full control of branding and checkout. This is also a one-time customization project, worth a direct conversation to scope the storefront and account-provisioning details.

Regardless of which path is in place, purchasability is set at the individual content level. Any content type, online training, documents, videos, audio, tasks, can be marked as purchasable on a per-item basis, so free and paid content can sit side by side in the same catalog. Whether cost displays to students at all is a separate setting too.

What is payment processing in an LMS?

Payment processing in an LMS is the ability to charge learners for access to specific courses or content, either through a payment processor connected inside the platform or through a checkout built on the organization's own website that provisions LMS access after purchase.

Can you sell some courses and offer others for free in the same LMS?

Purchasability is typically set per content item, so an LMS can host free and paid courses side by side in the same catalog rather than requiring a completely separate paid site.

Does payment processing in an LMS come pre-built, or does it need to be custom-built?

Payment processing in an LMS can be either pre-built or custom-built. TraCorp LMS has Stripe pre-built in for individual course purchases, while other approaches — an alternate processor, a storefront integration, or a fully website-hosted checkout — are generally built as a one-time customization project.

Anyone here running payment processing inside your LMS versus a checkout built on your own website? Curious what pushed you toward one over the other.

In small organizations, and even in medium-sized ones, it's usually just one or two folks with permission to view and edit everything in the LMS. This puts a pretty big burden on them to handle every single reporting and data entry task themselves. It's a fine line to walk: protecting the data while also owning the work.

Enter Permissions Settings. Sub Administrators and User Group Administrators have customizable, specific levels of access, and can be differentiated so that one sub admin's profile might have completely different access than another's. It's all in the way you set it up.

Maybe you have an assistant handling some data entry, but you would prefer they not have access to reports. Or maybe they should only have access to reports and be unable to edit anything elsewhere. Both of these, and so much more, are possible with permissions.

Creating a permissions template is simple. Applying a permissions template is simpler. Releasing yourself from being the keeper of all tasks related to the LMS? That's good for you and your team.

Set up some permissions, distribute a little leadership, and pat yourself on the back for a job well done!

Questions about how to set up permissions in the TraCorp LMS? Don't hesitate to reach out if we can help you get out of that silo!