Account & Partner Compliance

Multi-tenant MSP platforms attract abuse. Compromised cards, proxy-rotated signups, and bad actors hiding behind shell organizations are operational realities, not edge cases. Breeze ships the controls to stop abuse fast and keep an audit trail of every lifecycle decision — so one bad partner cannot put the rest of the platform at risk.

Email Verification on Signup

Every new partner must verify their email before the account can manage devices. The link is signed, resend is one click, and the user-facing copy distinguishes “this link was replaced” from “this link was already used” so the message matches reality.

The gate runs before any meaningful tenant capability unlocks. That closes the easiest abuse pattern: spin up a partner with a throwaway address, never read the mailbox, enroll devices anyway.

Activation Gate for Paid Signups

For paid signups, email verification and payment work together. When a card is attached and the email is then verified, the partner activates automatically and the “Awaiting email verification” banner clears. Until both conditions are met, the tenant is in a holding state — visible to platform admins, not yet able to operate.

A fraudulent card test doesn’t immediately yield a working tenant. A typo’d signup email doesn’t strand a real customer behind a support ticket — they finish verification and activation completes on its own.

One-Call Abuse Suspension

Platform admins can take down an abusive partner with a single API call. The suspension endpoint performs the full coordinated cleanup:

• Every device under the partner is queued for self-uninstall.
• Active sessions are deleted.
• Non-admin users are disabled.
• API keys are revoked.
• JWTs are blanket-revoked so no in-flight token survives.

The endpoint fails closed if any step fails — operators never get a misleading success while half the cleanup is still pending. An unsuspend endpoint covers the reversal path when the call was issued in error or the partner has resolved the underlying issue.

Before this shipped, removing an abusive tenant was a hand-written SQL transaction across half a dozen tables, run under pressure with the operator hoping nothing got missed. Now it’s one POST and the affected agents self-uninstall on their next check-in.

Lifecycle Audit Trails

Every suspension, unsuspension, and activation event is recorded with actor, target partner, timestamp, and reason. Audit data is durable and queryable, so platform admins can reconstruct what happened to a specific tenant, demonstrate to a downstream auditor that abuse controls were applied consistently, and spot patterns across multiple takedowns.

Activation events log the same way. A partner moving from “awaiting verification” to “active” is a real lifecycle transition, not a silent state flip.

Why It Matters for MSPs

These controls protect every legitimate MSP on the platform from a small number of bad actors:

• Containment. Abuse is bounded to the offending partner. No shared path back into the rest of the platform.
• Speed. A single API call replaces a multi-step cleanup, so operators respond in seconds, not during a half-hour incident window.
• Reversibility. Suspensions are explicit and reversible. Good-faith partners caught by a false signal can be restored cleanly.
• Transparency. Every action is in the audit trail, available to platform admins and to the partner whose account was affected.

For hosted-cloud partners, the payoff is indirect but real: a platform that responds to abuse quickly stays healthy, stays available, and keeps abuse-detection cost out of your subscription. Self-hosted operators get the same controls to apply to their own tenants — suspension, verification gate, and audit trails ship together.

Learn More

• Security Monitoring — Encrypted secrets, forced row-level security, and the trusted-proxy controls that round out platform-side defenses.
• Authentication & Authorization — The identity layer underneath the activation and suspension flows.