Enabling ICEFLO Communications
A Deployment Manager can amend which Comms are sent from ICEFLO about an Runbook they are the Deployment Manager for.
By default, Communications are switched off when a Runbook is created. This ensures Comms are not generated unless specifically required.
Enabling Communications From The Runbook
To amend a Users communication setting for a Runbook, from the ... More Options Menu, select Communications.
From the Teams panel, navigate to the Communications tab. You will see that the panel is split into 2 tabs, Users and Collaboration.
By default the listening community is everyone who is part of the Deployment Team, however interested parties can be added if required, from the Potential Users section via the add button.
Under the current users is the list of Users who would be receiving communications, you can see that both communications and escalations defaults are set to No, meaning the user will not receive communications. To change this so that user do receive the communications click into the field and change the No to a Yes.
If Notifications, Communications and Escalations are switched off at the Rubook level, users will be advised of this.
If Users see the above message, they should update the the Runbook level Communications, Notifications and Escalations from the Runbook Detail screen.
Who's Listening And Who's Not?
For both standard Comms and Escalations although the deployment manager may have enabled the Comms and Escalations for the User, they must also ensure that the users them self have these settings switched on.
As indicated above:
- Indicates listening or capable of receiving a message via SMS and/or email
- Indicates not listening or incapable of receiving a message via SMS and email
For this to be changed either the the user them self should update their own settings from the My Profile Dropdown, or a User who has User Admin rights can update the preferences from the User Domain.