Engagements

Documentation Index

Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt

Use this file to discover all available pages before exploring further.

An engagement is anything in Soundcheck that’s waiting on someone’s response — an event invitation, a crew offer, or an availability check. They all behave the same way: a recipient gets notified, the recipient responds, and the requester sees the result. Engagements live in a single place so members don’t have to hunt across three different lists.

---

​

The three kinds

All three roll up into the same statuses on the back end: pending, accepted, declined, standby, expired, or withdrawn.

---

​

My Engagements

Every member has a personal inbox at /engagements. Pending items rise to the top, with separate tabs to filter:

• All — everything you’ve ever been sent.
• Needs response — items still waiting on you.
• Responded — items where you’ve already replied.

Each row shows the engagement kind, the title, the event date (when available), and the relevant action buttons. For past events, the buttons are replaced with “Event has passed” so you can’t accidentally respond to a gig that already happened.

---

​

Org Engagements (admin)

Owners, admins, and gig coordinators get a separate view at /org-engagements that aggregates engagements across the whole organization. Instead of per-recipient actions, each row shows a stat strip:

• Total recipients
• Pending
• Accepted / Available
• Declined / Unavailable
• Standby
• Withdrawn / Expired

Use it to spot stalled engagements — for example, an invitation that’s been pending for three days with no responses, or a crew offer where every recipient has declined.

---

​

Calendar handoff on accept

When you Accept an invitation or crew offer on Soundcheck, the matching Google Calendar invite is automatically marked as accepted for you — no need to confirm twice. This works through the same Google Calendar sync that powers the event-to-calendar pipeline:

1. The event is already published to the organization’s Google Calendar.
2. When you accept on Soundcheck, the API calls Google Calendar’s attendee API with responseStatus=accepted.
3. Your calendar updates within seconds.

If the calendar sync isn’t configured for the organization, the accept still succeeds on Soundcheck — only the calendar side is skipped.

---

​

Notification deep links

Engagement notifications (email, SMS, push) all link back to the unified inbox using ?highlight={id}. When you open the link, the inbox scrolls to the matching row and pulses a ring around it for about three seconds. This replaces a previous behavior where notification links pointed at per-kind URLs (like /engagements/invitations/xyz) that no longer exist. If you have older notifications cached, they’ll now redirect into the inbox.

---

​

Engagement preferences

You can control how — and whether — you’re notified for each kind of engagement.

​

Per-user preferences

Open your profile and look for Notification preferences. For each of the three engagement kinds, you can toggle:

• Email
• SMS
• Push

Toggles default to on. Turning every channel off for a kind effectively mutes that kind for you.

​

Org-wide defaults

Owners and admins can set the defaults that new members start with, under organization settings. Defaults only apply where a member hasn’t set their own preference — your explicit choices always win.

---

​

Related