Incident Privileges are specific to each incident. From the Incident Privileges menu option, Incident Owner(s) assign and manage incident-level privileges for incidents they own. From this location, decision Approvers, if they are also incident Owners, can manage their preference with regard to system-generated, periodic assessment-related emails as well.
Incident Owners can perform the following tasks from the Incident Privileges menu option:
When assigning privileges to a group (it may be helpful to create that group if it hasn't already been created) in your personal WFDSS address book before you begin. Groups can help you quickly locate individuals you regularly work with on incidents.
WFDSS automatically generates an email to individuals you assign privileges to, notifying them of the change. Emails are automatically generated for this purpose in both Training and Production.
Incident Approvers can perform the following tasks from the Incident Privileges menu option, if they are Incident Owners:
When an Incident Owner assigns additional owners, the email box will automatically be checked beside the Owner's name. This indicates that the Owner will be opted in to receive emails when periodic assessments have been completed and when decisions are published. Owners can uncheck the box if they choose to opt out of this option.
When an Incident Owner assigns one or more approvers, the Email box will automatically be checked beside the selected Approver's name (as well as the Edit privilege). This indicates that the Approver(s) will receive an email alerting them that the periodic assessment is due or overdue. This feature is not enabled in Training, as Approvers are not alerted of due or overdue assessments in this system.
At least one Approver must receive the email, but other Approvers can opt out, as mentioned above. WFDSS will not allow all Approvers for an incident to opt out of receiving the email; WFDSS will 'reset' the incident overnight and automatically select each Approver to receive the email.
An Incident Owner can grant Edit, Review, and Approve incident privileges to:
The following is a breakdown of each privilege:
When you grant incident privileges to a group, each member of the group will receive incident privileges. For example, you may want to give Edit privileges to a group comprised of coworkers that you created in your personal WFDSS address book. If you subsequently change the group, the members who belonged to the group when you first granted the privileges will retain those privileges. To remove privileges for an individual, you must go through the Incident Privileges menu option, query the user's name, and unselect the checkbox for each privilege you want to revoke.
If you are working in Training and want to keep incident privileges to yourself, you can grant yourself incident editing and approving privileges and publish a decision without assistance from others. You cannot assign yourself Review privileges however; you can should assign those to another WFDSS user when you want to explore the Review privilege and the effect it has on decision publishing.
Incidents can be owned by one or more users assigned the role of Author, GA Editor or National Editor. Users with the owner role manage the development of a decision and can submit a decision for review and eventual publishing. They can also grant Incident Ownership to or share ownership with:
In addition, a user assigned the role of Author, GA Editor or National Editor can accept ownership of an incident if it has no owner. When multiple owners own an incident, each owner can add, manage and/or edit personnel assigned to assist with documentation. Changes in incident ownership can occur before or after declaring an incident out for reporting and analysis privileges.
Caution: Limit the number of people who have editing access to the incident. While each incident is different, at a certain point, it can become a situation of "too many cooks in the kitchen", and it's important to ensure that the people reviewing and approving the decisions have the correct level of authority. Limit the number of people who have editing access to the incident. While each incident is different, at a certain point, it can become a situation of "too many cooks in the kitchen", and it's important to ensure that the people reviewing and approving the decisions have the correct level of authority.