#1
Loading Channel...
1. Put Login Details & Seal in KMS Vault
Credentials are encrypted with a fresh 256-bit AES-GCM DEK bound to tenant_id|scope|owner_user_id|account_id. Plaintext secrets are never returned in API reads.
2. Connected Logins & Channel Settings 0
Test Vault AAD cryptographic health, trigger OTP verification, toggle per-account Kill Switch, edit credentials, or configure delegated user grants (`ACCOUNT_GRANTS`).
Delegated User Access (`ACCOUNT_GRANTS`)
Allow another team persona to draft or publish on a private `user`-scoped account (while keeping private DMs isolated unless `can_read_inbox` is checked).
3. Per-Channel Feature Test & 5-Point Readiness Evaluator Not Run Yet
Evaluate every capability of this integration either using your saved login details above OR in zero-credential fixture_sim sandbox mode. Checks KMS AAD, User Scope, Oman Baisa/Wilayat/TRA/PDPL compliance, platform limits, and engine routing.