Skip to main content

Client Portal Configuration

Manage who can access your client-facing portal and review the self-service access requests clients submit. This page is for MSP admins; it does not configure what your customers see once they log in.

The Client Portal feature requires the client portal license feature. If your plan does not include it, this page shows an upgrade prompt instead of the settings below.

Overview

The AdminClient Portal page lets you:

  • Review portal access requests submitted by people who want a portal login
  • Approve a request (which links or creates a contact and emails them an invitation) or reject it
  • Filter requests by status (Pending, Approved, Rejected, or All)
  • Copy a shareable Request Access Link that pre-fills your service provider identifier

Portal branding (logo, icon, and color) is configured separately in Org Settings, not on this page. See White-Label Branding below.

Go to AdminClient Portal (/admin/portal). Access requests are restricted to users with the Owner or Admin role.

Portal Access Requests

When a prospective portal user submits the request-access form, it appears here as a pending request for an admin to review.

Request columns

ColumnDescription
RequesterThe name and email address the person entered
CompanyThe company name they entered, or Not specified if blank
StatusPending, Approved, or Rejected
RequestedThe date the request was submitted
ActionsApprove / Reject buttons for pending requests; the review date for resolved ones

Filter by status

Use the status dropdown in the top-right of the Portal Access Requests card to switch between:

  • Pending (default) — a badge shows the pending count
  • Approved
  • Rejected
  • All

Approve a request

  1. Find the pending request in the list.
  2. Click Approve.
  3. If the request is already linked to an existing contact (the requester's email matched a contact when the request was submitted), that contact is used and an invitation email is sent. Otherwise, the system tries to match the company name the requester entered to one of your clients (an exact, case-insensitive name match). If it matches, a contact is created under that client and the invitation is sent.
  4. If no contact is linked and no client matches the company name, a Select Client dialog opens. Search for the correct client by name, select it, and click Approve to finish.

When a request is approved, the system sends the requester a portal invitation email. The contact then sets up their login by following the link in that email.

Reject a request

  1. Find the pending request in the list.
  2. Click Reject.

The request is marked Rejected and no invitation is sent.

The Portal Access Link card provides a shareable URL you can send to clients who need to request portal access:

https://<your-app-host>/portal/auth/request-access?spi=<your-org-slug>
  • Click Copy to copy the link to your clipboard.
  • The ?spi= parameter auto-fills your service provider identifier, so clients don't have to enter it manually.
  • Client-specific portal links that also pre-fill the company name are available on each client's Portal tab in the client record.

When a client opens the link, they land on the Request portal access form and fill in Your name, Email address, and Your company name, then click Request access. Submitting the form creates a pending access request that you review here.

White-Label Branding

The portal can be branded with your organization's logo, icon, and primary color. These are not set on the Client Portal admin page — they are configured in Org Settings under the Branding card:

SettingWhere it's used
LogoInvoices, quotes, and the expanded sidebar (PNG, JPG, SVG, or WebP; max 2MB)
IconCollapsed sidebar and browser tab; square image recommended (max 2MB)
Primary ColorButtons, links, and accents

White-label branding in the client portal additionally requires the separate white-label portal license feature. When that feature is enabled, the portal applies your organization's logo, icon, and primary color at runtime. Without it, the portal falls back to default Ascent branding even if you have uploaded a logo and color in Org Settings.

Best Practices

  • Use the shareable link. Sending clients the Request Access Link is the simplest way to onboard self-service users, since the service provider identifier is filled in for them.
  • Confirm the company before approving. When the Select Client dialog appears, double-check you're attaching the requester to the correct client so they see the right data.
  • Reject stale or unrecognized requests. Keep the pending queue clean by rejecting requests you can't verify.
  • Set branding once in Org Settings. Upload your logo and icon and choose a primary color there; they carry through to the portal when white-label branding is enabled on your plan.