Alerts

Configure Protect to notify you of data items of interest in near real-time using powerful data detection features.

Updated over a week ago

Worklabs Protect includes a real-time alert feature for monitoring content on its source system. Users can configure and manage alerts, specifying criteria such as content types, keywords, and notification preferences. This system ensures timely updates for account holders, enhancing platform security and compliance.

The alerts table

The alerts table is a key feature for managing alerts on the platform. Each alert set by an account holder is listed in the table, as below:

  1. Title: This is the given name of the alert.

  2. Status: Indicates whether the alert is currently active or inactive

  3. Description: Provides a brief outline of the alert's purpose or trigger conditions, as defined during setup.

  4. Created: Shows the exact date and time the alert was set up.

  5. Options:

    1. View: This feature allows users to delve deeper into each alert, offering a detailed view of its settings and parameters.

    2. Archive: Users can choose to archive alerts that are no longer needed or active, helping to maintain a clutter-free and efficient alert management system.

Creating a new alert

In Worklabs, creating a new alert includes the following steps -

Step 1

  • Create a new alert

    • Title: Give the alert a Name

    • Description: Give the alert a suitable descriptor, succinctly describing the purpose of the alert

      Figure 1: Add alert modal

Step 2

  • Configure channels in scope
    Your selection here sets alerts for only the selected types of content.

    • Post and comments

    • Messages

    • Articles

Figure 2: Configuring channels in scope to an alert

Step 3

  • Configuring people in scope
    Use this option to specify alerts for individual users. If left empty, the system will assume the alert applies to every user within the source system.

Figure 3: Configuring people in scope to an alert

Step 4

  • Specifying conditions (keywords and phrases to watch across channels and people in scope)

    • Specifying the phrase (press enter to add a keyword, Use; to separate multiple keywords

    • Exact match

    • partial match

    • exact exclusion

    • Partial exclusion

Figure 4: Configuring conditions in an alert

  • Configuring actions
    This step involves configuring notification options so that relevant account holders about an occurring event

    • Notification type
      account holders can be alerted by either

      • Work chat message

      • email

    • Admin
      Specify the list of account holders who will be alerted

      • Search and list users who need to be notified of the alert

    • When
      Specifies how quickly an alert is sent to the account holder

      • immediately

Figure 5: Configuring actions to an alert

Figure 6: Add alert action modal

Once an alert has been configured, all data that match the criteria set within will become available to the admin via the notification type, as well as the alerts view (triggered alerts tab) as described in the following section

Viewing triggered alerts

Once a new alert has been created, the system will start logging all data items that match the conditions set within the alerts. You can find this under the alert. As the account holder, you will be able to see this in the 'Triggered alerts' table within the configured alert. The table will list

  • What, Where: Lists the item (What) and its type (Where).

  • Status: Whether the item in question has been 'reviewed', or 'to be reviewed'.

  • When: The date when this was captured under the alert in question

  • Options

    • View: Opens a detailed drill-down view of the data items, displaying the author, creation time, last update time, source system, location, link, and contents.

    • View in the new table: Opens the view page in a new tab

    • Action: Enables account holders to mark items 'reviewed' directly from the 'To be reviewed' alerts. Marking items will record a corresponding event in the Action log.

Did this answer your question?