Company scope switching
Pick one company or a combined view from the company selector.
One login for every location, subsidiary, and division
Give authorized users access to multiple companies in one portal. Switch between companies or view them combined, without a separate login for each location.
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
One portal for clients with one office or many.
Pick one company or a combined view from the company selector.
See tickets, devices, invoices and compliance across every company the user may access.
Grant access through roles and company permission groups. A parent-child relationship alone does not grant access to every child.
Company-scoped views respect the selected companies and the user’s permissions.
Pull reports for a single office or roll up data across every location for board-level visibility.
Track compliance posture per location or across the entire enterprise. See which offices are lagging and which are ahead.
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.
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.
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.
Supported company-scoped views include tickets, devices, compliance and other portal records. Available filters and aggregate views vary by page and integration.
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.
We'll show company switching, combined views and per-location permissions.