Record Alerts
Flag records automatically based on conditions you set
An Alert
1. Configuring record alerts
You'll need Configure Permission
Permissionfor this collection to set up alerts. If you're unsure, ask your System admin.The level of access — No Access, View Only, View & Edit or Not Enabled — granted through a Role for a specific area of Kinabase, such as records, tasks or configuration.
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:
| Severity | Meaning |
|---|---|
| Critical | Needs immediate attention. |
| Warning | Worth checking soon. |
| Info | Useful context, no action required. |
| Success | Highlights something that's on track. |
6. Write the message
Add a Message explaining clearly why the alert was triggered. It shows with the alert's name on the record, and when you hover over the alert icon in the table or on a Kanban card.
7. Set the conditions
Build the alert's filter conditions on specific fields, the same way you would for a collection View
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, headed with a bell icon. It shows the severity icon for any record that meets the alert's conditions, and stays blank otherwise. Alerts also appear in the record's Info panel, under Alerts. When the panel is hidden, critical and warning alerts show as a coloured dot beside its icons.
On a Kanban board, a card with a current alert shows an icon at the start of its title, in the colour of its most severe alert. Hover over the icon to read every current alert, most severe first. See Using Kanban Views.
3. Example uses
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.