Permissions determine what information an employee is able to view, edit or delete in Severa. Permissions are centrally managed using ready-made permission profiles, but they can also be edited at the permission level through the user's profile.
When a new user is created in the system, they are automatically assigned the organization's default permission profile. Permission profiles are managed under the gear icon Permission profiles. Please note that the first Severa user will always automatically become the Main user with full rights to the entire system.
Defining and editing permissions
Permissions can be managed from the user's profile. Changes can only be made by a person with sufficient rights to the Users section. For security reasons, a user cannot edit their own permissions. A user cannot assign another user a permission level that is higher than their own.
If a user's permissions are changed, they must log out of the system once and log back in for the new settings to take effect.
Recommended management method
- Primarily use ready-made permission profiles according to the company's personnel structure.
- Management through profiles is efficient: when you change the permissions of a profile once, the change is updated for all users belonging to that target group.
- Main user can edit profiles to precisely meet the company's needs.
Factors affecting permissions
Permissions are not solely based on the selected profile. Information stored in the user's employment contract also affects what they see in the system. When creating a new user, ensure that the following points are filled in correctly:
User hierarchy
User hierarchy means the supervisor-employee structure. Many permissions (such as work hour approval) are based on this relationship.
- Every user (except the top person in the organization) must have a supervisor defined in the employment contract.
- Verify the correct hierarchy through User management to avoid permission conflicts.
Business units
Business units (e.g., departments, teams, locations) are used to limit visibility geographically or organizationally.
- All employees and projects always belong to a business unit.
- When restricting permissions based on business units, check that both the user and the project are placed in the correct business unit.
Project membership
Project membership and Project permission define which projects a user can handle.
- Only project managers can edit project information and handle billing.
- The user must be at least a project member to add hours to the project.
Did you find it helpful? Yes No
Send feedback