Why MAM is role-aware, how the per-button/per-role/global cascade resolves a setting, and how anonymous, member, owner, and admin audiences each get a tailored app.

What APNs keys, FCM service accounts, and device tokens are, and how MAM Suite uses them to deliver one notification to one phone.

A plain-language model of how your app’s data is built and cached, so you can reason about why a change shows up instantly, late, or not at all.

How a listing decides who can edit it, message its customers, and approve it for publish — the owner/manager/staff/admin roles, and the claim and invite flows that hand them out.

How channels, the dispatch queue, cron, and bracketed replacement tokens work together to turn one fired message into delivered email, SMS, and push notifications.