Roles
Every account has one or more roles. Roles decide whether you can enter the admin panel and what you can do there.
| Role (PL) | Panel | Can |
|---|---|---|
| Administrator (Administrator) | yes | Everything, including users, roles, settings, API clients, the audit trail and the monitoring tools |
| Editor (Redaktor) | yes | Manage categories, courses, sections, lessons, pages, menus and the whole media library; grant and revoke course access; use the AI assistants; preview unpublished material |
| Instructor (Prowadzący) | yes | View categories, and the courses they teach with their sections, lessons, students, entitlements and quiz attempts, in the panel; upload to the media library and manage their own uploads, and read (never change) a colleague’s file their course uses; open their own courses on the site before they are published; be named as an instructor of a course |
| Student (Uczestnik) | no | Browse the catalogue, join free courses, work through the courses they were granted |
Students who open /admin see an access-denied page. Visitors who are not signed in are sent to the login page.
What each role sees in the panel
Section titled “What each role sees in the panel”- An editor sees Courses, Categories, the Media library, Pages, Menus, Enrolments, Entitlements, Quiz attempts and AI generations.
- An instructor sees Categories, and Courses, Enrolments, Entitlements and Quiz attempts narrowed to the courses they are named on — read-only, and nothing of anybody else’s course — and the Media library narrowed to the files they uploaded, which they may change, and the files their own courses use, which they may open read-only (The media library).
- An administrator sees all of that plus Users, Phrases, Settings (Ustawienia) — which holds Branding, Styles, Fonts, Site pages, Languages, Region and time, Sign-up, Profile fields, Roles and permissions, Media and storage, Mail, AI assistants and API clients (The panel) — and the Monitoring group.
An instructor’s preview is narrower than an editor’s: they can open the courses they are named on, and no others.
Changing what a role may do
Section titled “Changing what a role may do”Administrators edit permissions under Ustawienia → Role i uprawnienia (Settings → Roles and permissions). Each entity — users, roles, languages, styles, categories, courses, sections, lessons, pages, media files, menus, enrolments, entitlements, quiz attempts, AI generations, API clients, the activity log — offers only the actions that entity really has, so a tick box you see is a tick box that does something.
The administrator role ignores permissions and always has full access. Only an administrator opens this page, and only an administrator gives anybody a role, because whoever could do either could hand themselves everything.
Nothing on it can lock the site out of itself. The four built-in roles — Administrator, Editor, Instructor, Student — can be neither renamed nor deleted, since the panel, sign-up and full access all look for them by name; a role you add yourself can be both. You cannot take the administrator role off your own account, so there is always somebody who can undo a mistake: another administrator can take it from you, and nobody can take it from the last one. Changes apply the next time the person loads a page.
Nobody but an administrator is given languages, styles, API clients, the audit trail or the monitoring tools by default. You can grant them to another role if you want to, and Shield lists them as permissions of their own.
Profile fields per role
Section titled “Profile fields per role”Which extra profile fields somebody is asked for depends on their roles. Out of the box an instructor is asked for a job title, a short biography, a website, LinkedIn, X and YouTube; nobody else is asked for anything. Administrators change that list under Ustawienia → Pola profilu (Settings → Profile fields) — see Administration.
HiLMS is MIT-licensed. No replicants were harmed in the writing of these books.