Provides a way to configure permissions for frontend applications in data objects.

Installs: 31 677

Dependents: 0

Suggesters: 0

Security: 0

Stars: 15

Watchers: 13

Forks: 9

Open Issues: 0


v1.5.1 2021-07-21 07:54 UTC

This package is auto-updated.

Last update: 2023-01-13 10:51:54 UTC


Adds some helpers to define permissions for users in websites based on Pimcore objects. So user permissions for complex systems can be defined directly in Pimcore objects.

A scenario to set up a role based permission system:

  • user represented as objects with a number of permission rights (= Permission Resources)
  • each user has relations to user groups (also Pimcore objects) with also a number of permission rights (= Permission Resources)


Installation instructions

  1. Inside your pimcore project require the bundle as a dependency:

    composer require pimcore/frontend-permission-toolkit-bundle
  2. Enable the bundle using the CLI command:

    bin/console pimcore:bundle:enable FrontendPermissionToolkitBundle

This will enable & install the bundle in your pimcore project as well as run the assets:install command. Alternatively you can log in to your admin area go to Tools > Extensions and enable the bundle from the list by clicking on the appropriate icon.

Functionality overview

  • Additional data types for Pimcore objects

    • Permission Resource:
      • represents one specific user right (e.g. login)
      • can have values allow deny inherit
    • Dynamic Permission Resource:
      • represents a set of specific rights for a user
      • each entry can have values allow deny inherit
      • actual permission resources are defined by a data provider
        • defined in the class definition, either defined by class name or service name with leading @
        • data provider class needs to implement DataProviderInterface and return an array of roles and labels:
        public function getPermissionResources(array $context, \Pimcore\Model\DataObject\ClassDefinition\Data $fieldDefinition): array
            // static example for explanation
            return [
                ['value' => 'testpermission_1', 'label' => 'Permission for test'],
                ['value' => 'testpermission_2', 'label' => 'Another Permission for test'],
    • Permission ManyToMany Relation: Wrapper for default data type objects for recursive permission calculation.
    • Permission ManyToOne Relation: Wrapper for default data type href for recursive permission calculation.
  • Service for checking user rights based on a Pimcore object and a permission resource as service class Service with two methods:

    • Service::getPermissions:
      • returns an array of all permissions for the given object, automatically merges all permission resources of objects related to the given object with 'Permission Objects' or 'Permission Href'.
      • merging: When permission is set to allow / deny directly in object, this is always used. Otherwise optimistic merging is used -> once one permission is allowed, it stays that way.
    • Service::isAllowed: checks if given object is allowed for given resource

The Service is registered at the container with the key bundle.frontendpermissiontoolkit.service.

Event listener

The postGetPermissions event listener allows you to manipulate the permissions after they have been collected. Take into account that the getPermissions method can be executed recursively. Therefore, make sure you add an object condition.

namespace AppBundle\EventListener;

use FrontendPermissionToolkitBundle\Event\PermissionsEvent;
use Pimcore\Model\DataObject\User;

class PermissionsListener
    public function postGetPermissions(PermissionsEvent $permissionsEvent): void
        // Object the permissions are retrieved for
        $user = $permissionsEvent->getObject();
        if (!$user instanceof User) {

        // Access service methods to retrieve additional permissions and merge them
        $service = $permissionsEvent->getService();

        $permissions = $permissionsEvent->getPermissions();
        $mergedPermissions = $permissions;
        foreach ($user->getGroups() ?? [] as $userGroup) {
            $userGroupPermissions = $service->getPermissions($userGroup);
            $mergedPermissions = $service->mergeNestedObjectPermissions($mergedPermissions, $permissions, $userGroupPermissions);

        // Update the permissions to return them from the service method
            - {
                name: kernel.event_listener
                event: frontendPermissionsToolkit.service.postGetPermissions
                method: postGetPermissions

Integration with Symfony Security

For how to integrate Pimcore objects with Symfony Security in general have a look at Pimcore docs.

In order to use Permission Resources in Symfony Security definition, you could export each allowed Permission Resource of an Pimcore object as role.

To do so, add the trait FrontendPermissionToolkitBundle\CoreExtensions\Traits\PermissionResourcesAsRolesTrait to your Pimcore user object and make sure there is no other getRoles method defined in the object. This method returns all Permission Resources the user is allowed prefixed with GROUP_ to as an array.

As a consequence, you can use Permission Resources in your access control configuration as follows:

        - { path: ^/special-offer-page, roles: ROLE_offer }

Note: To apply changes of permissions in the user object, the user has to logout and login again.

Integration with Pimcore navigation

To show/hide documents in navigation, you can assign Permission Resources as properties to Pimcore documents. Just add a property named permission_resource with name name of the permissionResource as value to the document.

Permission Property

A special navigation builder shipped by this bundle (FrontendPermissionToolkitBundle\CoreExtensions\Navigation\Builder) then can show/hide documents in navigation based on the permissions of the current user.

To do so, add following service definition to your application:

    class: FrontendPermissionToolkitBundle\CoreExtensions\Navigation\Builder
    arguments: ['@pimcore.http.request_helper']
    public: false
      - [setService, ['@bundle.frontendpermissiontoolkit.service']]
      - [setCurrentUser, ['@security.token_storage']]

Make sure that you deactivate the caching of the Pimcore navigation creation!

This only hides the document in navigation. It does not check permissions when the document is called directly via its url. Add an additional check into controller or access control to make sure the document cannot be called with missing permissions.