Back to workspace
AXORIK Help Center
Learn by outcome

What do you want to accomplish?

Find a workflow, understand live evidence or learn the safest next step. Search by the job you need to complete, not only by a feature name.

MSP service delivery 6 minute read Lesson 19 of 19

Deliver a branded client portal

Give each customer a clear view of health, service work, approvals and reports.

MSPMSP client
Complete this lesson, then continue through the system0 of 19 completed

Outcome

The client sees value and evidence without unrestricted operator access.

Where to find it

Partner Portal > Customers > Select customer > Client portal

Start here

Complete guide to Deliver a branded client portal

When you do this

Use the client portal after the MSP customer and its sites exist, when you are ready to give the customer a controlled view of the managed service.

What this means

The client portal presents customer-specific health, service requests, approvals, completed work and reports under the MSP brand. It is not the operator portal and must never expose another customer or unrestricted network controls.

Before you start

  • The selected customer has the correct name, sites and service package.
  • Brand, support contacts and welcome message are complete.
  • The client administrator and any read-only users are identified.

Do this step by step

  1. 1Configure the Branded service header and customer support details.
  2. 2Choose which health, requests, work history, reports and approval capabilities are included.
  3. 3Invite the client administrator and give approval authority only where required.
  4. 4Test the portal while signed in as a client user.
  5. 5Submit a test service request and confirm it reaches the MSP Service queue.

How to know it worked

The client sees only its own organization, the intended service modules and a working request or approval flow under the correct MSP brand.

If it does not work

  • If data is missing, confirm the site belongs to this customer and is included in the service package.
  • If a user cannot approve, verify that the user is the designated client administrator.
  • If a request does not reach Service, confirm the selected customer and site association.

Important

Client approval records permission for the reviewed scope. It does not execute a network change automatically.

What you will see on this page

These are the exact AXORIK sections to look for. Read them in the order shown unless the complete guide directs you to a specific finding.

1

Branded service header

Shows the provider identity, service package and customer-specific welcome message.

2

Network health

Summarizes sites, online devices and open findings without exposing operator controls.

3

Changes awaiting your decision

Lets an authorized client administrator approve or decline a clearly scoped request. Approval alone does not execute the change.

4

Managed locations

Shows which customer sites are currently included and monitored by the provider.

5

Need your provider?

Creates a tracked service request with site, priority and business-impact details.

6

Your service requests

Shows the client the current state of requests already sent to the provider.

7

Work performed for you

Lists completed and verified service activity instead of an unexplained activity log.

8

Reports and proof of service

Lets the client view or download the evidence packs the MSP has made available.

Recommended workflow

Follow these steps in order. If a step is blocked, resolve it before moving to the next one.

1

Set the customer identity

Configure brand, support contacts, service package and welcome message inside the selected customer.

2

Choose client visibility

Enable only the health, service requests, service activity, reports and approvals included in the service promise.

3

Invite the correct roles

Give approval authority only to the client administrator. Other client users receive the appropriate read-only service view.

4

Test the client journey

Sign in as a client, verify the brand and customer scope, send a service request and confirm it reaches Service.

5

Prove the service every month

Publish completed work and deliver branded reports so the customer can see the value of the subscription.

Safety and interpretation

  • Client access must never cross organization boundaries.
  • Only a client administrator can approve a change.
  • Approval records permission but does not execute automatically.
  • Branding does not change evidence ownership or operator responsibility.

AXORIK Essentials lesson 19 of 19

Can you now explain when and why to use this feature?

Mark it complete only when you know where to find it, what its main sections mean and what the safe next step is.