Skip to main content
Audience: MSP staff writing and attaching client reference material. Clients read these pages in their onboarding portal; they do not manage the library. Client Pages are reusable, read-only documentation pages you write once and reference from your onboarding templates and portals. Instead of re-typing the same welcome message, support instructions, or security FAQ into every client’s onboarding, build a tenant-level library of pages and attach the relevant ones to a template. Each new portal launched from that template includes the pages automatically, and clients read them as expandable articles inside their portal.
Client Pages share the same content as the Documentation Hub. A page you create here also appears in your Documentation Hub library, and editing it in either place updates the same page. See Documentation Hub sync below.

​
Why Use Client Pages

  • Write standard content once — support contact instructions, onboarding expectations, post-go-live next steps, security FAQs
  • Keep every portal consistent — the same vetted content appears across all clients
  • Reference, don’t re-type — templates point at library pages rather than copying text into each task
  • Give clients a reference area — pages appear as guides in the client portal, separate from action items

​
Managing the Page Library

The page library lives in Settings > Onboarding > Pages.
1

Open the Pages tab

Go to Settings > Onboarding and click the Pages tab.
2

Add a page

Click Add Page in the top right to open the page editor.
3

Fill in the page

Complete the fields:
  • Title (required) — the page name, e.g. “How to contact support”
  • Icon — choose Guide, Support, Security, FAQ, or Info
  • Section label (optional) — groups the page in the portal sidebar, e.g. “Support”
  • Summary (optional) — a short description shown in the portal sidebar and page header
  • Page content — the client-facing body, written in a rich text editor (formatting, images, alignment)
4

Save

Click Add Page. The page is now in your library and ready to attach to templates.

​
The Pages Table

The Pages tab lists every page with these columns: Each row has an actions menu with Edit page and Delete page.
Deleting a shared library page removes its onboarding references and archives it in the shared documentation library. This affects linked templates and portals. A confirmation dialog names the page; review Usage first. Removing one template link is a narrower action than deleting the library page.

​
Attaching Pages to a Template

Pages reach a portal by being attached to a template first. In the template builder, open the Client Pages section.
1

Open Client Pages in the template builder

Edit a template and expand the Client Pages section. Use Manage pages to jump to the page library if you need to create a page first.
2

Link a page

Use the Select custom page combobox to search your library and add a page. Pages already linked are not shown again; when everything is linked you’ll see “All custom pages are linked”.
3

Set client visibility

Linking, unlinking, and visibility controls save separately from the template header. Each linked page has a Visible to client portal toggle. Turn it off to keep a page attached but hidden from clients (it shows a Hidden badge). Use the Preview (eye) icon to review the rendered page.
Templates reference library pages — they don’t copy the text. Update the page once in the library and every template that links it stays current. Removing a page from a template only removes the link; the library page and any existing portals are untouched.

​
Reviewing Pages on a Portal

Each company’s onboarding workspace has a Pages tab (alongside Overview, Tasks, Documents, Activity, and Settings). Portal creation copies the page assignment, visibility, and fallback content while retaining the library link when available. Hidden assignments can also be copied. The Pages tab is a review view:
  • The left pane lists the portal’s Assigned pages with counts of Visible and Hidden pages and a search box
  • The right pane previews the selected page’s content
  • Shared page means the portal can display current library content; editing that library page can change what an existing portal shows
  • Portal snapshot means the portal uses its saved content rather than a current library link
  • Use the View as dropdown to open the client portal as a specific contact and read the pages in place, in an MSP preview of that contact’s visibility context
Template page assignments are copied when the portal is created. Changing a template link does not rebuild existing portal assignments. Editing a linked library page can update the content shown by Shared pages; an independent Portal snapshot retains its saved content. Check the source badge before editing a page used by clients.

​
What the Client Sees

In the client portal, visible pages appear in a Pages section titled “Guides and reference information for this onboarding”. Each page is an expandable article showing:
  • The icon and section label
  • The page title and summary
  • The full page content when expanded
Pages are read-only reference material — there’s no acknowledgement, sign-off, or completion required. Clients expand and read them at their own pace. Hidden pages never appear in the client portal.

​
Documentation Hub Sync

Client Pages and Documentation Hub “inline” documents are the same record, not two synced copies:
  • A page you create in Settings > Onboarding > Pages automatically appears in your Documentation Hub library
  • An inline page you create in the Documentation Hub appears in your onboarding page library
  • Editing a page in either place updates the one shared page everywhere it’s referenced
The shared record makes reuse convenient, but editing internal reference text can also affect client-facing uses. Review the page Usage and its content before saving changes.

​
Save and review changes

Add Page opens an editor; entering text does not save it. Submit Add Page for a new page or Save Changes for an existing one and wait for success. Cancel closes the unsaved edit. Linking a page to a template, changing its visibility, and removing that link save through their own controls. After changing shared content, review a linked portal’s Pages tab and View as presentation. Reading a reference page does not complete a task or record an acknowledgement. Create a separate task or approval if you need a client response.

​
Permissions

Creating or editing pages requires an active subscription. No external integration is required for Client Pages.

Onboarding Templates

Attach pages to templates alongside phases and tasks

Client Portal

How pages appear to your clients

​
Frequently asked questions

It can change portals showing that Shared page. A Portal snapshot keeps its saved content. Check Usage and the source badge before editing.
No. It removes that template link. The library page and existing portal assignments remain. Delete page is the broader shared-library action.
Check its client visibility and the portal display settings, then use the relevant contact or role preview. An assigned hidden page can still appear in the MSP review list.
No. Pages are read-only references. Use a task, approval, or signature workflow when a client must acknowledge or respond.
Page link and visibility controls save separately. The page editor also has its own Add Page or Save Changes action.
They use the same shared library page. Review every intended audience before saving content used in multiple places.