Set up push notifications
Push notifications are off by default for both the Sage Construction Management browser solution and mobile apps. You can turn them on in your account settings.
Enable push notifications in Sage Construction Management
- Go to Settings (
). - On the Settings Overview page, select Set Push Notifications.
- Select Enable Notification.Make sure that your browser is set to allow notifications.
- Select the features that you want to receive push notifications for.
- Select Save.
Allow push notifications in Chrome
- Go to the Sage Construction Management login page.
-
To the left of the web address, select View site information.
- Select Site settings.
-
In the Permissions section, select Allow from the Notifications dropdown.
Sage Construction Management features that support push notifications
General
| Feature | Trigger | Conditions |
| General To Do | A general To Do has been added. | The general to do is assigned to the user. |
| The due date of the general to do is today. |
Drawings, specifications, and invitation to bid (ITBs)
| Feature | Trigger | Conditions |
| Drawings | A drawing has been added. | The user is referenced as the bid contact in the lead or project internal stakeholders. |
| The user is referenced as the sales contact in the lead or project internal stakeholders. | ||
| The user is referenced as the project manager (PM) contact in the lead or project internal stakeholders. |
Correspondence
| Feature | Trigger | Conditions |
| Journals | A journal has been added. | The user is referenced as the from or respondent contact. |
| Received a response for a journal. | The user is referenced as the from contact. | |
| The reminder date of the journal is today. | The user is referenced as the from or respondent contact. | |
| The due date of the journal is today. | The user is referenced as the respondent contact and no response has been submitted. | |
| RFIs | An RFI has been added. | The user is referenced as the originator, coordinator, or respondent contact. |
| Received a response for an RFI. | The user is referenced as the coordinator contact. | |
| The response due date of the RFI is today. | The user is referenced as the respondent contact and no response has been submitted. | |
| Submittals | A submittal has been added. | The user is referenced as the originator, coordinator, or respondent contact. |
| Received a response for a submittal. | The user is referenced as the coordinator contact. | |
| The due date of the submittal is today. | The user is referenced as the respondent contact and no response has been submitted. | |
| Submittal Items | The planned submission date of the item design review is today. | The user is referenced as the originator, coordinator, or respondent contact. |
| The completion date of the item design review is today. | ||
| The return to originator date of the item design review is today. | ||
| The date that the item is required on site is today. | ||
| The anticipated delivery date for item material delivery to the site is today. | ||
| The estimated delivery date for item material delivery to the site is today. | ||
| The actual delivery date for item material delivery to the site is today. |
Documentation
| Feature | Trigger | Conditions |
| Daily Log | A daily log has been added. | The user is referenced as the bid, sales, or PM contact in the project internal stakeholders. |
| Meeting | A meeting has been added. | The user is referenced as an attendee. |
| The meeting date has been updated. |
QC and Safety
| Feature | Trigger | Conditions |
| Checklist | A checklist has been added. | The user is referenced as the responsible contact. |
| A checklist item is due. | ||
| Punchlist Items | A punchlist has been added. | The user is referenced as the responsible contact. |
| The punchlist is due. | The user is referenced as the inspector contact. | |
| The user is referenced as the responsible contact. | ||
| The punchlist is closed. | The user is referenced as the inspector contact. | |
| Safety Meeting | A safety meeting has been added. | The user is referenced as an attendee. |
| The date of the safety meeting has been updated. |
To Dos and schedules
| Feature | Trigger | Conditions |
| Project To Do | A project To Do has been added. | The user is the assigned contact. |
| The due date of the project To Do is today. | The user is the assigned contact. | |
| Scheduling Task | A resource has been assigned. | The user is referenced as the resource employee. |
| The task date has changed. |
Contract Administration
| Feature | Trigger | Conditions |
| Prime Invoice | A prime invoice has been added. | The user is referenced as the PM contact in the project internal stakeholders. |
| The user is referenced as the prime contract's prime contact. |
Procurement
| Feature | Trigger | Conditions |
| PO | A PO has been added. | The user is referenced as the PM contact in the project internal stakeholders. |
| Bill | A bill has been added. | The user is referenced as the PM contact in the project internal stakeholders. |
| Sub Invoice | A sub invoice has been added. | The user is referenced as the PM contact in the project internal stakeholders. |
| The user is referenced as the subcontract's prime contact. |
Time and Expenses
| Feature | Trigger | Conditions |
| Labor Timecards | A labor timecard has been added. | The user is referenced as the PM contact in the project internal stakeholders. |
| The user is the employee's manager. | ||
| The user is referenced as the employee's crew leader. | ||
| Misc. Expense | A miscellaneous expense has been added. | The user is referenced as the PM contact in the project internal stakeholders. |
| The user is the employee's manager. | ||
| The user is referenced as the employee's crew leader | ||
| Equipment Timecards | An equipment timecard has been added. | The user is referenced as the PM contact in the project internal stakeholders. |
Contract Administration and Procurement workflow
| Feature | Trigger | Conditions |
| Workflow | A workflow has been initiated. | The user is one of the approvers. |
| A workflow has been abandoned. | The user initiated the workflow or is one of the approvers. | |
| A workflow has been rejected. | The user initiated the workflow or is one of the approvers. | |
| A workflow has been approved. | The user initiated the workflow or is one of the approvers. |