Record change notifications are emails that Quickbase sends out when a record has been added, changed, or deleted. You can create your own message or use the default message Quickbase creates. The notification can include a copy of the record. When you create a notification, you set the conditions for when to send the notification and who should receive it.
Who can create notifications?
App Managers can create notifications for app users. Users can create notifications for themselves. App managers can edit, delete, or deactivate any notification, including those created by users.
What you can do with notifications
Notifications can help you keep track of what's happening in your application. You can set up a notification whenever a record has been changed in any way, or added or deleted, or be notified when a user appears in a task's Assigned to field.
Notifications also let you apply very specific conditions to check for before sending the email and also target only appropriate individuals for receipt. For example ,if your Quickbase application tracks deliveries for your company. When a delivery's status changes to "Ready for shipment" a notification can be sent to the user listed in the "Driver" field.
Quickbase can even let you know when larger changes occur. For example, if someone changes multiple records during the same operation (like an import), Quickbase can send you a single email notification summarizing all of the changes. (Note that the option to notify a user listed in a specific field is not available for this kind of notification.)
Quickbase can send two types of notifications
Quickbase can send two types of notifications:
Recipient. Use this type of notification to send notifications to app users. You can create notifications based on users' role, showing only those fields and records they have access to.
Open Open notifications let you send emails to someone who doesn’t have access to your app by typing in an email address. The notification recipient will be able to see all fields and information in the record(s). Only application managers can create this type of notification. You can control what fields display in an open notification by specifying a custom form for the notification or creating a custom notification
Note: Do not use open notifications to send sensitive information.
There's actually a third type of notification, but chances are, you'll never see one.
Prior to October 29, 2004, there was a third type of notification that would show all fields except the ones a user had no access to. Quickbase supports this type of notification only for backward compatibility. These notifications can no longer be created, but can be edited or deleted.
When notifications won't be sent
A notification won’t be sent when its owner no longer has access to the table or the app. The user may no longer have admin rights, or may have been removed from the app (for example, if the user has left your company).
To identify notifications that won't be sent:
Open the table that contains the notification.
Click Settings, then click Notifications, subscriptions, & reminders.
The title and owner of notifications that won’t be sent are displayed in red, and the icon also changes. You can make a copy of the notification, delete it, or deactivate it.