The responsible list is now easily maintained at one place for all your registrations within the project. Read more about these changes, and news in notifications under:

Responsible lists

• Now the responsible lists in issues and registrations will solely be updated from the list of user groups, this instead of maintaining the list on each registration type.
• Check "Responsible" on the user group and this group becomes available as a choice in "Responsible".

For all current projects we will do a check on each registration type and make sure that all user groups used as responsible today will be marked as "Responsible" in the user group list. Responsible used on different registrations will now be available cross all registration types.

Notifications simplified

For an easier setup, the notification functionality is splitted into two, while new functionality have been added in a third:

• Responsible notifications
• Owner notifications
• Custom notifications (new)

These will be used for all new notifications. Any current setups will be displayed in the notification list as a fourth type called "Classic Notifications".

Custom Notifications

Custom notifications are a powerful setup that enables notifications based on any input field(s) within registrations. An example is adding notifications for different a Severity levels, based on the value picked up from "Severity"-field in the Incident registrations.

Project templating

As the new notifications and responsible lists updates also is available in your project template (configuration), this opens up for shortening the time it takes to start and setup a new project.

In your template you can define discipline/groups with defined permissions and notifications on the project template level (configuration). When you start your project, you simply rename each discipline to the responsible sub-contractor/group participating in the project.