Introduction

Customizations in Eramba are part of the “Common Features.” This feature allows users to create custom fields of various types and tabs, enabling them to associate and organize any relevant information.

LLMs

Statistically, most people don’t "read" — and certainly don’t fully "understand" — documentation. If you’re planning to take this course be asured you wil get in trouble.

You can use LLMs to clarify doubts from what you "read" to make sure you "understand", you simply need to copy the URL and paste it into your preferred LLM (OpenAI, Gemini, etc.) together with the prompt below:

I’m trying to understand how customizations works and how it’s implemented in Eramba. This is their documentation. If you’re able to review it, can you answer any quick questions I may have? This is the URL: (paste url here)

If you are somewhat dilligent and careful on your questions you wil get a lot of support from your LLM.

Typical Scenarios

This chapter demonstrates practical ways to use customizations:

• Hide fields from forms that are not relevant or used by your organization.

• Create custom tabs to organize information according to your workflow or process needs.

• Add custom fields to capture additional data specific to your organization.

• Rename fields, including their name and description, to better reflect your organizational terminology.

• Reorganize fields by moving them up or down to match workflow priorities.

Supported Versions

Customizations are available in both on-premise and cloud deployments, and are available in Enterprise only.

Scope

Customizations are available in almost every module. You can verify whether a module supports Customizations by opening the module and clicking the Common Features button (the three dots in the top-right corner). If Customizations is listed, the module supports it.

Core Concepts

The following is a list of key concepts you need to understand in order to effectively manage customizations:

• Perform customizations on every module before starting work.

• Treat fields as “columns” in a spreadsheet. Decide in advance which fields you will use.

• Hide unnecessary default fields to simplify implementation and daily operations (can reduce complexity by approximately 20%).

• Custom fields limit: 30 per module.

• Tabs limit: 4 per module.

Fields

Fields have the following options that need to be specified:

• Field Name – The name of the custom field.

• Description – A brief explanation of the field’s purpose.

• Type – The field type (see the list of custom field types above).

• Mandatory – Indicates whether the field is required. Mandatory fields must be completed when adding or editing items in the module.

Custom fields are limited to 30 per module.

Types

There are 9 different types of custom fields in Eramba:

1. Short Text – Text field for brief information.

2. Paragraph – Text field for longer information or notes.

3. Date – A field to store date values.

4. Dropdown – Allows selecting only one option at a time from a predefined list.

5. Dropdown – Multiple Select – Allows selecting multiple options from a predefined list.

6. Numeric – Integer – Stores whole number values.

7. Numeric – Float – Stores decimal number values.

8. Custom Role – A field to assign roles for adding users and groups.

9. Module Relationship – Creates a custom relationship to another section. (Not available in all sections.)

Once a custom field has been created, its type cannot be changed.

Tabs

• Tabs can be created or rearranged to better organize your fields.

• A name must be specified at the time of creation.

Tabs are limited to 4 per module

Actions

Actions allowed on the customisation feature: Add, Edit, Delete, Hide, Preview, Reset, Rearrange

Edit

Fields can be edited by clicking the pencil icon in the actions menu. For custom fields, you can also modify options for Dropdown fields and toggle the mandatory checkbox.

Some system fields cannot be edited

Add

Fields can be created by clicking the “Add Field” button within the corresponding tab. When adding a field, the following information is required:

• Name – The name of the field.

• Description – A brief explanation of the field’s purpose.

• Type – The field type.

• Mandatory – Indicates whether the field is required.

Tabs can be added by clicking the “Add Tab” button in the top-right corner. When adding a tab, the following information is required:

• Name – The name of the tab.

Delete

Custom fields can be deleted by clicking the trash icon in the actions column.

System fields cannot be deleted, and deletions cannot be undone.

Hide

• Fields can be hidden by selecting the Hide checkbox.

• It is strongly recommended to review and hide unnecessary fields before working on any module. 

Some system fields cannot be hidden, as they are mandatory.

Preview

This button is used to preview how the form will appear and to verify the customizations you are applying.

Reset

You can reset the order and visibility of fields to their default settings using the Reset button. This action will not delete any custom fields or tabs that have been created.

Rearrange

You can rearrange the order of fields and tabs by dragging and dropping using the six-dot icon on the left side of the field.

Considerations

Notifications

Notifications will be affected by any renamed or newly created fields. Any custom role field you create will become a potential recipient in notifications. This is especially important when designing custom workflows, as it allows notifications to be sent to users based on your custom roles.

For example, a custom role field created in the Asset module will appear as an option in the recipient list for notifications.

Reports

Custom fields will affect the Table widget. Newly created fields will be available as options within the table, and any renamed fields will be displayed using their updated names.

Imports / API

Changes made to custom fields will be reflected in CSV imports. Newly created fields will be added as columns in the CSV import template, typically appearing at the end.

Translations

eramba uses English as the default language, though additional languages are available (see the Installation documentation). Creating or renaming fields will affect translations.

When creating a field or tab, all users (regardless of their selected language) will see the field exactly as defined in the customization. Customizations override language selection.

Examples

Internal Controls	Control Maturity/Readiness
Internal Controls / Audits	Dropdown to track audit duration Dropdown to track evidence quality Dropdown to Track Audit Maturity
Policies	Draft vs Published Document Maturity/Applicability Policy Approver Custom Role
Policy Reviews	Dropdown to track Review duration Dropdown to track down Reviewer Feedback Quality
Risk (All Three)	Root Cause Business Impact Risk Status (Closed/Open/Etc)
Risk Reviews (All Three)	Dropdown to track Review duration Dropdown to track down Reviewer Feedback Quality Exception Approver Role
Risk Exceptions	Exception Approver Role Severity
Policy Exceptions	Exception Approver Role Severity
Compliance Exceptions	Exception Approver Role Severity
Projects	Severity
Project Tasks	Uncertainty
Incidents	SIRT Responsible Custom Role Affected System Severity
Online Assessments	Assessment Result Fail / Pass
Online Assessments / Findings	Severity Finding Approver Role
Compliance Analysis	Maturity
Organization /Third Parties	Contact Name Contact Email