Site Restrictions
This page contains a grid listing application-level entities that may be hidden. These application-level entities are mostly available via the navigation bar at the top of the Cadebill application window.
Warning – These restrictions will affect all users. To setup restrictions for specific users/groups use Application Permissions instead.
Site Restrictions
Restricting a module, sub module or menu, automatically hides from the menus. Menu related page restriction will be auto removed, as if they are not specified. Table and fields will be hidden in UI.
If a field is restricted and nullable then the field is hidden on both read, edit. If a field is restricted and NOT nullable, it is shown only in edit mode.
Field's Description
Site Restriction ID Internal, Identity Field.
Module ID Generally, a module is restricted by license. However, if a company has the license, but currently not using it, the entire module can be hidden.
Sub Module ID Restrict by a sub_module_id.
Menu ID Prevents a page being displayed. While hiding a menu_id is possible in Menu tables, the data is replaced with system update. Hence it is necessary to keep the hidden menus as company specific and not lost by system update.
Menu Related Page ID Related menus items on a menu_id and/or table_name can be disabled/hidden.
Entity Table Name A table_name on all pages OR on a page (by specifying a menuId) can be hidden.
Field Name A field on all pages OR on a table OR on a menu OR module_id, sub_module_id, provider_id or combinations of them can be hidden. If the field is nullable hidden_edit, hidden_read will be set to true. If not nullable, hidden_read will be set true, and hidden_edit will be false.
Provider ID An end-user can be auto-determined as who the provider is. If a company has multiple providers in their setup, the objects can be further be restricted for a provider. This feature is yet to be implemented.
Site Restriction Comments A short explanation of what that Site Restrictions is created for, what it will do.