An LMS administrator is whoever owns the recurring jobs that keep a learning management system accurate: new-hire enrollments, leavers, reports, course versions and releases. At a company of a few hundred people, those jobs rarely add up to a full-time role, so they can stay split across people you already have, as long as every task has one named owner and a test that proves it ran.
That matters because an auditor won’t ask who your LMS administrator is. They’ll ask why last month’s leaver could still sign in, or why a completion is missing. This guide gives you the task calendar, a pass test for each task, the line between your work and IT’s, and a rule for when the work needs one person’s name on it.
Key Takeaways
- LMS administration runs on a cadence: daily questions, weekly enrollment checks, a monthly leaver and report check, and a quarterly catalog, certificate and release review.
- A task is done when its test passes. “Offboarding done” isn’t a test. “Last month’s test leaver can’t sign in” is.
- The administrator owns paths, courses and completions. IT owns sign-in and account removal, and the HRIS owns names, roles and managers. The administrator runs the leaver test, and IT fixes what it finds.
- On a hosted LMS the vendor patches the software. Self-host Moodle and a point release every two months, plus a major release every six, lands on your calendar.
- In the worked example below, a 400-person company on a hosted LMS spends about 19 hours a month on administration, under a day a week, so the work can stay split.
Course building isn’t on the calendar below. An AI LMS drafts a first version of a course from the policy documents you already have, so your hours go to the checks.
What an LMS Administrator Owns, and What Belongs to IT
The usual job description lists five areas: configuration, users, reports, integrations and support. Two of them, users and integrations, sit half in IT’s queue. That’s why one job title rarely covers them, and why an unscoped admin role ends up holding tickets it can’t close.
Draw the line by data instead. Each kind of data has one system that holds it and one person who edits it. Your work starts at the third row.
| Data | System that holds it | Who edits it | What the LMS administrator does |
|---|---|---|---|
| Who can sign in, account creation and removal | Identity provider (Okta, Microsoft Entra) | IT identity admin | Runs the monthly leaver test and reports failures |
| Names, roles, departments, managers, start dates | HRIS (Workday, BambooHR, ADP) | HRIS admin | Builds assignment rules on these fields and sends bad data back to HR |
| Paths, groups, assignment rules, notifications, certificate templates | LMS | LMS administrator | Owns them |
| Courses and their versions | LMS | LMS administrator, with each course’s content owner | Uploads, tests and retires them |
| Completions, scores, certificates | LMS | LMS administrator | Owns the record and the reports |
| Platform faults and releases | Vendor, or your IT if self-hosted | Vendor support | Logs tickets and re-tests after a release |
One rule sits under the table: every field has one editor. If a job title is wrong in the LMS, fix it in the HRIS. Otherwise the next sync overwrites your fix or disagrees with it. Our LMS integration guide covers how each of those connections is built.
Account removal follows the same split. Automatic account creation and removal between an identity provider and an LMS often runs over SCIM, the IETF protocol published as RFC 7644. Setting it up is IT’s work. Your part is the test: once a month, confirm that people who left can’t get in.
Do this first: send the table to IT and the HRIS admin and ask each of them to confirm their row in writing. Until they do, their tasks are still sitting on your desk.
The LMS Administration Calendar
Here’s the recurring work, sorted by how often it comes around. Every row has a pass test: a yes-or-no check that someone other than the owner could repeat. It’s the same idea as the go-live gates in a 90-day LMS implementation plan, carried on past launch.
| Cadence | Task | Passes when | Usual owner in a split team |
|---|---|---|---|
| Daily | Answer sign-in and assignment questions | Every question gets an answer the same working day | L&D generalist |
| Weekly | Check last week’s new hires | Each start date in the HRIS has an account, the right path and a due date | L&D generalist |
| Weekly | Read the sync and error report | The report is empty, or every error has a ticket with an owner | L&D generalist, IT for sign-in errors |
| Weekly | Send overdue lists to managers | Every manager with an overdue learner has the names | L&D generalist |
| Monthly | Leaver check | Nobody who left in the HRIS this month has a working account, and a sign-in with the test leaver account fails | IT removes, L&D tests |
| Monthly | Training report | Five learners picked at random match their own records in the report | L&D generalist |
| Monthly | Policy-change check | Every course tied to a policy that changed this month has a new version live | Content owner, L&D generalist |
| Monthly | Admin rights review | Every admin account belongs to a current employee who still needs it | L&D generalist, IT |
| Quarterly | Catalog review | Courses nobody has taken in 12 months are retired, and every live course has an owner and a review date | L&D generalist |
| Quarterly | Certificate look-ahead | Every certificate expiring in the next 90 days has a renewal assignment | L&D generalist |
| Quarterly, and after any release | Release check | A test learner signs in by SSO and a test completion reaches the report | Vendor or IT, L&D tests |
| Quarterly | Seat count | You know active accounts against contracted seats before anyone asks | L&D generalist |
| Yearly | Renewal and exit check | The renewal notice date is in the calendar, and one course and its completion history have been exported and opened | L&D generalist |
Three rows carry most of the risk, and each one is easy to run badly.
The leaver check is a sign-in attempt, not a report. An account list can look clean while a local password or an old invitation link still works. Ask IT for a test account that goes through the same removal as a real leaver, then try to sign in with it.
The report check compares totals with records. Pick five people, open their individual records, and compare them with the numbers your director will see. A report built on a completion that never recorded is wrong in a way no dashboard shows. Which reports are worth building is a separate question, and this row only checks that the ones you send are true.
The policy-change check needs a trigger from outside L&D. Give each course a content owner in the business and ask them to tell you when the policy behind it changes. The calendar can’t catch a change nobody reports.
Copy the table into a shared calendar and replace every owner title with a name. A row with a team name in it has no owner yet.
What Breaks When a Task Has No Owner
Unowned tasks don’t fail loudly. Each one leaves a record that looks fine until someone outside L&D reads it.
- Leavers keep access. Creation gets noticed on a new hire’s first day. Removal doesn’t get noticed at all, and on a per-user contract those forgotten accounts can keep counting against your seats. The monthly leaver check catches it.
- Old course versions stay assigned. A course built on last year’s policy keeps going to new hires, and the audit finds people signed off on a rule that no longer applies. The policy-change check and the catalog review catch it.
- Assignment rules drift. Rules run on HRIS fields, so three spellings of one job title become three groups, and an empty manager field leaves people off a manager’s view. The weekly new-hire check catches it within a week instead of a quarter.
- Completions go missing without an error. A course can open, look right and send nothing to the LMS. Nobody sees it. The gap shows up only when the report doesn’t match the room that took the training. The release check and the report spot-check catch it.
- A self-hosted site falls out of support. An upgrade with no name next to it doesn’t happen late. It doesn’t happen. The next section has the calendar for it.
If you can staff only three rows this quarter, staff the leaver check, the report spot-check and the policy-change check. Together they produce the evidence an audit asks for: who has access, who finished, and whether they finished the current version.
Upkeep: Who Patches the System, and Who Re-Tests the Content
Two recurring jobs depend on facts the usual job description skips: who hosts the software, and whether a course file has changed.
Patching depends on who hosts it
On a hosted SaaS LMS, the vendor patches and upgrades on its own schedule. Your task is the release check from the calendar: read the release notes, then have a test learner sign in and complete a course.
On a self-hosted install, patching is your task, and the software sets the calendar. Moodle, for example, ships a major release every six months, in April and October, and a point release every two months. A standard release gets 12 months of general support and 18 months of security fixes in total. A long-term-support release gets 36 months of security fixes.
So a self-hosted Moodle site on standard releases needs six point releases a year and a major upgrade at least once a year to stay in general support. Each upgrade needs a staging copy and a rollback plan. That’s a calendar row with a person’s name on it, or a site that’s out of security support 18 months after its release. The hours for each hosting model are worked through in SaaS, hosted or self-hosted LMS.
A replaced course file is a new course
A SCORM package you re-upload can import cleanly and still run under the wrong version. The version a package claims is one line of text in its manifest, and the platform matches that text against the strings it recognizes. Moodle’s SCORM code accepts 1.2, 1.3, CAM 1.3, 2004 3rd Edition and 2004 4th Edition, and it gives anything else the SCORM 1.2 runtime, with no error at import.
A 2004 package running under the 1.2 runtime plays normally and reports nothing, or half of what you expected. So this risk doesn’t end when an LMS migration does. Every update from an authoring tool, every re-export with different settings, and every file a content vendor sends you is a new package as far as tracking is concerned.
The test is the same each time. Before the new file replaces the old one, a test learner completes it inside your own LMS, and the completion, score and date show up in the report. What a SCORM file contains has the two-stage version of that test, and the SCORM 1.2 vs 2004 guide shows the manifest line to read.
Do You Need a Named LMS Administrator?
Most companies of a few hundred people don’t need a full-time LMS administrator. They need one of three models, and the calendar above tells you which one.
| Model | Who does the work | Who makes sure every test ran | Fits when |
|---|---|---|---|
| Split | L&D generalist, IT identity admin, HRIS admin, vendor support | Each task owner | Hosted LMS, SSO and the HRIS as the only connections, completions that aren’t audit evidence |
| Named part-time administrator | Mostly the same people | One named person | Completions are audit evidence, or the calendar runs past about a day a week |
| Full-time administrator | One person, with IT support | The administrator | Self-hosted, several connected systems and regulated recertification at once |
Read these rules in order and stop at the first one that fits.
- If you self-host, name one person. Write that name next to the software’s support dates.
- If completions are audit evidence and the calendar runs past about a day a week, name one person. They don’t have to do every task. They have to know every test ran, because on a split team everyone assumes a missed task was someone else’s.
- If the LMS connects to more than sign-in and the HRIS, give every connection an owner who would notice within a week if it stopped. If nobody on the split team can read all of them, that’s the named administrator’s job.
- Otherwise, keep it split. Put one person’s name on a short monthly review of the calendar itself, so a skipped row gets caught in weeks, not at the audit.
A worked example, for illustration
A 400-person company runs a hosted LMS with SSO and an HRIS sync, about 40 live courses and a handful of new hires a month. The times below are assumptions, so replace them with your own after a month of real use.
| Cadence | Tasks and assumed times | Hours a month |
|---|---|---|
| Daily | Questions: 15 minutes × 20 working days | 5 |
| Weekly | New hires 30 min, error report 15 min, overdue lists 30 min: 75 minutes × 4 weeks | 5 |
| Monthly | Leaver check 1 h, report 3 h, policy changes 2 h, admin rights 30 min | 6.5 |
| Quarterly | Catalog 4 h, certificates 1 h, release check 2 h, seat count 30 min: 7.5 h ÷ 3 | 2.5 |
| Total | The yearly renewal and exit check isn’t counted | 19 |
Nineteen hours a month is about 4.4 hours a week (19 × 12 ÷ 52). That’s under a day a week, so rule 2 doesn’t fire, and this company keeps the split model with one monthly calendar review.
Change one fact and the answer moves. Self-host the same LMS on Moodle with two major upgrades at 12 hours each, six point releases at 2 hours each, and an hour a week of monitoring and backups. The calendar gains 88 hours a year (24 + 12 + 52), about 26 hours a month in total, and rule 1 fires before the hours matter.
Building new courses isn’t in any of these numbers. It’s project work, and it’s where the hours grow when the business asks for more training.
If you’re pricing a hire. The US Bureau of Labor Statistics doesn’t track LMS administrators as an occupation of their own. Its nearest one is training and development specialists, who “plan and administer programs that train employees.”
That occupation’s median annual wage was $69,280 in May 2025. It runs training programs, not a system, so price the decision in hours from your own calendar rather than from a job title.
Set Up the Calendar in a Week: A Checklist
Each item is either done or not.
- [ ] IT and the HRIS admin have confirmed their rows of the ownership table in writing
- [ ] Every calendar row sits in a shared calendar with one person’s name on it
- [ ] IT has set up a test leaver account that goes through the same removal as a real leaver
- [ ] A test learner exists for each role, with the right path and a due date
- [ ] Every live course has a content owner and a review date
- [ ] The vendor’s release notes, or your own upgrade dates, are in the calendar
- [ ] The renewal notice date from the contract is in the calendar
- [ ] The split, named or full-time decision is written down and sent to your director
Put a Name and a Test on Every Row
Don’t start by asking who your LMS administrator is. Start with the ownership table. Send it to IT and the HRIS admin this week.
Then set up the test leaver and a test learner, and run the leaver check first, because nobody else will run it for you. After a month of real use, add up the calendar’s hours and apply the four rules in order.
Mini Course Generator is our product, and it’s hosted, so the patching row is ours rather than your team’s. Team seats for the people who share the work, and learner SSO on the Custom plan, are on the pricing page.
FAQ
What does an LMS administrator do?
An LMS administrator keeps the learning management system accurate: new-hire enrollments, leaver access, current course versions, reports and re-tests after releases. If a stakeholder needs the basics first, send them what an LMS does.
Is LMS administrator a full-time job?
Rarely, if the LMS is hosted. It moves toward full-time when you self-host, connect several systems and run regulated recertification at the same time.
What skills does an LMS administrator need?
Comfort with spreadsheets and CSV exports, enough HRIS knowledge to spot a bad field, and the ability to write an assignment rule a manager can follow. The habit that matters most: test before you close a ticket. Deeper technical skills only become part of the job on a self-hosted install, where upgrades are yours.
What’s the difference between LMS administration and LMS support?
LMS support is the vendor’s job: platform faults, outages and questions about how a feature works. LMS administration is yours: how your paths, courses, records and reports are set up. If the test learner fails right after a vendor release with nothing changed on your side, call support. If it fails after a change you made, it’s yours to fix.
What records prove the LMS administration tasks ran?
Keep three: the ownership table with IT’s and the HRIS admin’s written confirmation, the calendar with a name on every row, and a log of every test. Each log line needs the date, who ran the test and whether it passed. A failed test with a ticket number beside it still shows the check ran and the gap got caught.
Sources
- IETF RFC 7644 – System for Cross-domain Identity Management (SCIM): Protocol
- Moodle releases – release calendar and support windows
- Moodle SCORM module source – manifest version matching
- Training and Development Specialists – US Bureau of Labor Statistics, Occupational Outlook Handbook
