The following roles are standard for every Klaxon subscription.
Administrator – this role can perform operational administration, including User management, Service List management, and Location Management.
Major Incident Manager – this role can add, edit, update and delete major incidents.
Mass Notification Manager – this role can add, edit, update and delete mass notifications.
Planned Maintenance Manager – this role can add, edit, update and delete planned maintenance items.
Subscriber – this role can access the Klaxon web dashboard, Smartphone app and view/receive major incidents, mass notifications and planned maintenance.
Additional roles can be created by the Klaxon Support Team (email@example.com) to suit organisational need such as achieving segregation of duty.
Almost any feature/functionality can be associated/disassociated with a role, providing significant flexibility.
Templates can be associated with specific roles by the Klaxon support team (firstname.lastname@example.org), so they are only visible to that role. Please get in touch if you require this.
Klaxon supports three forms of workflow:
Approval of notifications. With approvals, you can designate a role (including custom roles that you create) that will receive and approve Klaxon notification requests before they are sent. This allows you to separate the responsibility for creating the notifications and approving them.
Alternative Delivery Channels – this is used with the major incident module and allows you to designate alternative delivery channels if a major incident impacts a delivery channel. For example, if you have a subscription called Outlook, and there’s a major incident affecting Outlook, it is undesirable to use email to notify recipients about the problem. So, in this case, another recipient notification channel can be used, such as Microsoft Teams.
Next update – Klaxon can issue reminders that an update is required for a major incident, when the ‘Next Update Time’ is about to elapse, and when it has elapsed. Reminders can be sent to specific roles.
The Klaxon support team configures workflow. Please email your requirements to email@example.com.
You can configure Klaxon to ask recipients to accept a set of terms and conditions the first time they log into Klaxon. This is useful for covering your policy around personal data, and in particular, if you intend to ask people to input their personal mobile number.
If the recipient does not accept the terms and conditions, they will not receive any notifications in the future.
You can see if/when a recipient accepted the terms and conditions or not in the individual user record (go to Configuration->Users).
Klaxon supports several integrations with third-party products.
SAML/OAUTH2 allows you to log in to Klaxon via a third-party identity solution such as Microsoft Azure Active Directory or Okta.
If configured correctly, the Klaxon login process can be fully automated when logging on from a corporate domain-joined computer. This offers the best ‘end-user’ experience since there is no need to enter the email address or password to log in.
Klaxon will soon support a fully featured integration with ServiceNow:
When you create a major incident in ServiceNow, a major incident will be created in Klaxon, which will trigger sending the notifications.
When a recipient clicks on an action response button, such as I’m affected, a child incident will be created in ServiceNow. This allows administrators to understand better who has been impacted by an incident.
Klaxon will soon add Slack as a recipient notification channel. You will be able to send Klaxon notifications to Slack users/channels using Klaxon.
Klaxon will soon support inbound and outbound webhook functionality. This will allow administrators to integrate with third-party monitoring solutions and service management systems.