Notifications

Crove notifies you about document events through two channels:

• In-app bell — the bell icon in the bottom-left sidebar with an unread count, polled every 60 seconds
• Email — sent from mail@updates.crove.app for events you've opted into

Both channels honor the same per-org preferences so flipping a preference off silences both surfaces. No more "I turned off the email but the bell still pings me."

The in-app bell

Click the bell icon in the sidebar to open your inbox. The popover shows up to 50 recent notifications, newest first.

Each notification has:

• An event icon (Sparkles for completions, FilePlus for sends, etc.)
• A title and body
• A relative timestamp (2 minutes ago, 1 day ago)
• A click target that deep-links to the relevant document

The unread badge (red, on the bell) shows up to 9+. Opening the popover auto-marks read the notifications shown — same UX as Slack or Linear, so opening the inbox doesn't get punished by having to mark each one yourself.

You can also click Mark all read at the top of the popover to clear the badge without opening individual notifications.

Notification preferences

Manage what fires under Settings → Notifications. Three toggles gate every notification Crove sends:

Toggle a preference off and Crove skips both the email and the bell entry for that event. Toggle it on and you start receiving again from the next event.

Preferences are scoped per organization — if you belong to multiple workspaces, you can have one workspace ping you on every respondent submit and another stay quiet, by visiting each org's Notifications settings.

What fires what

The "always" rows can't be toggled off — they're required by the respondent flow. If a doc was cancelled, the people you invited need to know to stop trying to sign.

Email open tracking

When Crove sends an invitation email, the body includes a 1×1 transparent pixel that pings:

GET /api/track/email/<invitationId>

When the recipient's email client renders the message, the pixel fires and Crove records the first-open timestamp. Re-opens don't overwrite the original (so the timestamp on the document's People tab is when they first saw it, not when their client last re-rendered).

The pixel is served as a no-cache GIF straight back even if the DB update fails, so a tracking outage never shows a broken image in someone's inbox.

What you can do with open tracking

• Spot stalled docs: filter the documents list by Status = Sent, then check the People tab — if last opened is several days old, time to remind
• Send timely reminders: open events show up in the activity feed so you can react in near-real-time
• Audit-grade evidence (with caveats — see Privacy below)

Privacy notes

Open tracking is approximate, not exact:

• Many corporate email clients (Outlook, Gmail Workspace) pre-fetch pixel URLs server-side for security scanning. An open recorded this way doesn't mean a human looked at the email.
• Image-blocking clients (text-only mode, some privacy-focused setups) miss opens entirely. The respondent might have read your message — Crove just won't know.
• Use opens as a directional signal, not proof of delivery.

If your compliance program needs harder delivery proofs, layer in SMS verification or in-person signing on top of the email channel.

Recommended setups

Sales (high-frequency, every event matters)

• Document events: ON
• Completions: ON
• New responses: ON

You'll see every respondent submission in the bell and emails go out for completions.

Operations / shared inbox (only the milestones)

• Document events: OFF
• Completions: ON
• New responses: OFF

Only fully-signed documents ping you. Use the dashboard's activity feed for everything else.

Vacation / focus mode

• All three: OFF

Crove still records every event in the activity feed and audit log — you just won't get pinged. Re-enable when you're back.