Tenant Onboarding

Client

Connect WhatsApp via Meta

Launches Meta's Embedded Signup flow for the selected tenant. Business/WABA/phone details are captured for review — this does not automatically provision the channel.

No tenant selected yet — add or pick a client above.

Captured Signup Events

Select a tenant to view captured events.

WhatsApp Setup Checklist

Live status for the selected tenant, read straight from our records — nothing here calls Meta by itself. Use the actions below to advance each step; the checklist refreshes automatically after every action.

Select a tenant to view its setup status.

Client API Credentials

For the client's own technical integration only — not needed for WhatsApp onboarding above.

Tenant ID Select a tenant

API Base URL —

Select a tenant to view its API key.

⚠️ Shown once — copy it now. It will not be shown again.

This API key is confidential and grants this tenant's full API access. Share it only with the client's own technical integration contact, over a secure channel — never in chat, email body, screenshots, or anywhere a third party (including Meta) could see it.

Portal Users

Client-portal login accounts for the selected tenant. Inviting or reinviting a user calls the existing POST .../portal-users / .../reinvite endpoints — this panel only adds a "Copy invite link" helper so you don't have to hand-build the URL from the raw token yourself.

Select a tenant to view its portal users.

Message Use-Case Mappings

Maps a purpose (login, registration, password_reset) to one Approved Authentication template on this tenant's own WhatsApp channel — this is what POST /api/v1/use-cases/otp/send actually resolves and sends at OTP time. Calls the existing .../use-cases endpoints as-is (list/create/delete); create additionally rejects a template that isn't Authentication category or isn't Approved, and every row shows the template's current status live, not just what it was when the mapping was made.

Select a tenant to view its use-case mappings.

Active Sessions

Platform-wide, not scoped to the tenant selected on the left — every portal user across every tenant who currently holds a valid, unexpired login session (GET /api/v1/admin/active-sessions). This is "could resume their session without logging in again," not real-time presence — this app has no live/online tracking, so someone who logged in weeks ago and hasn't opened the portal since still counts until their session actually expires. Times are shown in IST regardless of your own browser's timezone.

Loading…