Skip to content

Operations & Administration (Control)

Assignment of administration surfaces

liveForOperator

Who owns which administration page — the customer or the provider? With a reason, with the gap and with entries without a page.

Why#

A customer instance must not show a page that has not been decided on. This list is the checklist for that — and it really reads the folder instead of confirming itself.

How it works#

Click pathAdministrationAssignment

  1. 1Open “Assignment”. At the top “Who owns which surface?” and “This deployment: …” — whether this installation is the provider's or a customer instance.
  2. 2Two counters: “The customer” (stays in a customer instance) and “Universe” (operation across all customers; locked in a customer instance) (Fig. 1).
    Fig. 1 The two counters: the customer's surfaces and the surfaces of operation across all customers.
    The two counters: the customer's surfaces and the surfaces of operation across all customers.

    Fig. 1 The two counters: the customer's surfaces and the surfaces of operation across all customers.

  3. 3“Not assigned”: pages that are in the folder but in no list. They remain visible — a forgotten entry must not take anything away from the customer; nevertheless nothing has been decided about them.
  4. 4“Entered, but no longer present”: entries without a page.
  5. 5Below that, per group, every page with address (clickable) and reason.

Settings and switches#

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

The two groups#

  • The customer — university or company operations; stays in a customer instance.
  • Universe — operation of the software across all customers; locked in a customer instance. This also includes “Finances” (tuition fees and lecturer fees): the page reads across all tenants and therefore does not belong in customer hands.

Who may do what#

Only the operator. The page reads and shows; the assignment is changed in the source code.

Tips#

  • The list does not (yet) move any page; it is the checklist for a later move.
  • The permission matrix derives its administration surfaces from the same list — it exists only once.

Related features#