Groups, editing many items, importing and undo

Help centre › Registers: risks, controls, systems

Groups: drag items onto a group, in the hierarchy or in the grid, to put them in it; drop them on New group to make a group of them. Or pick them and choose Move or Group. Drop on All … to lift items back to the top.
Many at once: tick rows (or Ctrl/⌘-click, Shift-click, or Pick all that match), then set a field, move, group, make active or retire them together.
Edit in place: double-click a name or a field in the grid, or change it in the item’s panel. Changes save at once, without reloading the list.
Right-click a row (or the item’s panel, or its ⋯) to add an item under it, move it, group or retire it, or approve a proposal.
Where it is used: the processes that use the item, under their place on the process map, with the steps in each. Search it when the list is long.
Columns: click a heading to sort by it (any field), drag its edge to make it wider or narrower, and use Columns (or the arrow on a heading) to hide one. Your columns are remembered in this browser.
Import: Import a CSV or Excel file, map its columns (category columns build groups), check exactly what will change, then import.
Import into registers (Administration › Imports): CSV files, or an Excel workbook with a sheet per table. A file named after a register (risks.csv) goes into it. A row can also hold linked items: name the columns after their register (Risk: Name, Risk: Rating, Control: Name…) and each row creates both and links them (a control mitigates the risk). Rows about the same item count once, and importing the file again updates rather than duplicates.
Templates and mappings: Download template for the registers you pick gives a file the import reads by itself. For someone else’s file, Mapping… says which register and field each column goes to; admins save it under a name to use again, or from the API.
Reuse only (Fields and owners): for a register kept in step with another system. The AI only picks existing items and tells you when nothing fits; a risk or control a model defines for itself is flagged, with Propose it to the register to send it to the owners.
Owner fields take an email address, a name or a role title (as process owners do), so a file from a GRC tool can carry titles.
Retire with a replacement: the models that used the retired item can move to the replacement in one go.
Delete (right-click, or with rows ticked) removes items for good, with anything grouped under them, but only items no model uses: those you retire instead, so no model is left pointing at nothing. To clear a register, Pick all that match, then Delete.
Undo: every change is listed under Changes, and each can be undone; each item’s History tab shows what changed.
Fields and owners (admins): add your own fields, lists of options and the people who own the register.

More on registers: risks, controls, systems

Try it in the free demo, or contact us.