Welcome!
-
-
- Learn Home
- Core Concepts
- Companies and Departments
- Courses
- Course Status and Visibility
- Modules
- Video Activities
- Reading Activities
- Document Activities
- Enrolling People in a Course
- Bulk Enroll With CSV
- Roles in a Course
- How Progress Is Tracked
- Course Reports
- Knowledge Base Overview
- Libraries and Folders
- Uploading Content Items
- Library Visibility
- AI Agent per Library
- My Courses
- Platform People
-
- Project Structure Template
- Table of Contents (TOC)
- Content Folder
- Introduction to Markdown
- Markdown Basics
- Markdown Lists
- Markdown Links
- Markdown Images
- Markdown Code
- Markdown Tables
- Markdown Equations
- Markdown Videos
- Markdown Embedded HTML
- VS Code Snippets
- Introduction to Styles
- Framed Narrations
- Markdown Configuration
- Editor Setup
-
-
-
Course Admins
TL;DR; This is where a platform owner hands a company its first (or next) Company Administrator — assign the role, remove it, or send a locked-out admin a fresh temporary password. It only ever touches the Company Administrator role, not any other role in the system.
Before you start
You need the company already set up — see Customer workspaces.
Steps
Open Course Admins (the page calls itself Platform People Management) and pick a company. Its current Company Administrators are listed with who assigned them and when.
Assign grants an existing account the Company Administrator role, scoped to that one company. If they already had it and it was removed, assigning again reactivates the same grant rather than creating a duplicate — nothing about the earlier history is lost. For someone who has no Lupo account yet, Create Account & Assign as Company Admin creates the account from an email address and assigns the role in one step.
Remove takes the role away. It's a revoke, not a deletion of the person — they stay a member of the company, they just stop being an admin of it. Assigning them again later reactivates the same underlying record.
Resend access issues a brand-new temporary password by email and invalidates the old one immediately — the page warns you: "Their current password will stop working." There's no separate reset link; the password itself is what gets emailed, and it's valid for sign-in right away rather than expiring unread. This only works for someone who currently holds Company Administrator for that specific company; it deliberately cannot be used to re-issue access for a platform owner from this page, as a safeguard against handing out platform-level access this way.
What this doesn't do
Assigning Company Administrator here is scoped to exactly one company — it doesn't touch any other role the person might hold elsewhere, and it doesn't grant billing, user-provisioning, or single sign-on configuration access. Those stay platform-owner-only regardless of who's a Company Administrator.
Common issues
Resend access did nothing. — If the target isn't currently an active Company Administrator for that company, or is a platform owner, the resend is refused with a message rather than silently sent. Check their current role first.