The available roles in the application are defined through the used roles in the ACL table.
Beside of ACL table and the right system in some circumstances the users roles are directly checked for the roles a user have.
For that reason for each available role a PHP constant is set: ACL_ROLE_ROLENAME
By default this roles are available:
'admin', 'api', 'basic', 'editor', 'instantTranslate', 'noRights', 'pm', 'termCustomerSearch', 'termProposer'
|frontend||resource for general frontend rights|
|loadAllTasks||with this resource the role is able to see all tasks (should be converted to a right in the resource backend)|
|adminUserFrontendController||giving a role this resource, enables the admin GUI (should be converted to a right in the resource backend)|
|headPanelFrontendController||giving a role this resource, enables the head panel (should be converted to a right in the resource backend)|
|userPrefFrontendController||giving a role this resource, enables user specific settings (should be converted to a right in the resource backend)|
|taskOverviewFrontendController||giving a role this resource, enables the task overview (should be converted to a right in the resource backend)|
|editAllTasks||with this resource, the user can edit a task without beeing associated with it. Frontend Right editorEditAllTasks is also required (should be converted to a right in the resource backend)|
|getUpdateNotification||with this resource the user gets a notice if a new translate5 version is available (should be converted to a right in the resource backend)|
|readAuthHash||with this resource the user is able to see the authHashes in the TaskUserAssoc entity (API usage) (should be converted to a right in the resource backend)|
|backend||resource for general backend rights|
|setaclrole||resource for define if the user can set/change acl role|
ACL rights and description
In this table you can find some useful acl rules/rights/resources and also description which functionality they are providing inside the translate5.
In translate5 frontend and backend you are able to define which user roles can be modified/created to other users.
The 'setaclrole' is defined as a new resource in "application/modules/editor/configs/aclConfig.ini" file.
Insert new record in the table if you want to extend the user capabilities for creating/modifying acl roles to other users.
For each role combination a separate record in the table is needed.
|editor||frontend||editorChangeUserAssocTask||Enable and disable the User Task association tab in task preferences window.|
|editor||frontend||editorWorkflowPrefsTask||Enable and disable the Workflow properties tab task preferences window.|
|editor||frontend||editorPreferencesTask||Enable and disable the 'Task Properties window' button in task grid.|
|editor||frontend||editorEditTaskTaskName||Allow pm user to modify taskName in task.|
|editor||frontend||editorEditTaskDeliveryDate||Allow pm user to modify deliveryDate in task.|
|editor||frontend||editorEditTaskRealDeliveryDate||Allow pm user to modify realDeliveryDate in task.|
|editor||frontend||editorEditTaskPm||Allow pm user to modify taskPm in task.|
|editor||frontend||editorEditTaskOrderDate||Allow pm user to modify orderDate in task.|