title: Extending Phalcon ACL
body: <p>The current ACL of phalcon is managing access between <strong>roles</strong>, <strong>resources</strong> and its <strong>actions</strong>. For example, if we want to allow specific role into specific resource :</p>
  
  <pre><code>$acl-&gt;isAllowed("Guests", "Customers", "search");
  </code></pre>
  
  <p>This check if role called "Guest" can access "Customers" controller for action "search". 
  In my scenario, we also have "Role Level", for example, Admin can access all modules and controllers, but, to modify the contents, an Admin should have minimum Role Level 2. To gain access to modifying website configuration, an Admin should have Role Level 3. </p>
  
  <p>In addition to role level, we also want to assign which models a role can have access to. For example, Mr. A and Mr. B both are Admins and have same levels. But, we decided only to allow Mr. A to access "Accounts" models while Mr. B can have access to "Accounts", "Personnel", etc.</p>
  
  <p>Here are my questions :</p>
  
  <ol>
  <li><p>Does phalcon ACL support roles and levels ? Or, should I just create the custom validation?</p></li>
  <li><p>What is the benefit of using ACL compared to creating similar validation functions?</p></li>
  <li><p>If I have to create custom validation, where should I put it ? In the controller, or in the dispatcher ?</p></li>
  </ol>
  
  <p>Thx</p>