Customer portal

• Tickets — open + closed tickets the portal user has access to. They can comment, mark resolved, attach files. Comments write back to your PSA as customer-portal replies.
• Assets — device list per location, with warranty / OS / last-seen status. Read-only.
• Backups — last-success timestamps per backup job. Read-only.
• Documentation — runbook + password-page shortcuts that the customer is entitled to (Hudu / IT Glue access scoped per portal user).

Each surface can be toggled per workspace under Admin → Portal and per customer under Admin → Portal → Customer settings.

1. From the customer hub, open Portal users in the Customer panel.
2. Click Invite. Enter the user’s name, email, and access scope (which assets / which sites they can see).
3. The invite email lands with a one-time setup link. The user picks a password (or signs in with SSO if your workspace has SSO enabled and the user’s email domain matches a configured provider).
4. On first sign-in, the user lands on their own customer hub — scoped to just their organization.

The portal carries your branding by default: logo, colors, company name. Configure under Admin → Branding. SVG logo with a single-color picker is the recommended path; legacy URL + filter mode is supported as a fallback.

The portal hostname is portal.<your-subdomain>.mspvectis.com by default. Custom hostname (portal.your-msp.com) is available on Enterprise via DNS CNAME — email support to enable.

Portal users are scoped to one customer organization. Within an organization, you can restrict to specific sites (locations) so a regional contact only sees their own region’s tickets / assets.

• Roles: Admin (can invite other portal users), Member (can see + act on tickets), Viewer (read-only).
• Per-customer settings: enable / disable tickets, assets, backups individually. A site that doesn’t want their backup status visible can have it hidden without affecting other customers.
• Audit log: every portal-user action is captured under the same audit log, with the portal-user’s email as the actor. See Audit log.

Default posture is off. Enable per customer, not workspace-wide. The portal is most useful for customers where:

• They’ve asked to see their open tickets without calling.
• They have a designated IT-coordinator contact who triages on their side.
• They’re large enough that an asset list view saves you from rebuilding inventory spreadsheets every quarter.

For customers without those signals, the portal is overhead. Don’t enable it because you can.