Engagement and content

CRM and messaging

Page	Purpose
/admin/crm	Customer relationship management
/admin/inbox	Inbound messages
/admin/whatsapp	WhatsApp conversations
/admin/vendor-contacts	Vendor contact book

WhatsApp runs through apps/whatsapp-gateway, a Baileys session that ships as its own image in the API compose. One container only — a WhatsApp session is single-device, and two processes sharing the auth volume log the number out.

CDP

/admin/cdp, /admin/cdp/profiles and /admin/cdp/audiences build unified customer profiles and audience segments. CDP access is owner-tier (manage_cdp): superadmin only, by design.

Vendors

/admin/vendor-applications triages booth applications and /admin/vendor-page edits the public vendor marketing page. Editors can approve, reject and reassign; mark-paid is admin/finance only, enforced at the procedure rather than the page.

/admin/collaborate handles sponsorship and media leads.

Content

Page	Purpose
/admin/news	News articles
/admin/newsletter	Newsletter management
/admin/testimonials	Testimonials
/admin/legal	Legal pages, served at /legal/[slug] without a deploy
/admin/email-previews	Render transactional emails for review

Campaigns never send from code

Marketing and newsletter sends go through the Autosend MCP server only: draft, then send_campaign with confirmed: true. No drip, no staggered send, and no bulk-send code path — that is what got the sending domain flagged. Transactional email stays in code via sendEmail, with failures captured by captureEmailFailure so they never fail the operation they belong to.

Mobile app surface

/admin/mobile/* administers the companion app: Reports, Posts, Comments, Ads, Badges, Promo Cards, Wallpapers, Card Shops and App Config. Moderation actions need moderate_mobile.

Routers: mobileCatalog, mobileModeration, mobileShops, plus the /v1 REST surface the app itself calls.