Four delivery paths that open a project's modal: a live in-app event, a session flag set by another view's 'Go to Project' action, a crew-acceptance email link that opens the contract in sign mode, and a generic ?openProject link used by notification CTAs.
Also called: notification opens the project · email link to the job · deep link
- 1Query parameters are stripped from the URL after firing so a refresh or reshare doesn't re-trigger the action
- 2The schedule hash is preserved so the user stays on the schedule view
- 3Opening is deferred slightly so hash routing finishes settling first
Notifications and emails are only worth sending if the click lands on the thing they are about, and they used to land on a board the recipient then had to search — which is how an urgent message becomes a message that gets dealt with later. Every notification opens the job it refers to. A crew lead's acceptance email opens straight into signing, rather than into a hunt through a list of jobs for the one he was asked about.
- Notification clicks landing on a generic screen
- Re-triggering an action on refresh
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →