Welcome!

Platform People

TL;DR; Platform People is where you add users to a company so they can take courses, teach, or administer content. It's the admin side of the LMS: the roster of everyone who exists inside your organization's LMS footprint, separate from per-course enrollment.

Most of the LMS pages in this guide are about courses — building them, teaching them, taking them. This page is about the people layer that sits underneath: who can be enrolled in courses in the first place.

The two-step model

Lupo's LMS separates "who exists in the company" from "who is enrolled in which course." Getting a learner into a course is usually two steps:

  1. Add them to the company as a person. This creates a user record tied to the company and gives them an account in the LMS.
  2. Enroll them in a specific course. See Enrolling People in a Course.

Step 1 happens once per person. Step 2 happens as often as you add them to new courses.

For small organizations, step 1 is nearly invisible — the bulk enroll flow or the per-course Add Person flow will create the user record on the fly if it doesn't already exist. But for larger organizations with multiple courses and departments, it's useful to manage the person layer directly.

The Platform People page

From a company's admin page, open the People or Platform People section. You'll see a list of every person who exists inside that company's LMS, with columns for:

  • Name
  • Email
  • Role(s) they have somewhere in the company (Student, Observer, Instructor, or admin)
  • Date added
  • Status (active, inactive)

You can search the list by name or email and filter by role.

Platform People page showing a company's full roster

Adding a person

Click Add Person (or similar). You'll get a form with:

  • Email — the person's email address. This is the unique identifier Lupo uses.
  • First name and Last name.
  • Company — inherited from the page you're on.
  • Default role — usually "Student," but you can set admin or Instructor here if you're adding someone who will be a content author.

Once added, the person gets an account tied to that email. They'll receive an invitation or welcome message depending on your company's settings, and they'll be able to sign in and see whatever they have access to.

Adding a person does not enroll them in any courses. That's a separate step — see Enrolling People in a Course.

Bulk-adding people

If you're setting up a new company or migrating from another system, you'll want to add a lot of people at once rather than clicking through the form for each one. The bulk flow typically accepts a CSV with columns like email, first_name, last_name, role. It's the same CSV shape used for per-course bulk enrollment — see Bulk Enroll With CSV for the format details.

For the platform-people-level bulk add, the CSV creates user records; it doesn't enroll them in anything yet.

Company-level roles

A person can have roles at two levels:

  • Company-level roles — "admin" or "instructor" on the company itself. These grant broad permissions like creating courses, managing departments, or editing the company's settings.
  • Course-level roles — per-course assignments like "Student," "Observer," or "Instructor" for a specific course. See Roles in a Course.

Most people have only course-level roles. Company-level admin is usually reserved for a small number of people who run the LMS on behalf of the organization.

Removing or deactivating people

You can usually:

  • Deactivate a person — they can't sign in, but their historical progress and completion data is preserved in course reports.
  • Remove them from a company — they're detached from it entirely, but (again) historical data stays in the reports.

Both options preserve history. Permanent deletion of user data is rare and typically requires admin intervention.

Deactivate someone when they leave the organization or no longer need LMS access. Don't remove them unless you're certain you won't need to restore their access later.

Why you'd manage this directly

Most day-to-day work happens at the course level — enrolling learners, building content, reviewing reports. You'll find yourself on the Platform People page specifically when:

  • Onboarding a new cohort of learners and you want to pre-create their accounts before enrolling them in individual courses.
  • Assigning someone company-level admin rights because they'll be managing multiple courses.
  • Auditing who exists in the LMS — useful during offboarding cleanup.
  • Troubleshooting — if a learner "can't sign in" or "doesn't see their course," the first check is usually "does their person record exist in the company at all?"

Where to go next