Monitor every workspace and every user, and act on any of them — plan, status, seat cap, session revocation, password reset, and audited "Login as". Nothing here touches a tenant's own login; this is the control plane.
Monitor and act on every workspace and user. Restricted to control-plane administrators.
Live snapshot of every account. Use the inline controls, Open a workspace to drill into its users, or create/delete a whole workspace here.
Every user in this workspace. "Login as" mints a short-lived, audited tenant session; "Kill" revokes all of a user's sessions; "Reset" issues a one-time password link; "Delete" removes the user permanently.
| Name | Role | Active | Last seen | Leads | Calls today | Actions |
|---|
The workspace's latest lead activity feed (newest first).
Your own Razorpay / Stripe keys — the ones this business collects subscription money with. Every secret is encrypted with AES-256-GCM the moment it is saved and is never sent back to this screen: a field can only ever tell you whether something is stored. A workspace's own gateway, for collecting fees from its customers, is a separate setting inside that workspace.
Manual is the honest default: you set each account's plan and status by hand and invoice off-platform. Saving keys here does not start charging anyone — subscription checkout is not built — but it does put the keys in the server's hands, and the live check below proves they work.
Dashboard → Account & Settings → API Keys for the pair, then Settings → Webhooks for the secret. A key beginning rzp_test_ authenticates perfectly and collects nothing real — the live check names which kind you pasted.
Dashboard → Developers → API keys for the pair, then Developers → Webhooks for the signing secret (it begins whsec_). The publishable key is not a secret and is shown back to you; the secret key is not.
What actually reached those URLs, and whether its signature verified against the secret saved above. A rejected delivery is recorded too — the gateway's own dashboard shows you a bare 401 and nothing about why. Send a test event from the gateway, then refresh.
Nothing has arrived yet.
Deliveries are verified and logged, and nothing else: an inbound event never changes a plan, a status or a trial. That stays a decision you make on the workspaces screen, so no payload can buy an upgrade.