@@ -26,7 +26,7 @@ uses the authorization checker), or by
2626
2727Ultimately, Symfony takes the responses from all voters and makes the final
2828decision (to allow or deny access to the resource) according to the strategy defined
29- in the application, which can be: affirmative, consensus or unanimous .
29+ in the application, which can be: affirmative, consensus, unanimous or priority .
3030
3131For more information take a look at
3232:ref: `the section about access decision managers <components-security-access-decision-manager >`.
@@ -262,7 +262,7 @@ checks if the user is a member of the site and a second one that checks if the u
262262is older than 18.
263263
264264To handle these cases, the access decision manager uses an access decision
265- strategy. You can configure this to suit your needs. There are three
265+ strategy. You can configure this to suit your needs. There are four
266266strategies available:
267267
268268``affirmative `` (default)
@@ -274,7 +274,11 @@ strategies available:
274274``unanimous ``
275275 This only grants access if there is no voter denying access. If all voters
276276 abstained from voting, the decision is based on the ``allow_if_all_abstain ``
277- config option (which defaults to ``false ``).
277+ config option (which defaults to ``false ``);
278+
279+ ``priority ``
280+ This grants or denies access by the first voter that does not abstain,
281+ based on their service priority;
278282
279283In the above scenario, both voters should grant access in order to grant access
280284to the user to read the post. In this case, the default strategy is no longer
0 commit comments