MSPortal

One portal for every location your client manages

One login for every location, subsidiary, and division

MSP team view

Give authorized users access to multiple companies in one portal. Switch between companies or view them combined, without a separate login for each location.

Used by MSPs including

What changes for your clients

  • The problem

    Enterprise clients with multiple locations have to maintain separate logins or call every time they need data for a different office

    In MSPortal

    A single portal login with instant switching between the child companies each user may access, plus an aggregated view across them

    The outcome: The IT director logs in once and switches between locations without separate credentials

  • The problem

    When a client asks 'how many open tickets do we have across all our offices?' there is no single place to answer that

    In MSPortal

    An 'All Companies' view that combines tickets, devices, invoices and compliance across child companies

    The outcome: Enterprise clients see totals across every office without asking you to compile them

  • The problem

    Giving a client access to one location's data means either over-sharing other locations' data or creating rigid per-location accounts

    In MSPortal

    Grant parent-level users every location and location users only their own. Company permission groups control who sees what

    The outcome: Each person sees exactly what they should. The CFO sees all eight offices, the Denver office manager sees only Denver

What's included

One portal for clients with one office or many.

Activity from every location, labeled by company
MSP team view

Company scope switching

Pick one company or a combined view from the company selector.

Aggregated cross-company views

See tickets, devices, invoices and compliance across every company the user may access.

Link child companies to a parent in settings
MSP team view

Explicit company permissions

Grant access through roles and company permission groups. A parent-child relationship alone does not grant access to every child.

Consistent access controls

Company-scoped views respect the selected companies and the user’s permissions.

Per-location and org-wide reporting

Pull reports for a single office or roll up data across every location for board-level visibility.

Compliance across the organization

Track compliance posture per location or across the entire enterprise. See which offices are lagging and which are ahead.

At a glance

  • Single login for clients with multiple locations or subsidiaries
  • Switch between companies or view them combined
  • Review data for one company or several at once
  • Control cross-company access with explicit permission groups

Frequently asked questions

Still have questions?

Contact our team
How does parent-child company management work for the client?

Configure the company hierarchy and grant the intended users access through company permission groups. Users can then select accessible companies in supported views. Review each group’s company scope rather than assuming the hierarchy grants access automatically.

Is there a limit to how many child companies a parent can have?

You can organize clients with multiple child companies. Confirm the required hierarchy and portfolio size during a walkthrough rather than relying on an unlimited-capacity claim.

Can a user at a child company see other child companies' data?

Access follows configured roles and company permission groups. Grant only the companies a user should access; being associated with a parent or child company is not the complete access policy.

Which portal features support the parent-child company view?

Supported company-scoped views include tickets, devices, compliance and other portal records. Available filters and aggregate views vary by page and integration.

How does this affect how we set up clients in our PSA?

Link each MSPortal company to the intended PSA company and configure portal company access separately. A parent-child relationship does not replace integration mappings or grant users access to every child company.

See one login across every location

We'll show company switching, combined views and per-location permissions.