Knowledge Base

From /event-manager click the + New Event button. Pick a blueprint (Wedding Classic, Corporate Conference, Birthday) or pick Custom. The blueprint auto-spawns sub-events (Mehndi, Sangeet, etc.) when you click Indian Wedding (Classic).

Settings → Team → Invite. Each invite costs 1 seat (5 seats included on Pro). Crew get the crew role by default; Coordinators get coordinator; Studio owner can promote anyone via the dropdown.

Lead = someone enquired (Instagram DM, website form). Deal = qualified opportunity with a value & expected close date. Proposal = the line-item PDF/quote sent to the client for signature. One lead can produce many proposals.

If you've published your public site at /studio/<slug>, every contact-form submission lands in public.contact_submissions and is auto-promoted to public.leads within 60 seconds (via the automation engine).

Set the score column manually (0–100) or let an automation rule do it: e.g. "if budget_band > ₹10L AND event_date within 6 months → +30 score". Visible as a colour bar in the CRM kanban.

CRM → Proposals → New. Add line items (with HSN/SAC codes for GST), set tax_rate, click Send. The share_token is generated; client clicks the link to view + sign. Stripe/Razorpay payment link auto-attached if you have it enabled.

One click in /new-event spawns 5 sub-events on the dates you specify: Mehndi (D-3), Sangeet (D-2), Haldi (D-1), Wedding (D-day), Reception (D+1). Each has its own guest list, timeline, and vendor allocations but shares the parent_event_id for cross-reporting.

Event → Settings → Dietary. Pick from the chip grid: Jain, Tamil-Brahmin, Halal, Marwari, Kosher, etc. Public RSVP page reads via public_event_dietary() RPC; guests see only the dropdown options you enabled.

Every guest gets a unique QR voucher (auto-generated). On event day open /check-in?event_id=<id> on a phone, point at the QR, the RPC checkin_guest_by_token() marks them present. Works offline if PWA cached the route.

/api-keys → New key. Keys start with eos_live_ (or eos_test_ in dev). They're one-shot — copy when shown. Pick scopes (read, write, admin). All requests need Authorization: Bearer eos_live_…. 600 req/min rate limit per key.

/webhooks → Subscribe. Pick events (rsvp.received, invoice.paid, etc.), enter your endpoint URL, copy the signing secret. Every delivery includes X-EOS-Signature: t=…,v1=… (timestamp + HMAC-SHA256). Verify with EventSuperOS.verifyWebhookSignature().

/mfa → Scan QR with Google Authenticator / 1Password / Authy → enter the 6-digit code. Save your 8 recovery codes. Without 2FA your account is at higher risk if your password is phished.

Settings → Data → Export now. We generate a complete JSON dump of all your rows + signed URLs for uploaded files. Valid 7 days. Limit: once per 24 hours per studio.

Settings → Data → Delete my account. We insert into deletion_requests, send a 30-day grace email, then hard-delete via execute_scheduled_deletions() cron. Financial records covered by Indian Income Tax 7-year statute are retained (see DPA).