Skip to content

Operations & Administration (Control)

Subscription & activation

ForAdministrationOperator

Every organisation books exactly what it needs: individual building blocks, individual features or everything. Seats and billing monthly or yearly, changes immediately and pro rata; features that are not booked show a calm activation card instead of an error.

Why#

Not every institution needs everything. Whoever only wants group work books only group work; whoever grows adds features without renegotiating. A single source decides what is enabled — pages, interfaces and background jobs all follow it.

How it works#

  1. 1Administration: open “Subscription & features” (address /admin/abo).
  2. 2Choose building blocks — “Build & learn courses” is always included. “Everything” selects all building blocks. Under “More features individually” (expand) are features available without the whole building block; anything already in a chosen building block is not listed there.
  3. 3Whatever a feature needs is added automatically and named on the right; whoever deselects something sees what goes with it.
  4. 4Set seats and billing (monthly or yearly). On the right are the total and — for a running subscription — the pro-rata amount for the rest of the period.
  5. 5“Subscribe” leads to checkout; the first subscription starts with a trial. For a running subscription, “Apply change”: added features are enabled after payment, removed ones are credited pro rata.
  6. 6Below: next invoice, invoices as PDF, payment method and billing address, grants and “Cancel subscription” (at the end of the period, can be undone until then).
  7. 7Wherever a feature that is not booked appears in the product, a card shows its benefit in one sentence; administrators see the price and “Enable now”, everyone else only that their organisation can enable the feature.

Settings and switches#

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

  • Applies only to organisations switched to the subscription; all others keep their switches as before.
  • Whoever was there before the switch keeps everything they use (grandfathering).
  • The tenant switch can still turn a booked feature off — but cannot turn anything on beyond what is booked.

If a payment is outstanding#

  • Everything keeps running until the end of the grace period; the page names the date.
  • After that, creating and managing are read-only: content stays visible, changes are blocked.
  • Learning always remains possible — courses, quizzes, exams, credentials.
  • After a cancellation everything booked is read-only. Nothing is deleted.

Who may do what#

  • The organisation's administration books, changes and cancels the subscription and sees invoices and prices.
  • The operator grants pilot customers and trials in the cockpit /admin/abo-betrieb.
  • Everyone else only sees, at a feature not booked, that their organisation can activate it — without prices.

Tips#

  • If a payment is outstanding, everything keeps running at first. After that, creating and managing are read-only; learners keep learning, and no data is lost.
  • The operator grants pilot customers and trials of individual features in the cockpit /admin/abo-betrieb — with an end date or without.

Related features#