Partner Management

Breeze is designed around a partner-first multi-tenant model. MSPs register, manage their customers, and control access — all within a clean hierarchy built for service delivery.

Self-Service MSP Registration

MSPs can create their own Breeze account directly from the registration page. The flow creates a partner account, an admin role, and a user in a single operation. Rate limiting, email uniqueness checks, and password strength validation are all enforced server-side, with enumeration-safe error messages that protect your customer data from day one.

Partner and Organization Hierarchy

Partners sit at the top of the tenant tree. Under each partner are organizations, sites, device groups, and devices. Every API call automatically scopes data to the caller’s position in the hierarchy — partner users only see what they are authorized to see, and organization users stay contained to their own account.

Three Organization Access Levels

Partner users can be granted access to all organizations, a selected subset, or none at all. This makes it straightforward to model technician roles that are scoped to specific customers, account managers who oversee a defined book of business, or billing contacts who only need partner-level settings.

Plan and Feature Controls

Partners are assigned a plan tier — free, pro, enterprise, or unlimited — that governs device and organization caps. System administrators can provision partners directly with explicit limits and types. Partners manage their own display name, billing contact, and operational settings through a self-service endpoint that merges changes rather than replacing the full settings object.

Service Delivery Ready

The partner model supports the operational reality of MSP work: multiple customers, multiple technicians, and the need to control what each person can see and do. Breeze enforces these boundaries at the API level so access control is not a configuration exercise — it is built into the data model.