Welcome!

Platform People

TL;DR; Learn has no company-wide roster where you add, deactivate or bulk-create accounts. An account comes into existence the moment someone is given access to something — enrolled on a course with Enroll User or Bulk Upload, registered on a class through the run roster's import, or granted a knowledge base — and every change to who holds what is made on that course's People tab or that knowledge base's People page. Users and Roles, in the account menu, is the read-only company-wide view of all of it. The page called Platform People Management belongs to Lupo's platform administrators; a Company Administrator who opens it gets an access-denied page.

Most of the Learn pages in this guide are about courses — building them, teaching them, taking them. This page is about the people layer underneath: how people in your company come to have an account, where you can see them, and what you can and cannot change about them.

How people get an account

There is no "Add Person" form. Lupo creates an account, and adds it to your company, when you first give an address access to something:

  • Enroll User on a course's People tab — type an email, pick a role, click Send Invitation. If the address has no account, one is created and an invitation email is sent; the person sets their own password when they accept. See Enrolling People in a Course.
  • Bulk Upload on the same tab — a CSV of emails with optional names and passwords. Every new address gets an account, a password (the one in your file, or a generated one) and an invitation email that carries it. See Bulk Enroll With CSV.
  • Import CSV on a delivery run's roster — registers the people in the file on that run. With Create accounts for addresses that do not have one ticked, "each new learner gets an account and an invitation email asking them to set their own password"; left off, rows with no matching account are reported rather than registered. See Manage the Roster.
  • Bulk grant on a knowledge base's People page — a CSV of email,password that creates the missing accounts, adds them to the company and gives each one KB Manager or Member access. Download template gives you the two columns.
  • Grant KB access on a knowledge base's People page — "Invite anyone by email — they don't need a Lupo account yet. If their email isn't in Lupo, we create the account for them, add them to this company, and email them a one-click sign-in link."

A person's name is whatever they enter themselves — or, for an account a CSV import created, the name in the file. Nothing you upload later renames an existing person.

Users and Roles — the company-wide view

Open the account menu (your name, top right) and click Users and Roles. A Company Administrator sees it for their own company. Its subtitle says exactly what it is: "Who is in each department, and what they hold across Knowledge, Learn and Create. Read-only — changes happen in the existing editors."

  • Department: — All departments is the default; click a department to narrow the list.
  • Company-wide — the people who hold something on the whole company rather than in one department, with Person, Learn and Create columns.
  • One table per department, with Person, Knowledge (KB Manager and KB Member grants), Learn (course roles — each course name links to that course's People tab) and Create (a Seat badge for someone who holds a Create-plane seat in the department).

Role names appear as Lupo's own identifiers — the same in every language — and the page changes nothing: you cannot add, remove or re-role anyone from it. Knowledge base grants are made on the knowledge base's own People page (see below), not here.

To check your own access rather than someone else's, click My Roles in the same menu — "What you hold, where you hold it, and what an absence stops you doing."

Where changes are made

A course's People tab. Enroll User, Bulk Upload, Change Role and Remove, plus a Filter… box to find someone on a long roster. An Instructor can enroll and remove Students and Observers; only a Company Administrator can add or remove an Instructor. See Enrolling People in a Course and Roles in a Course.

A delivery run's roster. Registering, waitlisting and removing people on a class of an instructor-led course happens on that run's roster, not on the course's People tab. See Manage the Roster.

A knowledge base's People page. Open the knowledge base and click People (the button is shown to KB Managers and Company Administrators, not to KB Members). There you Grant KB access as a Manager or a Member, change a role, or revoke it, and Bulk grant does the same for a CSV of addresses at once. "Managers can add and remove members; only company admins can revoke other managers." A Company Administrator needs no grant of their own to manage every knowledge base in the company. See Knowledge Base Overview.

What you cannot do today

Said plainly, because the absence is the thing people search for:

  • Create an account on its own. Someone gets an account by being enrolled, registered or granted something. There is no standalone account form and no company-level "add person".
  • Deactivate a person or remove them from the company. Remove on a course's People tab and revoking a knowledge base grant take away that one access; the account itself, and its membership of your company, stay. If someone has left the organization, remove them from each course and knowledge base they hold.
  • Bulk-create accounts without enrolling them. Every CSV import here grants something: the course's Bulk Upload enrolls, a delivery run's Import CSV registers, and a knowledge base's Bulk grant gives KB access. There is no CSV that only creates users.
  • Reset someone's password. Password resets are self-service: the person uses the forgot-password link on the sign-in page. An invitation that never arrived can be re-sent from a delivery run's roster — Resend invitation on that person's row — but not from a course's People tab, where enrolling the address again is refused as already enrolled; write to help@lupo.ai for that case.
  • Appoint a Company Administrator. That grant is made by Lupo, on the platform console described below. To add or remove a Company Administrator for your company, write to help@lupo.ai.

Platform People Management (Lupo staff only)

The page headed Platform People Management exists "to assign Company Administrators who can manage their company's Learn content and users". It is where Lupo's platform administrators pick a company, search for an existing user by email and Assign them, or Create Account & Assign as Company Admin for a new address (an email address is the only field; the person receives a temporary password by email). The same page lists the Current Company Admins of each company, can Resend access (a new temporary password, mailed) and can remove someone as Company Admin.

It is not part of a customer's Learn. A Company Administrator who follows a link to it is refused, and the People & Access button on a company's page that leads there is shown only to platform administrators. Nothing on it deactivates a person or removes them from a company either — it grants and revokes one role.

Company-level, course-level and knowledge-base roles

A person can hold roles at three levels, and they add up:

  • Company level — Company Administrator, granted on the whole company: creates and manages its courses, delivery runs and knowledge bases, enrolls Instructors, and reads Users and Roles. It's the only company-level role a customer holds; there is no company-level Instructor.
  • Course level — Instructor, Student or Observer, granted per course. See Roles in a Course.
  • Knowledge base level — KB Manager or KB Member, granted per knowledge base.

Most people hold only course-level roles. Company Administrator is reserved for the small number of people who run Learn on behalf of the organization, and is appointed by Lupo. For the full matrix, see Who Can Do What.

Where to go next