Settings & Notifications

PR Flow is designed to be quiet. It doesn't send you a notification for every single comment—only when a PR transitions into a state that actually blocks you or your team.

Notification Types

You can configure these options in Settings.

Reactive Pings

Turn on Reactive pings to hear when a tracked pull request newly needs your attention or has been waiting too long. Selecting the alert brings PR Flow forward and opens that pull request directly instead of sending you to a browser.

If new work accumulated while PR Flow was closed, the next successful launch sends one consolidated catch-up alert instead of a burst of individual notifications. Selecting it opens Needs you. Attention that was already known before shutdown stays quiet.

Digest Notifications

Instead of real-time pings, you can configure PR Flow to give you a summary of your queue at specific times of the day, such as 09:00 and 14:00. A digest tells you:

• What needs you right now.
• What has gone stale.
• How many minutes of review are queued, using the same effort estimates shown on each pull request.

PR Flow stays quiet when there is nothing in Needs you. Selecting a digest opens that view.

Notification History

The bell keeps recent alerts available when you miss an operating-system notification. Entries open the same pull request or Needs you destination as their matching alert. Clearing the complete history requires confirmation.

Group Management

If you manage multiple teams or squads, you can configure Groups in the sidebar.

• Import members automatically from GitHub, GitLab, or Gerrit.
• Filter your Board or Feed view to only show PRs relevant to a specific squad.

Feature Policies

For enterprise setups, a seat-administrator can manage feature policies. This allows team leads to turn certain capabilities (like AI reviews) on or off for the entire team, and these changes synchronize to the UI in real time.