Partner Console overview
What the partner console is, where it lives, and how it sits next to the customer portal.
The Partner Console is a dedicated, separate console for partners who
operate WASViking® on behalf of customers. It lives at
partners.wasviking.com (and partners.localhost in dev). It is
isolated from the customer portal by host, by URL config, by identity
table, and by data access boundary.
Who uses it
| Audience | What they do |
|---|---|
| Resellers | Quote, provision, manage commercial accesses for customers. |
| MSSPs | Operate the platform for customers under co-managed or fully-managed engagements. |
| Technology Alliances | Use the public REST API; the console is supplementary. |
What lives in it
- Dashboard with charts: customer portfolio funnel, quote pipeline, plan mix, top customers by partner cost, aggregate security posture.
- Customers list with operating model, plan, status, usage.
- Customer detail with real posture metrics (gated by operating model).
- Quote engine with live price preview.
- Quotes in flight.
- Billing with consolidated monthly previews, PDF and CSV export.
- Demos with ephemeral fully-populated tenants, 24h auto-destroy.
- Team with role-gated invites and anti-lockout.
- Audit log scoped to the partner.
- Help & FAQ humanized, bilingual.
- Settings with language switcher.
What is NOT in it
- Customer-managed engagements do not show posture data. The partner sees commercial state only. This is enforced in code, not in a contract clause.
- WASViking-side staff tools for managing partners live on the internal portal host, not on the partner host.
- Real session impersonation does not exist. Impersonation is a read-only console preview only, audited.
- White-label / custom branding is a permanent design decision: it is not implemented and will not be. The Partner Console is WASViking- branded.
How a partner gets access
- Partner submits an application at
partners.wasviking.com/apply. B2B email policy refuses free, public, and disposable domains at submission, same engine as customer registration. - WASViking staff review the application and either approve or decline.
- On approval, the partner admin gets an invitation email with a one-time set-password link.
- The partner admin sets a password, sets MFA, and lands on the Partner Dashboard.
Identity boundary
The Partner Console runs on a separate identity table (PartnerUser,
session key partner_user_id). Partner operators are not Django users.
The customer portal cannot see partner operators; the partner host
cannot see customer users. This is by design and is enforced at every
view.
Multi-tenancy
A partner can manage many customer accesses. Each access is a soft reference to a customer organization, not a hard foreign key, so the two schemas remain independent and migrations stay separate.