Enforce tenant module availability in Views
This commit is contained in:
@@ -20,6 +20,13 @@ use their normal permission checks. Required Views retain the View selector and
|
||||
administration surfaces needed to inspect and change the assignment, preventing
|
||||
administrators from locking an installation out of its own configuration.
|
||||
|
||||
Views are also the canonical user/group module-visibility mechanism. Core
|
||||
creates a root `<module>.module` surface for every WebUI module, so a View may
|
||||
hide or reveal a tenant-effective module without creating a second personal
|
||||
module-state store. A View cannot make a module operationally available when
|
||||
system tenant policy excludes it, and it cannot grant the Access permissions
|
||||
needed to use the module.
|
||||
|
||||
## Administration
|
||||
|
||||
The module contributes **Views** sections to system and tenant administration.
|
||||
|
||||
Reference in New Issue
Block a user