How notifications work in Apropos
Apropos keeps you updated through several separate channels: an in-app notification bell, product-update emails, and transactional emails that follow each proposal and contract. They're independent systems, so this guide covers what each one does and how to use it.
In-app notifications
The bell in the top of the app shows alerts about your proposals and contracts. Click it to open a Notifications panel with an unread-count badge (capped at 99+), a Mark all read button, and a list of notifications newest first. When you have none, the panel shows No notifications yet.
Notifications are delivered to the owner of the proposal, not to every member of your team. New notifications appear in the list as they arrive, without a page refresh.
Notification events
Three client actions currently create in-app notifications, each with its own title and destination.
Event | When it happens | What the notification says | Where it takes you |
|---|---|---|---|
Proposal accepted | A client accepts a proposal | <document term> accepted (for example, "Quote accepted") | The project page |
Contract signed | A client signs a contract | Contract signed or Contract awaiting your signature | The project page |
Changes requested | A client requests changes to a proposal | <client name> requested changes | The proposal |
The accepted-proposal title uses your organization's document term, so it reads "Quote accepted" if you call your documents quotes. See Change what you call your documents for how that term is set.
Read and manage in-app notifications
You open and clear notifications from the bell in the app header.
Click the bell in the app header to open the Notifications panel.
Click a notification to open the proposal or project it links to. Clicking an unread notification also marks it read and closes the panel.
Click Mark all read to mark every unread notification as read.
Unread notifications appear in bold with a dot indicator. Selecting a notification that's already read opens its link without changing anything else.
Transactional emails
Transactional emails are sent automatically as part of the proposal and contract workflow.
Send, resend, or send a revised proposal — the client receives the proposal email with a View proposal link (the link will reflect the word you have chosen if instead of proposal). A proposal must have at least one line item and the client's email address to send.
Proposal accepted — the proposal owner receives an acceptance email with the subject Proposal accepted — <client>. When a contract is generated on acceptance, the client receives a signature-request email with the subject Please sign: contract from <business name> and a Review & Sign link that requires no login.
Client signs a contract — no email is sent. The proposal owner gets the in-app Contract signed notification instead.
Resend Contract — available from the proposal's Actions menu only when the proposal is accepted and contract generation is enabled. It sends a reminder email with the subject Reminder: Sign your contract — <proposal name> and a Sign Contract link.
See Proposal settings for how Generate contract on acceptance controls the signature-request email, and Customize your contract template with merge fields for what the client signs.