Kinabase Logo
Help & Support

Record Alerts

Flag records automatically based on conditions you set


An Alert

rule flags records that match conditions you define, so your team can spot them instantly and act, without hunting through a full list.

Why use alerts?

  • Catch risks instantly - an icon and colour draw the eye to overdue, expiring or high-priority records as soon as you open the collection.
  • Focus your team - sort by alert level so colleagues tackle the most critical work first.
  • Share safely - surface only the alerts that matter in a portal, keeping external users informed without oversharing.

1. Configuring record alerts

You'll need Configure Permission

for this collection to set up alerts. If you're unsure, ask your System admin.

1. Open collection configuration

Open the options menu (⋯) in the top-right of the collection screen and select Configure.

2. Go to Alerts

Under the Display heading, click Alerts.

3. Add an alert

Click Add Alert to start configuring a new rule.

4. Name the alert

Give it a clear name so your colleagues can recognise its purpose at a glance.

5. Set the severity

Select one of four severity levels, each shown with its own icon and colour on the record:

SeverityMeaning
CriticalNeeds immediate attention.
WarningWorth checking soon.
InfoUseful context, no action required.
SuccessHighlights something that's on track.

6. Write the message

Add a message that will display on the record, explaining clearly why the alert was triggered.

7. Set the conditions

Build the alert's filter conditions on specific fields, the same way you would for a collection View

. You can combine multiple conditions on one alert.

8. Save

Leave configuration to return to the collection - your alert is now active.


2. Viewing alerts

Once an alert is set up, an Alerts column appears in the collection list with a lightbulb icon. It shows the severity icon for any record that meets the alert's conditions, and stays blank otherwise. Alerts also appear on the record's Details tab, above its workflow history.


3. Example uses

How to use alerts effectively

  • Account managers flagging clients they need to chase before a relationship goes cold.
  • Asset teams tracking warranty expirations or scheduled maintenance dates.
  • Project teams identifying slippages or approaching deadlines.
  • Logistics teams highlighting records with missing address details.

4. Best practices

  • Name your alert clearly - a descriptive name helps your team recognise its purpose at a glance.
  • Write a clear message - explain what the alert means and, where relevant, what action to take.

Alerts let your team spot critical records the moment they matter, so nothing falls through the cracks.


Need more help? Ask your System admin, or contact our support team via Help & Support.