Alerts let people know, automatically, when there have been changes that they should know about or there are matters that need their attention.

Phrontex can create a notification for any action that modifies content, such as creating, editing, or approving content, or posting a comment.

Users receive notifications as entries in the Alerts list on the user drop-down and, optionally, in an email.

Note: you don’t receive notifications for your own actions.

Example uses

  • Let everybody know when a policy has been added or updated.
  • Let people know of any change to a page that includes a reference to their position.
  • Notify managers that content for which they are accountable is due for review. There is often a policy requirement — and in some cases a legal requirement — that some types of content be reviewed annually. This form of notification helps meet that requirement.
  • Notify a senior manager that content is overdue for review.
  • If you have a register of items with date values (such as permits or contracts with renewal dates), notify the accountable manager when the item is coming due or a more senior manager if the item is overdue.

Types of Alerts

There are really three types of alert: activity, scheduled and warnings.

Activity Alerts (immediate)

A sub-set of items from the activity log.

Scheduled Alerts (delayed)

These are delayed notifications, such as if a page has not been reviewed within a year.  This would set up as a regular alert with a one-year delay from the last update.  If the page gets updated, the alert will be pushed out to a year from the latest update.

Warnings - based on custom dates

A page type can be configured with one or more date fields.  For example, a contract or lease would have an end date. 

You can use Phrontex to alert someone in advance or after this date. For example, six months before a lease expiry, alert the property manager.