punktde / inspectorvisibility
Neos package to configure the visibility of inspector elements using privileges
Installs: 5 752
Dependents: 0
Suggesters: 0
Security: 0
Stars: 4
Watchers: 6
Forks: 1
Open Issues: 1
Type:neos-package
Requires
- neos/neos: ^4.2 || ^5.0 || ^7.0 || ^8.0
This package is auto-updated.
Last update: 2024-10-15 14:37:24 UTC
README
This package allows you to configure the visibility of inspector elements, like properties, groups and tabs using policies. With that you can configure the visibility of these elements according to the users roles.
CAUTION: Although this is done with policies, this is not a security feature!
If you prevent a user from editing nodes, you aditionally need to define policies with an EditNodePropertyPrivilege
for example.
Installation
The installation is done with composer:
composer require punktde/inspectorvisibility
Usage
The matcher can be defined using standard eel. The following properties to match for are available:
- nodeTypeName
- tabName
- groupName
- propertyName
If no policy is matching for a role, the configured visibility is used. Same, if a permission is set to ABSTAIN
.
Examples
Example Policy.yaml
privilegeTargets:
'PunktDe\InspectorVisibility\Security\Authorization\Privilege\InspectorVisibilityPrivilege':
'PunktDe.InspectorVisibility:AdminFields':
matcher: "${tabName == 'meta' && groupName == 'nodeInfo'}"
roles:
'Neos.Neos:Editor':
privileges:
-
privilegeTarget: 'PunktDe.InspectorVisibility:AdminFields'
permission: DENY
Matcher Examples
- Adress all uriPathSegment properties:
matcher: "${propertyName == 'uriPathSegment'}
- Adress all meta tabs of all nodeTypes
"${tabName == 'meta'}"
- Address all title fields of a specific type
matcher: "${nodeTypeName == 'Neos.Demo:Registration' && propertyName == 'title'}"