Customer Self-Service Portal

Let Customers Order, Change and Operate Their Own Services

Every seat added by email, every “can you restart this VM”, every request for last month’s invoice is margin leaving through the support desk. The work is trivial. The cost is that a person has to do it.

Hybr® gives each customer, reseller and business unit a branded portal where they order from your catalog, change what they already have, operate their own resources and see their own spend — inside limits you set, with fulfilment and billing happening automatically behind them.

How a self-service request is fulfilled in HybrA customer, reseller or business unit acts in the portal — ordering from the catalog, adding or removing seats, starting or resizing a virtual machine, or downloading an invoice. Every action passes through a guardrail layer that checks role and scope, requires approval where policy demands it, enforces quota and budget limits, and applies that customer’s price list. Fulfilment then happens automatically: the service is provisioned, the subscription record is updated, usage is metered and rated, and the audit trail is written. No ticket is raised and no operator is involved.What a customer does without raising a ticketEvery self-service action passes the same guardrails, then fulfils itself — and bills itself.THE CUSTOMER ACTS IN THE PORTALOrder from the catalogsubscriptions, VMs, add-onsChange what they haveseats up or down, upgradesOperate their resourcesstart, stop, resize, snapshotAnswer their own questionsusage, spend, invoicesGUARDRAILS — APPLIED TO EVERY ACTIONRole and scopeApproval where requiredQuota and budget limitsCustomer price listFULFILLED WITHOUT AN OPERATORProvisionedPartner Center, vCenter, Azure, K8sSubscription updatedterm, seats, effective dateMetered and ratedagainst the right price listLogged and auditablewho did what, and whenOne portal, three audiencesEnd customers · resellers selling under their own brand and price list · internal business units charged back — the same portal, scoped by role.

The three things that make self-service work

A catalog on its own is a brochure. Self-service only removes work when all three of these are true:

  • Scope. Each user sees only their own tenant, subscriptions and resources, at the level their role allows — a customer administrator sees more than one of their end users, and a reseller sees their own customers.
  • Guardrails. An action either fits policy, quota, budget and approval rules or it is not offered. There is no path to an outcome you did not sanction.
  • Fulfilment. The request provisions the service, updates the subscription record, starts the meter and applies the right price list. If a person still has to finish it, nothing was saved.

What customers can do for themselves

  • Order from your catalog — subscriptions, virtual machines, Kubernetes namespaces, managed services and add-ons, priced with their own rate card.
  • Change what they already have — add or remove Microsoft CSP seats, upgrade or downgrade a plan, extend or cancel within your policy. See Microsoft CSP license management.
  • Operate their resources — start, stop, restart, resize and snapshot VMs across VMware vCenter, Azure Local, Hyper-V and Azure.
  • See their own consumption and spend — rated usage while the period is still open, not a surprise at invoice time.
  • Handle their own billing admin — invoices, payment methods and billing contacts, without a request to your finance team.
  • Manage their own users — invite people, assign roles, remove leavers, within the boundaries you defined.

One portal, scoped three ways

  • End customers get your brand, your catalog and their own resources.
  • Resellers get their own branded tier, their own price list and margin, and the ability to onboard and manage their customers underneath them — see reseller management.
  • Internal business units get the same experience as a chargeback model, ordering from an approved catalog against a departmental budget.

Guardrails, so self-service is not a blank cheque

Every action is checked before it happens, not reconciled afterwards:

  • Role and scope decide what appears in the catalog at all.
  • Approval steps can be required for specific items, sizes or spend levels.
  • Quotas cap how much of a resource a tenant can hold.
  • Budgets and thresholds alert or block against rated usage — see usage-based & metered billing.
  • An audit trail records who did what, and when, per tenant.

What it changes

  • Tickets that never get raised. Seat changes, restarts and invoice requests stop reaching a human.
  • Provisioning in minutes. The order is the fulfilment — there is no queue between them.
  • Fewer billing disputes. Customers watch their own spend accrue instead of discovering it.
  • Headcount that scales with revenue, not with tenants. Adding the hundredth customer costs what the tenth did.

Self-service is the last stage of the lifecycle Hybr automates — see onboarding & lifecycle management for the stages that come before it.

Frequently asked questions

What is a cloud self-service portal?

A self-service portal is a branded web front end where your customers, resellers or business units order and manage the services you sell them — without going through your support desk. In practice it needs three things to be more than a catalog: role-based scoping so each user only sees what is theirs, guardrails so an action cannot exceed policy or budget, and automated fulfilment so the request is actually provisioned and billed rather than queued for someone.

What can a customer do in the Hybr® portal without contacting support?

Order from your catalog, add or remove Microsoft CSP seats, upgrade or downgrade a subscription, start, stop, resize or snapshot a virtual machine, request a new environment, view rated usage and current spend, download invoices and manage their own users. Each of those is scoped by role, so a customer’s administrator sees more than one of their end users.

Can we control what each customer is allowed to do?

Yes. Every action in the portal is governed by role, scope and policy. You decide which catalog items a tenant can see, which operations each role can perform, what needs an approval step, and what quota or budget ceiling applies. Anything outside that is simply not offered.

Does the portal work for resellers as well as end customers?

Yes — that is a distinct tier rather than the same screen with a different logo. A reseller gets their own branded portal, their own price list and margin, and the ability to onboard and manage their own customers underneath them, while you keep visibility of the whole chain. See reseller management.

Can the portal be branded as ours?

Yes. Logo, colours, domain and email templates are yours, and resellers can apply their own branding within their tier, so the end customer sees the company they bought from.

Does letting customers self-serve risk uncontrolled spend?

It is the opposite, provided rating is continuous. Because usage is rated against the customer’s price list while the period is still open, quotas and budget thresholds can block or alert on an action before it becomes an unbilled write-off. See usage-based & metered billing.

Related: Self-service in the commerce platform · Onboarding & Lifecycle Management · Reseller Management · Pricing & Rate Management · Usage-Based & Metered Billing

See it with your own catalog

Bring the three requests your support desk handles most often. We will show you the portal your customers would use to do them without you.