The goal is to limit the module/action access by roles.


It begin by the preparation of the models/ontology/funcacl.rdf by extension, describing each public method (action) accessible by class (module).

The script to generate the files for all extensions is tao/scripts/taoPreparePublicActions.php calling class.TaoPreparePublicActions.php.

It must be called each time a class/method is created or deleted.

The manifest of each extension introduce the funacl.rdf file and install it. It’s followed by other rdf file like aclrole.rdf giving basic access for this extension.


Once installed, it starts in tao/include/class.AccessControlFC.php called by the bootstrap checking your access to the uri targeted. Extension, module and action is checked.

The control is made by the helper tao/helpers/funcacl/class.funcACL.php :: hasAccess method. It retrieves the roles of the current user and adds, even if not logged in, a base access control role (CLASS_ROLE_BASEACCESS) giving the access for logging and basic access like that. This is valid for all 3 kinds of login


For optimizing the access to the database (processing ~+5000 records), it create a file (tao/data/cache/RolesByActions) structured for giving a fast answer to the “hasAccess” request.


An interface exists to give access for the entire module or a specific action in the user management. It’s more for a developer than user by the way it shows methods and classes (actions/modules).

It’s hidden! To activate it, in the structures.xml of TAO add this line

The interface shows the roles, select one to display modules by extension, showing directly what’s selected, partly selected or not selected. Click on a module to display the actions, showing what’s selected or not and at the bottom of this list, a way to select all (access by module) even if the module is modified (new action or less).

Edit a user to attach a role.