One LMS, many teams, each with its own admin

Branches decide who sees whose data

A branch has a name, a short code, an optional parent organization, a logo and an active flag. Users and courses each belong to a branch. The part that matters is the branch isolation setting, which ships switched off. Turn it on and every role below admin (branch manager, manager, course manager, instructor and student) sees only users and courses in its own branch. Super admins and admins keep the full view.

Do one thing before you flip it: give everyone a branch. A scoped user with no branch sees nothing at all, which is the safe way to fail but will fill your inbox. Deleting a branch unassigns its users and courses. It does not delete them.

Organizations are client accounts with their own portal

Each organization has a seat limit (50 unless you change it, and every member counts, managers included), its own logo, colors, font and optional custom CSS, and a branded sign-in page reached through the organization’s own code, with its own heading, text and background image. When you assign a course to an organization you set a due date and whether it is mandatory, and every current member is enrolled at once. Removing it later revokes those enrollments, so take care. Learning paths can be pointed at chosen organizations too, and their members are enrolled automatically, both the people already there and anyone who joins later.

Members are either employees or managers. Managers get a separate portal limited to their organization. A new manager can look but not change anything until you tick one or more of four permissions: assign courses, remove courses, manage members, create accounts. A separate approval permission lets a manager accept or turn down enrollment requests from their own people on courses set to request with approval, so your central team is not the bottleneck. They add learners by pasting one line per person (email, name, department), and the import stops when seats run out. Their reports export as CSV, Excel or PDF, and what they do lands in the organization’s activity log.

The role ladder

Roles rank in a fixed order: student, instructor, course manager, then branch manager and manager at the same level, then admin and super admin. The rule is applied everywhere: you cannot edit an account at or above your rank, and you cannot grant a role at or above your own. That holds on the Users screen, in the bulk importer, through the API, and for SAML and SCIM group mappings, which are capped at admin. A refused attempt is recorded in the audit log as a privilege denial.

You can have several super admins, and they can manage each other, but the last active super admin cannot be demoted, deactivated or deleted. That spares a self-hosted install the classic lockout where the only fix is a database query.

Cohorts, search and your own wording

A group becomes a cohort when you give it a start and an end date. Assign a course to that group and drip lessons count from the cohort start (or from the learner’s enrollment, if that is later), so a March intake moves through week two together even if some people were enrolled in February.

Admin search looks across about 24 kinds of record from one box, so finding a user, a course, an organization or a certificate does not mean opening five screens. Under Settings > Terminology you can rename Course, Lesson, Assignment, Quiz, Learner and Instructor, and the new words appear across the interface. If your people say “Training” and “Trainee”, the LMS can too. The web interface itself runs in 9 languages: English, Hindi, Urdu (right to left), French, German, Spanish, Swedish, Swahili and Portuguese. Lesson content has its own setting: a video, PDF, SCORM or text lesson can carry versions in up to 20 more languages, and the lesson languages page shows how learners switch without losing their place.

For the front door, the login page designer offers 5 layouts, and the welcome page builder sets what people see first, with an optional pop-up on the dashboard.

When a client needs a site of its own

Organizations share one site. When a client, brand or division should have its own address, branding, administrator and users, the Super Admin creates a tenant instead: a white-label site on a sub-domain or the client’s own domain, with its own seat, storage and feature plan. The multi-tenant page explains how tenants are provisioned and kept apart.