Skip to main content

ClientOne Admin

Navigation: Sidebar → ClientOne Admin (visible to Owners and Admins only)

ClientOne Admin is where MSP owners and admins configure ClientOne — the client-facing app where your customers view devices, submit tickets and service requests, access documents, and complete onboarding.

ClientOne Admin

Overview​

ClientOne Admin is organized into tabs:

TabPurpose
ConfigurationEnable ClientOne per client, invite end users, branding, per-client SSO
Customer UsersManage end-user accounts for ClientOne
Service RequestsView and manage service requests from ClientOne users
OnboardingCreate and manage customer onboarding workflows
AgreementsManage agreements for customers to review/sign
ActivityView activity from ClientOne users
ClientOne ticketsMSP-wide dropdown options for the ClientOne ticket form
ClientOne SSOMulti-tenant Microsoft 365 sign-in for ClientOne (setup guide)

Configuration​

Navigation: ClientOne Admin → Configuration (/clientone-admin/settings)

Enabling ClientOne for a client​

  1. Find the client in the list
  2. Toggle ClientOne enabled
  3. The client's end users can access ClientOne

The configuration page shows:

  • All your clients listed
  • ClientOne enabled/disabled status for each
  • Quick stats: how many clients have ClientOne enabled

Inviting customer users​

  1. Click Invite on a client's row (when ClientOne is enabled)
  2. Fill in the invite form (Email, Name, Role: User or Manager)
  3. Click Send Invite
  4. The customer receives an email with a link to create their account

Roles:

  • User — Standard ClientOne access (view devices, create tickets, view documents)
  • Manager — Extended access across that client's devices/users per your assignments

Per-client branding​

  1. Click Configure (branding) on a client's row
  2. Set logo, colors, welcome message as needed
  3. Save changes

Per-client SSO (Entra)​

  1. Click SSO on a client's row
  2. Configure parameters for that client's identity provider
  3. Save

For MSP-wide Microsoft 365 sign-in for all tenants, configure ClientOne Admin → ClientOne SSO.

Routes: /clientone-admin/settings — legacy /portal-admin/settings redirects here.

Customer Users​

Navigation: ClientOne Admin → Customer Users (/clientone-admin/customers)

  • View customer users across clients (or scoped by header client selector)
  • Roles, activation, device assignments
  • Invite flow links back to Configuration

Service Requests​

Navigation: ClientOne Admin → Service Requests (/clientone-admin/service-requests)

View and manage service requests submitted by ClientOne users.

Onboarding​

Navigation: ClientOne Admin → Onboarding (/clientone-admin/onboarding)

Creating an onboarding workflow​

  1. Open ClientOne Admin → Onboarding
  2. Define steps (for example agreements, credentials, kickoff)
  3. Send or assign onboarding to clients as supported in the UI

Tracking progress​

Use Client Status to see completion and follow up stalled onboardings.

Agreements​

Navigation: ClientOne Admin → Agreements (/clientone-admin/agreements)

Create and manage agreements end users acknowledge in ClientOne.

Activity​

Navigation: ClientOne Admin → Activity (/clientone-admin/activity)

Audit-style feed of actions from ClientOne users (tickets, requests, onboarding, agreements, etc.).

ClientOne tickets & ClientOne SSO (MSP-wide)​

  • ClientOne tickets — /clientone-admin/ticket-fields — customize priorities/categories/options for ticket creation in ClientOne for your MSP.
  • ClientOne SSO — /clientone-admin/sso — multi-tenant Azure app registration and optional Partner Center values for Sign in with Microsoft 365 on ClientOne.

Legacy Settings URLs (/settings/clientone-ticket-fields, /settings/clientone-sso) redirect to these tabs.

Client-scoped view​

When you select a client in the header Client selector, Configuration, Customer Users, Service Requests, Activity, and related views can filter to that client.

Tips & best practices​

  • Roll out ClientOne gradually; tighten branding and onboarding per client type
  • Configure ClientOne SSO early if most users should use Microsoft sign-in
  • Use agreements and onboarding to reduce onboarding email back-and-forth
  • Invite managers where they help distribute access within the client org