New guide: user rights management in TimeLog Project

Who are you? (In TimeLog Project)

A curious headline for a blog entry, but your system role defines your level of access in TimeLog Project. We’ve prepared a guide to explain the features available to you in the system.

If you’re a project manager, you have other rights than those of the CEO. Similarly, a system administrator is the only role that allows complete control of all system user rights.

Our new guide offers an overview of your level of access in the system depending on your role and responsibilities. For example, CEOs require access to more advanced reports than project managers, whose areas of influence are usually limited to the projects they’re currently working on.

The following TimeLog Project roles are covered:

  • External employee (time registration access only)
  • Project worker
  • Project manager
  • Account manager
  • Department manager
  • CEO
  • System administrator 

What’s your system role?

If you're unsure of your system role – and, consequently, your user rights and level of access – you can contact your company system administrator/super-user or go to System Administration > Permission control in the Employees menu group.


Permission Control


Seven system roles

In describing these system roles, we’ve focused on presenting TimeLog Project with all add-ons enabled, providing an overview of all user access rights. Each role description builds on previously described roles, meaning that e.g. all project worker rights apply to project managers as well. As such, project manager rights are based on the specific features available to them in TimeLog Project.

Using the guide

The guide is useful for determining whether there are features you use, but don’t fully exploit. Also, undiscovered features which might prove relevant for you now or later on may be covered. The guide is also intended as an aid for new employees, providing them with a sound introduction to the system and their user rights.

Alternatively, the guide can serve as a good starting point for employee interviews: do they have the right system role and, as such, user rights? Or have they recently been given new areas of responsibility, warranting a user-rights extension?


Not all features are covered, and not all screenshots are provided in the guide, as that would make it far too comprehensive. The most significant ones are, however, covered as are some of the most useful features to consider the needs of most of the employees. If you feel the guide is missing vital information, please don’t hesitate to contact us at

Thomas Ljungqvist

Thomas Ljungqvist
New Call-to-action