All permission objects registered by WinGate components are organized into a hierarchical tree by the Permissions system. This is to allow easy management and grouping of permission objects within their components, and for permission inheritance from parent to child objects.
Read more about the permissions tree
The inheriting of permissions plays a key role in the application and management of permission objects. Inheritance can be controlled from both parent permission containers and children permission objects depending on your requirements. There are two types of inheritance that parent containers can pass on to their children.
The Permissions system allows parent containers to inherit permissions from an upper level parent, and propagate these inherited permissions to all their child permission objects. This is regardless of whether the parent container is actually configured to use these inherited permissions themselves.
All parent containers have the Allow inherited permissions to propagate to children option which controls whether the inherited permissions they have received from their immediate parent further up the tree, are to be propagated through to their child permission objects. Deselecting this option will not affect explicit permissions that can be set on children from the parent container (See Explicit permissions on children below).
The parent container allows you to manually set explicit permissions that will be applied to all children in their container. Setting these explicit permissions will override any inherited permissions that children may have received through propagation.
Parent containers are set to use the inherited permissions from their immediate parent for their own permission settings by default. As with all permission objects, any inherited permissions can be cleared easily from the parent container by deselecting the Include inheritable permissions from parent option. Deselecting this option will remove any existing permissions settings and allow you to manually configure what permissions the parent will use and apply to itself.
Remember that permissions set explicitly for children in a parent container, will override any propagated permissions inherited by the children.
Deselecting the Allow inherited permissions to propagate to children option in a parent container will not affect explicit permissions that are set on the children by that parent.
Child permission objects inside parent containers will use any inherited permissions that they can receive by default. These can either be inherited permissions passed through from upper level parents via the Allow inherited permissions to propagate to children option set in their parent container, or explicit permissions that have been manually set on the children by their immediate parents.
Like all other permission objects, child permission objects also have the option to switch off the inherited permissions using the Include inheritable permissions from parent option. Deselecting this option allows you to remove any permissions that have been set by upper level parent containers either manually or by inheritance.
The propagation of inherited permissions from an upper level parent, through a parent container to their children, is automatic by default and can controlled in the permissions configuration of the relevant parent container.
Although permissions can be set on a granular, per child item basis, the users and groups affected by these permissions require at least a Read permission for the module parent container in order to see and access the appropriate feature, dialog etc. in the WinGate Management console.
You can use basic Full-Text Searches against the page title and body to find matching articles. Use the following search modifiers to refine your query:
