Platform & Solutions by Prorigo

Protrak Logo

Push and Email Notifications

Configure notifications across lifecycle actions, assignments, updates, scheduled reports, and program-driven events through push and email channels.

What the Capability Enables

Overview

Push and Email Notifications help ensure that the right users are informed at the right time. Notifications can be triggered by lifecycle promotions, task assignment, record updates, scheduled reporting, or custom programs.

Customers can configure recipients, roles, access-based audiences, user attributes, subject lines, message bodies, templates, and event timing according to their operational process.

Configured collaboration

What the Capability Enables

  • Notify users when assignments, lifecycle actions, updates, inspections, completions, or scheduled reports require attention.
  • Use push notifications for quick awareness and email for formal communication.
  • Configure recipients by role, user attribute, record access, or program logic.
  • Use templates for consistent subjects, bodies, and mapped record values.
  • Reduce noise by configuring only the events and audiences that need communication.

Operational capability

Core Capabilities

Event-Based Notifications

Notifications can be triggered from lifecycle commands, record updates, task assignments, or other process events.

Communication can happen automatically when a business action occurs.

What this enables

  • Trigger notifications from configured lifecycle promote actions.
  • Send notifications before or after updates through configured triggers and programs.
  • Notify users when assignments, starts, reviews, or completions occur.

Use cases

  • Notify a site engineer when work is assigned.
  • Notify a planner when work starts or a baseline changes.
  • Notify quality when a checklist is submitted for review.

Recipient Configuration

Recipients can be specific roles, users captured in user attributes, or all users with record access.

This supports broad operational awareness and focused communication to responsible users.

What this enables

  • Send notifications to configured operational or management roles.
  • Use assigned-to fields to notify exact responsible users.
  • Notify all users with record access when broad visibility is required.

Use cases

  • Notify only task-authorized users within a shared role.
  • Alert the assigned user through the configured user attribute.
  • Inform authorized stakeholders of a major lifecycle event.

Push and Email Templates

Templates control how notification content is presented. Email can include subjects, bodies, and mapped record values, while push notifications use shorter action-oriented text.

Reusable templates standardize communication while retaining record-specific information.

What this enables

  • Configure email subjects, bodies, and mapped project or task values.
  • Configure short push text for mobile or web users.
  • Reuse templates across similar events and processes.

Use cases

  • Include clear project and task details in an email.
  • Provide a short mobile alert for a new action.
  • Reuse notification templates across lifecycle events.

Scheduled Report Notifications

Notifications can support periodic report delivery on daily, weekly, monthly, or other configured schedules.

Operational teams may receive daily reports while management receives weekly or monthly summaries.

What this enables

  • Send configured reports to selected roles or stakeholder groups.
  • Attach generated PDFs or progress reports to emails.
  • Vary recipient groups by report frequency.

Use cases

  • Send daily progress reports to operational roles.
  • Send weekly progress summaries to management.
  • Attach a generated PDF for external review.

Program-Driven Notification Services

Configured programs can invoke notification services for requirements beyond simple lifecycle triggers.

This supports exception, delay, validation, or location-related notification logic.

What this enables

  • Trigger notifications after customer-specific business evaluation.
  • Support exception, delay, access-based, or validation scenarios.
  • Combine notification logic with rules, lifecycle controls, and access permissions.

Use cases

  • Notify a responsible user when a configured condition fails.
  • Send a delay alert only when it requires attention.
  • Notify an authoritative role after a customer-specific validation result.

Configured process

How the Capability Works

  1. 1

    Identify the assignment, lifecycle, report, or program event that should trigger communication.

  2. 2

    Choose push, web/mobile, or email as the notification channel.

  3. 3

    Configure recipients by role, user attribute, access scope, or record access.

  4. 4

    Define the subject, body, push text, and mapped values in the template.

  5. 5

    Activate the notification in lifecycle commands, triggers, schedules, or program logic.

In practice

Customer Scenarios

Scenario 1

Assignment and action notification

An assigned user receives a push or email with relevant task details without depending on manual follow-up.

Scenario 2

Lifecycle-driven notification

Configured users or roles are notified when work starts, a checklist is submitted, or a task is completed.

Scenario 3

Scheduled report distribution

Daily, weekly, or monthly reports reach the relevant audience with PDF attachments where required.

Controlled collaboration

Configuration and Governance

  • Configure notifications by lifecycle state, command, trigger, program, schedule, recipient role, user attribute, and access scope.
  • Use templates to control information shared and mapped from the underlying record.
  • Use access-aware options to avoid sending details to users who should not see the record.
  • Keep notification rules selective to focus attention on meaningful events.

Customer Value

  • Improve responsiveness when action or awareness is required.
  • Reduce manual status chasing across assignments, reviews, completions, and reports.
  • Support operational alerts and formal report distribution from one governed platform.
  • Align communication with workflow rules, access control, and customer-specific configuration.

Collaboration

Inform the Right Users at the Right Time

Keep operational alerts and formal communication aligned with workflow rules, access control, and customer-specific process configuration.