Operations & Administration (Control)

Accounts, roles & permissions

liveForOperator

Create real administration accounts and define in a matrix which university function may open which surface — with a visible difference between default and deliberate decision.

Why#

A student registry should see applications and records, but not the costs and operation of the installation. A president should read figures, not process records. Accounts and matrix make this configurable and traceable.

How it works#

Click pathAdministrationPermissions

1Open “Accounts & roles”. Under “Create administration account”: choose name, email, “Function” (the description appears below) and organisation, then “Create account” (Fig. 1).
Fig. 1 “Create administration account”: name, email, function with description and organisation.
Fig. 1 “Create administration account”: name, email, function with description and organisation.
2The password appears exactly once — write it down now. It is not stored anywhere and can no longer be retrieved after leaving the page. The account can sign in immediately.
3Under “Who has which role” change the function for every account; demo accounts are marked and cannot be changed here.
4Open “Permissions”: at the top the functions with their technical level, below that a table per group (university operations, operation of the installation, teaching, studies …): surfaces in rows, functions in columns (Fig. 2).
Fig. 2 A group of permissions: surfaces in rows, functions in columns, deliberate deviations outlined in bold.
Fig. 2 A group of permissions: surfaces in rows, functions in columns, deliberate deviations outlined in bold.
5A click on a cell toggles the surface for this function; a second click withdraws the decision and lets the default apply again. Outlined in bold means: deliberately deviated from the default.

Settings and switches#

No switch of its own in the feature catalogue — the feature belongs to its surroundings.

The university functions#

IT administration — operation of the installation: operations surfaces, costs, usage, guards and this matrix (technical level operator).
Study affairs — application, admission, student record, examinations office, transcript (level administration).
Administration (general) — day-to-day business of the university without the especially sensitive surfaces (level administration).
President — the view from above: figures, control, credentials; reading, not processing (level administration).
Lecturer — build a course, set an exam, assess (level learner, with teaching authorisation).
Student — the route from the study offering to the transcript (level learner).

IT administration can also change the matrix itself — it is a role of trust.

Which surfaces the matrix knows#

All pages of the administration (derived from the assignment of administration surfaces) plus surfaces outside it: proctoring & usage, lecturer surface, exam creation, learning workshop, fact-check file, student dashboard, studies, course player, survey, badges, doctorate and the HR cockpit. The longest matching path always applies.

Who may do what#

Create accounts, assign functions, toggle the matrix: only the operator.
Whoever may not open a surface lands on the dashboard with the notice “This area is locked for your function.” — “This is a setting in the permission matrix, not an error.”

Tips#

The university's organisation is at the front of the selection; empty organisations are marked “(empty)” and are at the back. Without an organisation every administration surface remains closed.
The matrix applies at one single point — the shell of all administration pages. It refines, it replaces nothing: whoever gets through here must still be allowed to access the page below.
Administration accounts are something different from the showcase's demo accounts: those can be adopted without signing in and therefore only see fictitious people.