VAI Oman Marketing Hub Settings & Governance

Tenant Policy, Master Login Vault, Team Personas (`X-Actor-Token`), API Keys, Signed Webhooks & Oman PDPL

1. Master Connected Logins & KMS Vault Inventory 0

Shows all connected channel logins visible to the active Tenant + Actor Persona. Private `user`-scoped logins belonging to other staff members remain cryptographically & scope-hidden.

Channel Account Display Name Scope Masked Login / Fingerprint Retention Status Actions

2. Tenant Governance, Kill Switch & Oman Policy

Configure workspace defaults (`Wilayat`, `OMR/Baisa`), mandatory executive HMAC `approval_receipt`, and emergency Global Outbound Kill Switch.

First-Party Oman PDPL Edge Pixel Snippet (`/p/:slug.js`)

3. Team Users / Personas & Signed `X-Actor-Token`s

Pass a user's signed X-Actor-Token from your upstream app to isolate their private `user`-scoped logins, WhatsApp DMs, and OTP prompts.

4. Tenant API Keys (`X-Api-Key`) & Outbound Webhooks

Issue SHA-256 hashed API keys for your upstream backend (`diamondstonex.com`, `alhiba.om`, FastAPI/SvelteKit) and configure HMAC-SHA256 (`X-Vai-Hub-Signature-256`) webhooks.

Signed Webhook Endpoints

5. Oman PDPL (`Royal Decree 6/2022`) Opt-Out Suppression Registry

Any `+968` mobile number or email listed here is automatically blocked (`451 E_PDPL_SUPPRESSED_RECIPIENT`) across WhatsApp & Omantel/Ooredoo/Vodafone SMS broadcasts.