All Collections
System Updates
Update 13th March 2020: Single Sign-On, Incident Checklists
Update 13th March 2020: Single Sign-On, Incident Checklists
Charlie Vaughan-Fowler avatar
Written by Charlie Vaughan-Fowler
Updated over a week ago

This update sees some changes that have been a long time in the making and it is one we are particularly excited about. 

SINGLE SIGN ON (and a whole new way of logging in...)

The way that you login to WeTrack is changing. We have upgraded our authentication and login service to a more secure, single-sign-on (SSO) version which means that you will now login to all your WeTrack accounts using the same username and password*. You can still retain different permissions and preferences in those accounts, but will be able to switch between your accounts easily and without having to login again. 

*NOTE: Single-Sign-On (SSO) only works across WeTrack accounts for which you use the same email address. If you have different email addresses for different accounts, you would need to login to these separately.

What will happen when you login

When you login for the first time in this new way, you will be asked to confirm or update your password. The password you choose here will then be applied across all your WeTrack accounts. You may need to update an old password to match the stricter password rules that are now applied - details of these rules can be seen on this password confirmation screen, which will look like this:

Switching between WeTrack accounts

If you are already logged in to a WeTrack account, you can quickly switch to other accounts by clicking Switch Account below the Account Logo in the left hand menu. 

This will open the Account Switcher shown below. You will be presented with a list of the accounts you have access to. Simply click on any account to access it:

Incident Checklists

You will now be able to create checklists within incidents - items which need to be actioned to properly deal with and close out an incident. These checklists can be set up as templates in the settings area and associated with certain incident categories so that they become "playbooks" for how to deal with incidents of certain types.

When you then create an incident of a certain category, you will be offered the opportunity to add the checklist associated with that category of incident.

This checklist will then be added to the incident and items can be assigned to different users. As items are checked off, these changes are logged and timestamped in the incident's history as a record for future audits, etc. There is also the option to star items on a checklist template or within an incident itself - this will prevent the incident from being closed until starred checklist items are marked as complete.

Other Updates

Among the many other improvements, new bits of functionality and bug fixes included in this upload, here are some highlights:

  • Project Manager Notifications: Users can now choose to receive notifications for ALL items that are updated in projects for which they are project manager, whether tasks, risks or issues.

  • Additional changes on Incidents: log who the incident was reported by, breakdown clusters of incidents with the same location, archive items straight from the incident and log list, report on incidents from certain channels.

  • Several fixes to the settings area, especially around user and department management.

  • Fixes to date filtering on reporting, as well as to sorting between preview mode and PDF.

  • And much more!

As ever, please contact us with your thoughts and feedback through the chat widget or by email to [email protected] 

Did this answer your question?