Permissions determine what information an employee is able to view, edit and delete.
There are a few default permission profiles ready to be used and the first user is automatically assigned to Administrator profile with full permissions to the system.
Permissions are build for user roles. In order for these to work correctly, user hierarchy and business units must be correctly defined.
Employees must sign in again in order for the changes in permissions to become effective.
User hierarchy means the supervisor-employee structure. One person is always top of the hierarchy, meaning there is one person without supervisor (head of organization). All other users have supervisors. Many of the permissions are based on the relationship between supervisor and their employees. Verify that supervisors have been set correctly for all employees in User management to avoid any conflicts in permissions.
Business units can be used to limit permissions. In your organization you might call them companies, business units, departments, teams or perhaps even locations. Whatever the name, every employee and every project belongs to one. When you wish to limit access based on business unit, remember to check that all your employees and projects belong to correct business units.
Project membership together with Projects permission limit the visibility of projects. Every project has a project manager and project members. Only project managers are able to edit and invoice projects. To be able to enter work hours, user must at least be a member on a project.
Did you find it helpful?Send feedback