Skip to content

Notes, labels, and history

Notes record free-text context, labels classify records, and history records platform events. None of these actions approves an application, changes a loan, or allocates a payment.

For
Users recording context, classifying a record, or reviewing what happened.
Requires
Access to the person, application, loan, or action and the relevant note, label, or history permission.
Available when
The current record exposes the corresponding Notes, Labels, or History section.
Before you begin
Select the narrowest correct record and omit unnecessary sensitive information from free text.
Expected result
The note or label is stored on the intended record, or history identifies the recorded event, without changing lifecycle status.

Notes

Notes can be stored against a person, application, loan, or related action. Put the note on the narrowest record that gives it the correct context:

  • person note for information about the continuing customer relationship;
  • application note for one request or review;
  • loan note for servicing the issued agreement;
  • action note for the reason or evidence behind a specific change.

Notes can show their author and affiliation, and visibility can depend on access. Keep them factual, dated where relevant, and free of unnecessary sensitive information. Edit an existing note only to correct it; add a new note when recording a later development.

Labels

Labels are reusable classifications attached to people, applications, or loans. They can support queues, searches, and integrations such as a configured politically exposed person result.

A label should have one agreed meaning. Adding or removing it does not change the record's formal status and should not be used to bypass a processing action.

History

History records the user, event, and date. Some entries allow you to open the changed values. Use it to answer questions such as:

  • when an application was approved or lent;
  • who changed person details;
  • whether a payment or invoice line was deleted;
  • when a loan action completed;
  • whether an automated event was triggered.

History confirms that a platform event was recorded. For email, SMS, document-generation, or webhook failures, an administrator may also need the event-action execution history.

Use Activity and audit history to choose between record History, Workspace Events, profile History, enrichment history, and event-action Execution History.