Least-privilege scope
API credentials are issued with explicit scopes instead of reusing an owner browser session.
Partner operations
One scoped service account for delegated customer operations
An MSP with forty clients should not automate through browser sessions that belong to individual administrators. Partner API access gives automation a scoped service account, delegated workspace boundaries and auditable operations.
Partner API is a BusinessProxy-branded integration surface. It is not full partner-branded legal identity, billing, support or customer portal white-labeling.
Scoped service accountsDelegated workspace operationsNo shared administrator accountAudit-friendly automation
Operating model
Automation gets a narrow identity
Service accounts should have exactly the operations they need: create customer workspaces, configure apps, inspect status or export events depending on delegated scope.
Delegated customers
Partner operations can be limited to customer workspaces that delegated access to the partner.
Rotation and audit
Credential lifecycle should be visible, rotated and tied to audit events.
Use cases
Where partners use it first
The practical first use is not a new platform. It is reducing repetitive setup and support operations across many customer workspaces.
- Create or update customer app configurations.
- Check connector and private-app readiness.
- Export operational events into partner tooling.
- Rotate partner-owned credentials without sharing human passwords.
Current boundary
Partner automation, not full reseller platform
Partner-branded billing, legal identity, support desk, email sender and customer-portal white-labeling are available only when they are explicitly included in a partner rollout.
- No shared administrator account as the automation model.
- The API is not intended for platform-wide administration.
- A full partner-branded platform is not included.
Next step
Review the rollout details before turning it on
The documentation page shows what to configure, how to verify the setup and which operational boundaries to review before rollout.