Sign Request Notifications
Choose who gets emailed when a customer submits or resubmits a sign request.
A sign request that nobody notices is a request that sits there. Each event has its own Notifications page where you pick which of your team are emailed the moment a customer raises one.
Availability
Sign request emails are part of the customer portal, available on the Business and Enterprise plans, and only fire on events with the design phase switched on. The page itself is visible on every plan, but there is nothing to notify about until the portal is in use.
Choosing recipients
- Open the event and click Notifications in the event menu.
- On the New sign request notifications card, tick the people who should be emailed.
- Click Save.
The description on the card says it plainly: "These people are emailed when a customer user submits or resubmits a sign request. Leave everyone unticked to send nothing."
Only organisation members can be recipients — owners, admins and members, each shown with their role. Contractors and customer users can never be selected.
If nobody is ticked
No email is sent. That is a valid setup: some teams work the Requested filter on the signs list instead of their inbox. Nothing is lost either way — the request is still on the sign with its full history.
What triggers an email
- A customer submits a new sign request.
- A customer resubmits a request you sent back for more information or rejected.
- A customer makes an artwork decision — approving, requesting changes or rejecting — which goes to the same list of people.
The list is checked against your current organisation members each time an email goes out, so someone who has left the organisation stops receiving them automatically.
Keep the list short — one or two people who actually action requests. A notification that goes to everyone gets ignored by everyone.
Per event, not per organisation
Recipients are stored against the event, so a client-facing event can notify the account manager while an internal one notifies nobody. Duplicating an event does not carry the recipient list across — set it again on the new event.