In WFDSS, there are system-wide user roles (e.g., Author, Viewer) and incident-specific privileges (e.g., Owner, Editor, Reviewer, Approver). Incident privileges are specific to each incident and determine what types of tasks a user can perform in support of the incident's documentation. For example; edit decision content, develop incident objectives and requirements, draw a planning area, or approve/publish a decision.
Incident privileges are assigned after an incident is created. When and whether you can assign incident-specific user roles depends on your system-level role:
Multiple Owners can assign incident-level roles to individuals or groups; however, at least one of the Multiple Owners must be an Author, GA Editor, or National Editor.
Each incident is assigned an owner or multiple owners. An Incident Owner can grant incident-specific privileges to other personnel (individuals or groups). When incident ownership is assigned to a group, an Incident Owner can add and modify roles for other individuals in the group, and delete ownership as needed. Incident Owners can also change incident ownership after declaring an incident out for reporting and analysis purposes.
-----------
Last updated on 8/14/2015 6:58:16 PM.
In This Section |
See Also |
Reference |
Incident owners are responsible for ensuring that the incident is accurately tracked and analyzed, and that decisions about the incident are properly recorded, reviewed, and approved.
Owners must meet the following criteria:
In addition, the following rules apply:
Owners have the following incident-level privileges:
-----------
Last updated on 2/28/2011 4:06:29 PM.
Incident Editors are responsible for assisting the incident owner in keeping the incident information updated.
Decision Reviewers and Approvers also can be Incident Editors.
Incident Editors must meet the following criteria:
Incident Editors have the following capabilities within the incident:
-----------
Last updated on 8/12/2011 3:21:17 PM.
Decision Reviewers are responsible for examining the documentation related to a pending incident decision, and indicating whether have reviewed the decision or are returning it for edits. If they return the decision for edits, they need to include comments and/or suggestions for edits.
Marking a decision as Reviewed does not mean that the decision is approved. A decision can only be approved by the Decision Approver(s).
Decision Reviewers must meet the following criteria:
While a Decision Reviewer can also be an Incident Editor, they cannot also be a Decision Approver for that incident. This incident privilege allows the Incident Owner to access specialists who might have specific input on a decision, but who do not have the fiscal responsibility for a decision that an Approver has.
-----------
Last updated on 4/21/2021 12:49:54 PM.
Decision Approvers are responsible for examining the documentation related to an incident decision, and indicating whether they approve the decision or are returning to it for edits. If they return a decision for edits, they need to include comments as to why they rejected the decision.
Approving the decision adds it to the system of record for the incident. Once the decision is approved, it can't be altered.
All designated Decision Approvers for an incident must approve before it becomes part of the system of record (e.g., if the incident is multi-agency, the designated Decision Approver from each agency must sign off on the decision).
At least one Approver must complete the periodic assessment when it is due.
Decision Approvers must meet the following criteria:
While Decision Approvers are automatically granted editing privileges for the incident, they cannot also be decision reviewers for that incident.
-----------
Last updated on 1/30/2018 11:30:07 AM.