Email: support@elma-life.eu

List of users

The administrator of eLMA in your Organization has the right to grant rights to application for any user (the user does not need to be an employee of the beneficiary). Granted rights to view and modify the data stored in the application reflect the level of competence in the project or in your organization. The user is not always an employee, but the employee is always a user.

Creating user profiles and giving them the appropriate permissions enables granting different levels of access, for instance without access to sensitive or confidential information (for example: time sheets of other team members). It also allows you to differentiate rights depending on the position occupied by the employee in the organization. it means, for example, lack of access to costs and time sheets of other employees for junior staff, but full access to costs and time sheets for all employees or chief accountant.

Create a user profile by indicating the email address as a user name (login) and a password. The user name is associated with the name and surname of the person. In the next step, mark the corresponding checkbox on the right-hand side (checking the box means giving permission). Rights are divided into modules and to edit/read only rights. User rights in each of the modules can therefore vary.

Using buttons ‘grant all’ and ‘deny all’ we can change the information immediately in all fields.

Additional privileges are: accessibility to timesheets of other employees and ability to approve them. This option is intended for employers or accounting/HR staff, who are entitled to access sensitive and confidential personal information.

Admin Coordinator Manager Employee Guest (read-only)
Employee list All Within organization – edit,

within the project – read

Within organization Within organization Within the project
Personal cost list All Within organization – edit,

within the project – read

Within organization Only own Within the project
Timesheet view All Within project Within organization Only own Within project
Timesheet approval All Within organization Within organization None None
Configuration views (configuration, projects, users) All Within project Within organization None Within project
Add/remove users All None None None None
Modify users All Within organization, without changing access profile Within organization, without changing access profile Can change only itself (e.g. update password) None
LIFE financial statement All Within project Within project Without personnel Within project

When you specify a list of users with access to the application, enter project configuration data starting from ⇒ the financing shares.

157