Adding a Register

Registers

What registers are, why they matter, and how to create and configure them in the Clew Platform

Contents

• 1. Introduction & Context
• 2. Key Features & Functions
• 3. Requirements
• 4. Step-by-Step Guide
  • Creating a Register
• 5. Common Issues & Troubleshooting
• 6. Related Articles

1. Introduction & Context

A register is a structured repository that organises and stores your data in the Clew Platform, much like a folder, so records can be categorised, retrieved efficiently, and protected with the right permissions.

The Registers section in Admin allows you to define the registers against which modules can be recorded. Registers work like folders and can be set up in a hierarchy, with child registers sitting under a parent. For example, an organisation might have a parent register for each division, with child registers for each department underneath, so risks and other records can be captured at the right level of the business.

Registers also provide robust permission management, ensuring sensitive information is accessible only to authorised individuals.

Who is it for? System Administrators who set up and manage the register structure for their organisation.

What does it impact? Registers determine how records are organised across modules and who can access them. Settings such as auto rollup and cascade policies affect how data is displayed on parent registers and how security group permissions are applied.

2. Key Features & Functions

• Structured data storage: registers act like folders, categorising records so they are easy to organise and retrieve.
• Hierarchy: registers can be nested under a parent register to mirror your organisational structure.
• Permission management: access to a register and its data is controlled through security groups, so sensitive information is only visible to authorised users.
• Auto rollup: optionally display all of a child register's information on its parent register page.
• Cascade policies: automatically apply the permission sets from the parent register's security groups to a new child register at creation.
• Library display: optionally show a register as a link under the Library menu on the top bar.

3. Requirements

• You must have admin access to reach the Registers section on the Admin page.
• To use the Sensitivity field, the sensitivity feature must be enabled for your organisation, and levels above the default must be assigned to users via Admin > User > Sensitivity.
• To use the Business Objective field, the Business Objective module must be in use and configured.
• The fields available on the register form depend on your organisation's configuration, so you may see additional fields not covered in this article.

4. Step-by-Step Guide

Creating a Register

1. Click Registers in the left bar of the Admin page. This takes you to the list of registers already available in the application.
2. Click Add.

The Registers list in Admin. Click Add to create a new register.

3. Complete the form using the field reference table below.

The new register form showing the fields described below.

4. Click Save.

5. Common Issues & Troubleshooting

Best practices:

• Plan your register hierarchy before creating registers, so it mirrors your organisational structure and does not need reworking later.
• Use clear, consistent titles so users can easily identify which register a record belongs to.
• Keep Cascade policies enabled when creating child registers, so permissions stay consistent with the parent register without manual setup.
• Use sensitivity levels sparingly and review user assignments regularly, as records in a higher sensitivity register are hidden from users without the matching level.

6. Related Articles

• User: managing user settings and sensitivity levels