You're done! Now, when you:ref:`call isGranted() with view/edit and a Post object<how-to-use-the-voter-in-a-controller>`,

your voter will be executed and you can control access.

Checking for Roles inside a Voter

..versionadded::2.8

The ability to inject the ``AccessDecisionManager`` is new in 2.8: it caused

a CircularReferenceException before. In earlier versions, you must inject the

``service_container`` itself and fetch out the ``security.authorization_checker``

to use ``isGranted()``.

What if you want to call ``isGranted()`` fomr *inside* your voter - e.g. you want

to see if the current user has ``ROLE_SUPER_ADMIN``. That's possible by injecting

the ``AccessDecisionManager`` into your voter. You can use this to, for example,

*always* allow access to a user with ``ROLE_SUPER_ADMIN``::

Next, update ``services.yml`` to inject the ``security.access.decision_manager``

service:

..configuration-block::

..code-block::yaml

..code-block::xml

..code-block::php

That's it! Calling ``decide()`` on the ``AccessDecisionManager`` is essentially

the same as calling ``isGranted()`` on the normal ``security.authorization_checker``

service (it's just a little lower-level, which is necessary for a voter).

..note::

The ``security.access.decision_manager`` is private. This means you can't access

it directly from a controller: you can only inject it into other services. That's

ok: use ``security.authorization_checker`` instead in all cases except for voters.

.. _security-voters-change-strategy:

Changing the Access Decision Strategy