Docs

What Triggers a Notification in BackOps

The events, tasks, files, schedule, areas, collaborators, advances, procurement, organization, and billing activity that can create a notification.

This page lists the activity that can create a notification, grouped the way they are grouped in your settings. Whether you actually receive one depends on whether you follow the item and which types you turned on. See managing your notification preferences.

Notification Types by Area

AreaActivity that can notify
EventsEvent created, event drafted, event updated, member added to an event
TasksTask created, assigned, status changed, commented on, review requested, reviewed
FilesFile created, new version added, commented on, review requested, reviewed
ScheduleActivity created, activity updated
AreasArea created, area updated
CollaboratorsCollaborator added, collaborator removed
AdvancesAdvance requested, approved, assigned, updated
ProcurementResource created, quantity changed, schedule changed, type changed, removed; reservation requested; order status changed; order line removed
OrganizationMember added to the organization
BillingPayment failed, trial ending, renewal upcoming

An event type's effects can also send a custom notification. Use that when you want a specific change to alert people beyond the standard list. A custom notification goes to the recipients and channels chosen in the effect, regardless of their preferences, and it reaches the person who made the change too.

Who Is Notified

BackOps notifies the people following the item the activity happened on, subject to their preferences. You are not notified about your own changes. The exceptions are custom notifications from event type effects, described above, and the trial ending and renewal upcoming billing notices, which go out whatever your preferences say. Organization-level activity, such as events being created or drafted, notifies only people who turned on organization activity.