Notifications (Admin configuration)

Account Notifications let org admins control where notifications are delivered (Email, Slack or Microsoft Teams) and which events trigger notifications across the account. This helps your team stay on top of projects, tasks, Q&As, and document collaboration without missing critical updates.

Who can configure: Org Admins / Account Owners (Member roles typically can’t access Account Notifications).

Accessing Account Notifications

1. Go to Settings in the SiftHub Web App

2. Click Notifications

3. You’ll land on Account Notifications

1) Choose notification channels

Under Channels, you can enable/disable where notifications are delivered across your account:

• Email — receive notifications in your email inbox

• Slack — receive notifications in Slack (requires SiftHub Slack bot to be connected)

  • Slack delivery has two independent destinations — a direct message to the person, and a project’s linked Slack channel

• Microsoft Teams — receive notifications as a direct message in Teams (requires the SiftHub Teams bot to be connected)

Turning a channel OFF disables that channel across the org.

Delivery columns explained

The Preferences table has one column per delivery destination. Each is set independently for every notification, so the same event can go to some destinations and not others.

A column is greyed out when its channel is switched off under Notify on above.

Slack DM and Slack Channel

These are two separate destinations, not alternatives — a notification can go to both, either, or neither.

• Use Slack DM for anything personal: a task assigned to you, content requested from you, an @mention.
• Use Slack Channel for team-wide milestones the whole bid team benefits from seeing: autofill completed, project status changed, submission package exported.

Turning on Slack Channel for an event that fires per question would post a message for every question, so it suits milestones rather than item-level activity.

Slack Channel only delivers for projects that have a channel linked. Linking is done on the project itself, not here — see Project Details Page. A project with no linked channel simply sends nothing to that destination.

2) Choose which events trigger notifications

Under Preferences, you can enable/disable notifications at a category level and also at an individual event level.

• Use the expand/collapse arrow to open a category (e.g., Projects, Q&As).

• Use the checkboxes under Email and Slack to control where each event is sent.

• Some events show a ⚙︎ (settings) icon — these are time-based reminders where you can configure reminder frequency.

3) Notification categories

Notifications are grouped into categories (Projects, Q&As, Document collaboration, Tasks & Comments). Each row represents a specific event, and you can enable/disable it per channel (Email / Slack). 

Notification definitions (what each one means)

Projects

• Clarifying questions are due in — Reminder sent before a clarifying question’s due date (based on the reminder frequency you set).

• Clarifying questions are overdue — Alert sent after a clarifying question passes its due date (can repeat based on the reminder frequency you set).

• Project is due in — Reminder sent before a project’s due date (based on the reminder frequency you set).

• Project is overdue — Alert sent after a project passes its due date (can repeat based on the reminder frequency you set).

• You’re added as a Collaborator — Notifies a user when they’re added to a project as a collaborator.

• You’re added as a Reviewer — Notifies a user when they’re added as a reviewer on a project.

• Autofill is completed — Notifies when an Autofill run finishes for a document.

Q&As

• Q&A is about to expire — Reminder sent when a Q&A is nearing its expiry date (based on the reminder frequency you set).

• Q&A is overdue — Alert sent when a Q&A is past its due/expiry date (can repeat based on the reminder frequency you set).

• You’re added as a Reviewer — Notifies a user when they’re added as a reviewer for a Q&A.

Document collaboration

• Content is requested — Notifies when someone requests content from you (i.e., asks you to contribute/provide content).

• Content is submitted for review — Notifies when content is submitted and is ready for review.

• Content is updated — Notifies when content you’re involved in is updated.

• Content is approved — Notifies when submitted content is approved.

• Content is rejected — Notifies when submitted content is rejected and needs changes.

• Content is assigned to you — Notifies when content ownership/assignment is given to you.

Tasks & Comments

• Task is due in — Reminder sent before a task’s due date (based on the reminder frequency you set).

• Task is overdue — Alert sent after a task passes its due date (can repeat based on the reminder frequency you set).

• Mentioned you — Notifies when someone @mentions you in a comment.

• New comment — Notifies when a new comment is added on an item you’re involved in.

Configure reminder frequency (for time-based reminders)

For reminders like “due in” and “overdue”, click the ⚙︎ icon to configure when reminders should be sent.

Before due date

1. Click the ⚙︎ icon for a “due in” reminder (e.g., Task is due in, Project is due in).

2. In Before due date, select the day(s) you want reminders to go out (you can select multiple).

   • Example: 3 days and 1 day before the due date

3. Click Save.

After due date (overdue)

1. Click the ⚙︎ icon for an “overdue” reminder (e.g., Task is overdue).

2. In After due date, select the day(s) you want reminders to go out after the due date.

   • Example: 1 day after the due date

3. Click Save.

Tip: You can remove a selected day by clicking the × on the chip.

Notification configurations are currently configurable at the account level from the SiftHub Web App. If you want to configure notifications for a specific user or team - reach out to your Customer Success Manager.