Login Systems built LS Portal to run its own managed-services business. It reads the PSA, RMM, security, licensing, Microsoft 365 tenants, documentation and satisfaction tools into one place, then gives every seat its own view: dashboards for staff, a portal customers can act in, a wall for the office, and an AI analyst that never invents a number. It has run the Sydney service desk since May 2026, and it is ready for other MSPs in the group.
Screens from the Login Systems portal as it runs today, September 2026. Client and staff names are replaced with invented ones and free text is blurred; everything else is exactly as the team sees it. Click a screen to enlarge.
MSPs run on excellent vendor tools that do not talk to each other. The cost is not the licences. It is the questions nobody can answer without an afternoon of exports.
Three tools, three device counts, no owner of the truth. The portal resolves every vendor site to one client record and shows the drift as named gaps.
"Which clients have devices without an EDR agent?" is two exports and a spreadsheet. The portal answers it on one page, from synced data, every day.
In the portal a customer opens their risk register, accepts a residual risk in two steps or approves a costed proposal, and the account manager sees it change live.
Every panel below is the real product running on sample data. Click into them.
Every vendor tool has its own version of your customer. The portal brings them together into one client record, so a device, a security agent, a licence seat and a ticket all land on the same page, and the disagreements between tools become a list you can act on.
A technician, an account manager, a project lead and the CEO each land on the view built for their job. Access is capability-based and enforced on the server, so what is on the screen is exactly what that role should see, and changing it takes minutes, not a vendor ticket.
Two office boards rotate through ticket flow, endpoint health and supplier status. An alarm engine with nine sources evaluates every minute. When a SOC escalation lands, the wall takes over, pages the roster and stays red until someone acknowledges it.
Twenty-one pages, seventeen per-user feature flags, and a risk register where the customer accepts a residual risk in two steps or approves a costed proposal. The record carries their name, the time and the rating as it stood. The account manager's view updates live.
The monthly service report computes its eight headline KPIs in code and hands them to the model as ground truth it must use verbatim. Validators reject any figure that is not in the KPI block. The narrative is drafted, approved by a human and published to the client portal as a branded PDF.
Recurring revenue, block-hour burn and the effective hourly rate of every fixed-fee agreement, with external technicians excluded from the denominator. One agreement under the floor shows up in September, not at year end.
EDR alerts and SOC escalations, identities without MFA, exposed ports attributed to an office, a cloud host or someone's home, Shadow IT found in the software inventory, phishing results and domain locks. Each signal attributed, linked to the device or identity, and shown to the right people.
Before a technician opens a new ticket, your automation platform can ask the portal how long similar work took and what fixed it. Staff can ask the same questions from their AI assistant with a personal key that an administrator sets up, narrows and can switch off. Every question is recorded.
The browser never talks to a vendor and never holds a credential. Every request passes independent checks before business code runs, and every action, vendor call and model call is audited.
A feature a customer has not enabled stays visible but locked, so the next conversation is an upsell, never a mystery.
A portal user's client scope is derived server-side from their bindings; every by-id endpoint re-verifies ownership.
Non-root immutable images pinned by digest, login throttling on the true peer address, security headers across the board.
An adversarial security audit, its findings fixed in code with tests, and RBAC tripwires that fail the build.
LS Portal has run the Login Systems service desk, management meetings, finance reviews and customer portal since May 2026. This is what is different now.
Each operating company runs its own copy with its own data, so nothing is shared between businesses unless you decide it should be. Improvements made for one flow to all. The tools you already use decide how much lights up on day one; adding a new vendor is a contained piece of work, not a rebuild.
Read-only keys for each vendor, entered once on an admin screen with a connection test. The portal never writes back to them.
Customers are matched across tools automatically; a mapping screen catches the few that need a human.
Technician, account manager, executive and finance groups come ready-made; adjust in minutes.
Portal access per contact, feature by feature, with a switch to turn a client off instantly. Publish the first monthly report.
Pick your tools above and copy the link: it opens pre-selected for your operating company. Login Systems supports the rollout and runs the first walkthrough with your team.
The portal is improved every week. In flight means it is built and being verified before release; next means it is designed and queued.
A walkthrough takes forty minutes: the product live, the client portal from your customer's seat, and what would light up for your stack. Then a scoped plan for your operating company. Login Systems, Sydney.