Skip to main content

ClientOne

URL: app.clientone.dev (default). Your MSP can configure a custom ClientOne origin (for example a white-label domain) in Settings → ClientOne SSO; when set, end users use that host instead of app.clientone.dev.

For developers and preview: On localhost or a preview host, the same app mode is also available with ?app=customerportal in the query string, matching how the product routes ClientOne in code.

ClientOne is the client-facing side of PanelOne. It gives your clients a self-service interface to view their devices, submit support tickets, access documentation, review agreements, and complete onboarding — all branded with your MSP's identity.

The legacy hostname portal.panelone.dev is not a supported default URL; use app.clientone.dev (or your configured ClientOne origin) for documentation and end-user support.


How end users access ClientOne

Invite Flow

  1. An MSP admin sends an invite from Portal Admin → Configuration
  2. The end user receives an email with an invite link
  3. They click the link to accept the invite and create their account
  4. They set their password and can then sign in at https://app.clientone.dev (or your custom ClientOne URL)

Sign In

  • Navigate to https://app.clientone.dev/login (or your custom sign-in URL)
  • Enter email and password
  • If MFA is required, enter the authenticator code

Password Reset

  • Click "Forgot password?" on the login page
  • Receive a reset link via email
  • Set a new password

End-user dashboard

Navigation: ClientOne → Dashboard (landing page after login)

The dashboard provides an overview of the end user's services:

Welcome Message

A personalized greeting using the customer's name and a configurable welcome message set by the MSP.

Stats Cards

CardShows
Open TicketsActive support tickets
DevicesTotal managed devices
BackupsBackup count
DocumentsAvailable published documents

Onboarding Prompt

If the customer has an active onboarding workflow, a prominent card appears:

  • Shows current onboarding step
  • "Continue" button to proceed with onboarding
  • Progress indicator

Devices

Navigation: ClientOne → Devices

End users can view their managed devices:

  • Device list with names and status
  • Online/offline indicators
  • Basic device information (OS, type)

Note: This is a read-only view. End users cannot perform device actions.


Tickets

Navigation: ClientOne → Tickets

End users can view and create support tickets:

Viewing Tickets

  • List of all tickets for their organization
  • Status indicators (open, in progress, resolved)
  • Priority badges
  • Click to view ticket details

Creating a Ticket

  1. Click New Ticket (or go to ClientOne → Tickets → New)
  2. Fill in:
    • Title — Brief description of the issue
    • Description — Detailed explanation
    • Priority — Low, Medium, High, Urgent
  3. Click Submit
  4. The ticket appears in both ClientOne and the MSP's PanelOne ticket queue

Ticket Detail

Click any ticket to see:

  • Full ticket information
  • Status updates
  • Communication history
  • Resolution details

Backups

Navigation: ClientOne → Backups

End users can view the status of their backups:

  • Backup list with status indicators
  • Healthy, at-risk, and failed statuses
  • Last backup timestamps

Documents

Navigation: ClientOne → Documents

End users can access published documentation:

  • Documents published by the MSP for this client (or for all clients)
  • Organized by category
  • Search and browse
  • Click to view full document content

Document Detail

Click any document to read the full content, including rich text formatting.


Agreements

Navigation: ClientOne → Agreements

End users can review and acknowledge service agreements:

  • List of agreements assigned to their organization
  • Agreement content and terms
  • Acknowledgement status
  • Option to acknowledge/accept agreements

Onboarding

Navigation: ClientOne → Onboarding

If the MSP has created an onboarding workflow for this customer:

  • Step-by-step onboarding checklist
  • Progress tracking
  • Complete steps one at a time
  • Each step may require information input or acknowledgement

The onboarding prompt also appears on the dashboard.


Profile

Navigation: ClientOne → Profile

End users can manage their account:

  • Update display name
  • Change email address
  • Update password
  • View account information

Branding

ClientOne can be customized per client by the MSP:

  • Custom logo
  • Custom color scheme
  • Custom welcome message
  • White-label appearance

Custom ClientOne origin (optional): In Settings → ClientOne SSO, the ClientOne origin field can point to a white-label host (for example https://portal.yourmsp.com) instead of the default https://app.clientone.dev. The Microsoft Entra and redirect configuration must match the origin you set.

This means each of your clients can see ClientOne branded to their (or your) organization.


What the MSP controls

As the MSP, you control everything about ClientOne through Portal Admin:

ControlWhere
Enable/disable ClientOne per clientPortal Admin → Configuration
Invite end usersPortal Admin → Configuration
Customize branding per clientPortal Admin → Configuration → Branding
Configure SSO per clientPortal Admin → Configuration → SSO
Microsoft 365 “Sign in with Microsoft 365” (ClientOne SSO)Settings → ClientOne SSO (MSP-wide) and per-client consent on the client record
Manage end-user accountsPortal Admin → Customer Users
Create onboarding workflowsPortal Admin → Onboarding
Manage agreementsPortal Admin → Agreements
Publish documentsDocuments → customer-visible document workflow

For Microsoft Entra SSO to ClientOne (per client’s tenant), see Configuring Entra ID SSO for ClientOne (MSP guide).


Tips & Best Practices

  • Brand ClientOne before inviting end users — First impressions matter
  • Start with documents — Have FAQ and basic guides ready before enabling access
  • Use onboarding workflows — Guide end users through their initial setup smoothly
  • Monitor ticket creation — ClientOne tickets go directly to your PanelOne ticket queue
  • Encourage self-service — The more useful your published documents are, the fewer support tickets you'll receive
  • Set up agreements first — Have terms of service ready for end users to acknowledge