Skip to main content

Managing your action plan registers: creation, merging, visibility

Learn how to create, merge, hide, and delete an action plan record, and how to make it visible to the relevant perimeters

An action plan register is the container that groups and organizes your actions around a common theme: an audit, a compliance project, a pentest, a remediation campaign, etc.

This article covers the possible operations on a register:

Create a register

  • In the left navigation bar, go to the Action Plans module.

  • Click "+ Add plan". A modal opens. Fill in the register's information:

    • Name: the register's title (e.g. ISO 2025 audit remediation plan)

    • Group / perimeter: the register's affectation, which determines access rights. The "visible to everyone" option lets you display this action plan to all your users, within which they will then only see actions from their own perimeter.

    • Description: context or purpose of the plan (optional)

  • Click "Save". The register appears in the action plan list and is ready to receive actions.

💡 A register can group actions from several perimeters, provided those perimeters are compatible with the register's affectation: they must be at the affectation level or below.

For example, an action plan assigned to France can contain actions from Grenoble, Paris, or Toulouse, while an action plan assigned to Grenoble can only contain actions from Grenoble.

A single action can also belong to several registers at the same time.

Merge several registers into one

This operation relies on an export followed by an Excel import. It's useful for consolidating several existing registers, or for adding a batch of actions from one register to another.

Step 1: Create the destination register

Create the register that will receive the consolidated actions (see the Create a register section above), or choose an existing register as the destination.

Step 2: Export the registers to be merged

For each source register, go to Action Plans, click the relevant register, then click "Export XLS" in the double-arrow menu.

⚠️ By default, actions with the Finished or Cancelled status don't appear in the export. If you want to include them in the merge, change the Statuses filter in the filter bar before exporting:

Step 3: Import each file into the destination register

Open the destination register and click on "XLS Import" in the double arrow menu. Select the XLS file exported in the previous step and confirm. Repeat this operation for each source register to be merged.

💡 If an error occurs during import, you can correct the XLS file and re-import it.

Hide and unhide a register

Hiding a register lets you archive it once it's finished, while keeping the actions it contains for traceability purposes. A hidden register is no longer shown by default in the action plan list.

Hide a register

In the action plan list, click "Hide" in the 3-dots menu of the relevant register:

Show hidden registers

To find a hidden register, check the "Show hidden" box at the top of the action plan list:

Unhide a register

From the list (with "Show hidden" checked), click "Unhide" in the 3-dots menu of the relevant register to make it visible again:

Delete a register

⚠️ If the deleted register is the only register an action belongs to, that action is permanently deleted along with the register. If the action also belongs to one or more other registers, it is simply removed from the deleted register and remains accessible in its other registers.

In the action plan list, open the 3 dots menu of the relevant register. Select "Delete", then confirm the deletion.

🔎 A transverse register (assigned to a grouping or to the root) can also be made visible to the relevant local pilots and auditors, while preserving the confidentiality of each perimeter's actions. To understand this option, see Making an action plan visible to everyone.


Frequently asked questions

Can I merge registers belonging to different perimeters?
Yes, provided the actions' perimeters are compatible with the destination register's assignment, meaning at the assignment level or below. For example, a register assigned to France can group actions from Grenoble, Paris, or Toulouse. A register assigned to Grenoble, however, can only contain actions from Grenoble. Export/import works according to this same rule.

What happens if I delete a register that contains actions also present in another register?
Those actions are not deleted: they remain accessible and manageable from their other register(s). Only actions that don't belong to any other register are permanently deleted.

Does a hidden register remain visible to other users?
No. Hiding is not a personal setting: it applies at the register level, the same way for all users with access to that assignment level. No one sees it in the list while it's hidden. It remains accessible at any time by checking the "Show hidden" display option.

What's the difference between hiding a register and making it "Visible to everyone"?
These are two distinct mechanisms. Hiding a register archives it so it's no longer shown by default in the list. "Visible to everyone," on the other hand, extends access to a cross-cutting register to local pilots and auditors who wouldn't normally have access to it: see the dedicated article for more details.

Can I undo a merge after import?
There's no automatic undo function. If you make a mistake, delete the imported register and start again with a corrected XLS file.

Did this answer your question?