Skip to content

Labels

Labels classify people, loan applications, and loans. Administrators set each label's displayed name, translation, colour, and order. Users with permission attach or remove them from records.

For
Administrators defining reusable record classifications.
Requires
Label administration permission and an agreed meaning, owner, wording, and translations.
Available when
The relevant person, application, or loan view exposes labels.
Before you begin
Check saved queries, decisions, integrations, procedures, and existing records that may use the label.
Expected result
The label is recognisable on representative records and does not replace or imply a lifecycle status.

Use labels for classification

Use a label for a review category, operational segment, or integration-maintained classification. A configured politically exposed person integration applies its selected label when the result matches.

Labels are not lifecycle states. Do not use a label such as “Approved” instead of the application approval action, and do not assume that removing a label reverses the process that originally applied it.

Create or edit labels

  1. Open Administration → Labels.
  2. Add a label row or edit an existing row.
  3. Choose its Color and enter the Label wording and translations.
  4. Reorder labels when a consistent display order helps users.
  5. Select Save to persist the complete collection.
  6. Open a representative person, application, or loan and confirm that the label is recognisable in context.

Adding, editing, removing, and reordering rows changes the current form first. The collection is not persisted until Save succeeds. Labels do not have a separate durable key, so names must still remain unambiguous to users and configuration owners.

Define and review labels

  • give each label one documented meaning and owner;
  • use translations that preserve the same meaning;
  • choose colours for recognition, not as the only source of meaning;
  • avoid two labels that differ only slightly;
  • define whether users, decisions, or an integration maintain the label.

Before renaming or deleting a label, check saved queries, decisions, user procedures, and integrations. Historical enrichment results can remain even if the current label is later removed.

Automation and integration use

A decision or configured workflow can add or remove a label. The politically exposed person integration can maintain a selected label when a provider result matches. In either case, the label is the visible classification; the decision result or dated enrichment remains the evidence behind it.

Before changing a label used by automation:

  1. identify the responsible decision, query, or integration;
  2. confirm whether its selection follows the label record or relies on displayed wording;
  3. test both the matching and non-matching case;
  4. confirm that a later result removes or retains the label as intended;
  5. keep historical provider results even if the current label changes.

Delete or retire a label

Removing a row and saving removes that label from the maintained collection. First check people, applications, loans, saved queries, decisions, integration settings, and operating procedures that refer to it.

When earlier classification must remain explainable, prefer an agreed retirement procedure over silently replacing the label's meaning or colour. Colour is a cue, not evidence or status.

Troubleshooting

Symptom Check
A row change disappeared The collection was saved after editing.
Label is unavailable on a record Label-update permission, supported record type, and tenant configuration.
Automated label is not applied Enabled integration or decision, its condition, selected label, provider result, and execution history.
Label returns after removal A decision, enrichment, or other configured process may be applying it again.
Users confuse labels with status Rename the label and update the procedure so the formal application or loan action remains clear.