Risk Register¶

The Risk Register is the main portfolio list. It shows every risk you are allowed to see. For most people that means every submitted risk except those marked confidential or restricted to a department (see Who can see a risk).

Choose a view¶

• My Risks — risks associated with you.
• All Risks — every risk you are authorized to view.
• Watched — risks you are following.
• Kanban — the same results as cards on a board, grouped by workflow phase, rating, business unit, or owner.

Use the Views menu to save your current filters and layout under a name so you can return to them later. Give shared views a name that explains the business purpose, such as “High risks awaiting treatment approval.”

Rejected risks are hidden by default because they are no longer active. Tick Include rejected to show them.

If you have the export permission, Export downloads the current filtered list as CSV or Excel.

Search and filter¶

1. Open Risk Register.
2. Choose the view that best matches your task.
3. Enter a title, RR number, or description text in Search. Search text longer than 200 characters is truncated.
4. Add filters such as workflow status, rating, likelihood, impact, SLA state, linked-asset sensitivity, or deleted records.
5. Review the active-filter chips above the results.
6. Remove one chip to broaden the result, or clear the filters to start over.

Filters apply to the entire matching result set, not only the visible page.

Risk owner, business unit, and aging-bucket filters can't be chosen from the filter panel yet. They are applied when you open the register from a Dashboard SLA queue, and you can remove them like any other filter chip.

Image needed: Risk Register with the view selector, search box, filter panel, active-filter chips, and results table labeled.

Use row actions¶

The action menu shows only what you can do:

• View opens the authoritative Details page.
• Edit opens the workflow-aware editor.
• Delete permanently deletes your own draft. For a submitted risk it performs a soft delete, which hides the risk from the register. A submitted risk can be deleted only after it has been closed and the organization's retention period has passed, and never while a legal hold applies (see Deleting and restoring risks).
• Restore brings back a soft-deleted risk.

The table can also show workflow state, rating, owner, dates, linked-asset sensitivity, and configurable columns.

Target Date, SLA deadline, and Overdue¶

Two of the register's dates sound alike but measure different things:

• Target Date is the date your team is aiming for. Someone typed it in.
• SLA Status is measured against a separate, automatic SLA deadline that the workflow sets for the state the risk is currently in.

Because they are different clocks, a risk can show a Target Date next week and still be marked Breached today. The SLA deadline itself appears on the risk's Details page and in My Work Items' All overdue treatments tab.

The Target Date column stays in plain text rather than turning red, because red there would suggest the target had been missed when what is actually late is the current workflow step. The Overdue column reflects the SLA clock. A dash in SLA Status means no SLA applies to that risk's current step; it isn't a problem.

Preview a risk without leaving your view¶

In the Kanban view, select the eye icon on a risk to open a quick summary panel. It follows the same access rules as the full Details page and includes a link to the complete record. Quick view is also available beside risk results in the Ctrl+K search window, and by selecting a risk's ID on the All work tab in My Work Items.

Perform a bulk action¶

Authorized users can update multiple risks together. Available bulk actions include delete or restore, assign owner, assign resource, set a due or review date, run a common workflow transition, add a tag or category, archive, and assign a legal hold (for users who manage legal holds).

1. Apply filters until the result set contains the intended risks.
2. Select individual rows, or select all records matching the current filter.
3. Choose the bulk action.
4. Select Preview.
5. Review which risks are eligible and which will fail.
6. For an assignment, enter a Reason if the preview says any selected risk needs one.
7. Correct the selection or continue with the operation.
8. Review the final result report and download the error CSV when offered.

Permissions and workflow prerequisites are checked separately for every risk. Partial success is possible.

Bulk submit¶

A bulk Submit behaves exactly like submitting one risk. If automatic reviewer assignment is on, each submitted risk is handed to the next reviewer in turn. If no reviewer can be assigned, the risk still counts as submitted, and its row in the result report explains why so you can assign one by hand.

Bulk assignment¶

Assign owner checks once, up front, that the person you picked can take on risk ownership (see Who can be a risk owner). If they aren't eligible, nothing changes and you're told why, instead of every row failing separately.

Assign resource changes any of the five people fields, not only the owner. It is available only when an administrator has enabled resource reassignment (see Change who is assigned to a risk).

Assignments have three extra rules, all aimed at not overwriting someone else's work:

• Run Preview first. Preview records the version of every risk it examined, and Execute uses those versions to confirm nothing changed in between. Going straight to Execute is refused with a prompt to preview.
• Give a reason when work is already under way. Preview tells you whether any selected risk needs one. Risks still in their setup window don't.
• Closed, Archived, and Rejected risks are refused, as are approvals that have already been recorded. Those rows come back as failures with the reason; the rest of the batch still goes through.

Bulk delete¶

In a bulk delete that mixes your own drafts with submitted risks, the drafts are deleted permanently and the submitted risks are soft-deleted as usual. The preview shows which is which.