User roles and permissions

User roles

User roles can be defined on customer demand. They can be high-level or detailed and specify the permissions a user account has. A user role is assigned to each account at its creation. For example, the user Marco Rossi, with an account on the username m.rossi can be assigned the role as Timetable planner, which indicates the permissions the user has. Each account has one or more user roles.

Permissions

Permissions are the individual actions a user role can perform. Permission include visualisation and writing permissions. An admin has full permissions. A timetable planner, doesn't have permission to see, write or change the scenario settings or to write or change the infrastructure model. He has permission to write and change the timetable in all scenarios.

Additionally, permissions can be limited by the status of objects. For example, even an admin user cannot delete trains which have been imported from a TMS.

User accounts

Each user must have an account. Accounts can not be transferred between persons. If an account is linked to a specific workstation, for example a dispatcher, which is used by different people in different shifts, each user must log out at the end of his shift.

The username of the account is used in the internal logs of trenoLive to trace modifications and give information about last edits and tasks triggered. The access to logs can be limited to specific user roles, e.g. Admins.