Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

What partners need to see that end customers should not

Technical article
Hosting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Direct answer: Give partners cross-tenant operational views they need to resell and support—billing metadata, health summaries, provisioning actions and escalations—while end customers see only their own organisation, users and data. Anything that mixes the two (partner browsing customer records “for convenience”) becomes a privacy incident and an audit finding waiting to happen.

Why it matters

Many Australian ISVs sell through accountants, integrators or vertical specialists (editorial judgement — channel mix varies by product). Partners need enough visibility to quote, provision sandboxes and chase renewals. End customers expect their payroll, clinical or financial data stays invisible to the partner’s entire sales desk.

Confusion here shows up as support tickets (“why can your reseller see our users?”), broken trust at renewal, and Privacy Act questions you cannot answer with a vague “they’re trusted.” Delegated access must be purpose-bound, logged and revocable—this is design work, not a checkbox on the partner agreement.

Hosted delivery on managed infrastructure does not remove the ISV’s obligation to define who sees what in the application and portal layers. The hoster may offer admin roles for servers and networking; your product still owns tenant-scoped RBAC.

How it works

Think in three planes:

Commercial plane (partner-visible)
Subscription status, SKU, renewal date, contract tier, implementation milestones, named partner account manager. Partners usually need aggregate usage for sizing conversations—not row-level transaction detail unless the customer explicitly opts in for a professional services engagement.

Operational plane (partner-limited)
Provisioning new tenants, resetting demo environments, opening tickets on behalf of the customer, viewing platform-wide release notes and maintenance windows. Partners may need read-only health for tenants they manage (up/down, version, open incidents) without opening the customer’s business records.

Tenant plane (customer-only)
User directory, application data, audit logs of who changed what inside the tenant, integration secrets, exports. Partners access this plane only through customer-granted roles (e.g. delegated admin for a migration week), with start and end dates.

The Australian Signals Directorate’s cloud shared responsibility guidance states that customers cannot outsource governance risk to a cloud provider. Application-level access control for partners and customers remains the ISV’s design problem when a hoster runs the VMs. NIST defines software as a service as a model where the consumer does not manage the underlying cloud infrastructure but may configure limited user-specific application settings—useful context for where portal RBAC sits. Least privilege (NIST glossary) and separation of duties are the practical rules—partners get the smallest role that still lets them earn margin.

A simple role matrix helps:

Capability ISV ops Partner End-customer admin End-customer user
Create tenant shell Yes Often yes No No
View cross-tenant list Yes Only assigned accounts No No
Read customer application data Break-glass only Only with customer grant Yes (scoped) Own records
Billing and commission Yes Own deals only Own invoice No
Platform maintenance notice Yes Yes Yes Optional

Logging should show which principal acted: partner SSO separate from customer SSO avoids ambiguous “support@isv.com” shared logins.

What to choose and why

Named partner organisations, not individual sharing. Assign roles to the partner’s Entra/IdP group or service accounts; rotate when staff leave.

Customer-granted elevation, time-boxed. Migration or go-live support gets a documented window; auto-expire elevated partner access.

Separate URLs or clear UI affordances. If partners and customers share one portal, visual and navigational separation reduces “wrong tenant” clicks.

Default deny on cross-tenant APIs. Internal admin APIs that list all tenants belong behind ISV staff auth, not partner keys.

Risks and limits

  • Impersonation features are powerful and dangerous; require MFA, reason codes and customer notification where appropriate.
  • Partners with export rights can exfiltrate data as easily as customers; contractual terms are not technical enforcement.
  • Multi-tenant bugs that ignore tenant filters are catastrophic—treat visibility tests as release gates, not pen-test surprises.
  • This article is not legal advice on the Privacy Act or Australian Privacy Principles; involve qualified counsel for subprocessors and cross-border visibility.
  • Design is ISV product responsibility on hosted infrastructure.

Sources

Related reading

Learning notes

  1. Partner visibility is a product RBAC problem, not a hosting SKU detail.
  2. Commercial metadata and tenant data should use different roles by default.
  3. Time-boxed elevation beats permanent “super partner” accounts.
  4. Shared logins destroy audit trails—use federated partner identities.
  5. Test cross-tenant isolation on every release that touches authorisation.