Operations & Administration (Control)
Assignment of administration surfaces
面向运营方
Who owns which administration page — the customer or the provider? With a reason, with the gap and with entries without a page.
用途#
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.
使用方法#
操作路径AdministrationAssignment
- 1Open “Assignment”. At the top “Who owns which surface?” and “This deployment: …” — whether this installation is the provider's or a customer instance.
- 2Two counters: “The customer” (stays in a customer instance) and “Universe” (operation across all customers; locked in a customer instance) (图 1).
图 1 The two counters: the customer's surfaces and the surfaces of operation across all customers. - 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“Entered, but no longer present”: entries without a page.
- 5Below that, per group, every page with address (clickable) and reason.
设置与开关#
功能目录中没有独立开关——该功能属于其所在环境。
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.
提示#
- The list does not move any page; it is a checklist.
- The permission matrix derives its administration surfaces from the same list — it exists only once.
相关功能#
- Administration: overview, bar and toolsThe home page of the admin back end with tiles, the bar of all administration pages and the tools overview with running counts of open items.
- Tenants & brandCreate new customers with their own address, their own corporate design and their own modules — one platform, many organisations, strictly separated data.
- Accounts, roles & permissionsCreate real administration accounts and define in a matrix which university function may open which surface — with a visible difference between default and deliberate decision.