HOC Site

Web push (members)

Optional browser push for signed-in website members when they receive in-app notifications (for example from lifecycle create_notification actions). Configure per website in admin Website settings → Identity (website superadmin). There is no REST or MCP API for VAPID keys yet.

Identity Admin panel

In the admin panel

Under Identity → Web push, generate VAPID keys once, then enable member push. Preview websites cannot enable push until the site is active. Members opt in on the public site via button consent mode (push or all) and browser permission.

Tenant vs admin push

Tenant push uses per-website keys stored in the database and targets website_user subscriptions. Admin push (platform users, object-type alerts) is configured in User settings and uses separate platform VAPID credentials — see the Admin panel interface guide.

When push is sent

Push is a parallel channel to in-app notifications: when createWebsiteNotifications runs (lifecycles, mentions, etc.), subscribed members also receive a browser notification if they opted in. Delivery never blocks the primary notification write.