Solidlio Mobile

An iOS and Android app that runs the MSP, Organization and Customer portals against the same API as the web product, for technicians working away from a desk and for the people who raise tickets.

The problem

The work is not at the desk. A technician is in a server room with a barcode on a switch and no way to look it up, so they photograph it and deal with it later. The three hours on site get reconstructed on Friday from memory. A change window stalls because the one person who can approve it is driving. A client emails to ask where their ticket is, because the portal is a browser bookmark they have never opened on the phone that is in their hand. Every one of these is a round-trip through someone’s laptop, and every round-trip is where the detail gets lost.

What Solidlio does about it

The app is a client over the same gateway and the same guards as the web portal — there is no second permission model to keep in step and no mobile-only data path. Sign-in is by password, by the organization’s own Entra or Google tenant, by Apple, or by a magic link, with device biometrics unlocking a stored session afterwards. Time runs on a server-side clock, so a timer started on a phone can be stopped in a browser. Writes made without a connection are held on the device and delivered when one returns.


Capabilities

CapabilityWhat it does
Role and workspace switchSwitches concrete memberships and their End User, Org Tech, Org Admin, MSP Tech or MSP Admin view, including lower-privilege views.
Persistent MSP client scopeSwitches between All Clients and any managed client, then consistently narrows dashboard, tickets, field work, assets, projects, changes, calendar, IPAM, monitoring, locations, software licenses and commercial companion lists.
Enterprise SSOSigns in through the organization’s own Entra or Google tenant, brokered server-side.
Biometric unlockReleases the stored session with Face ID or Touch ID instead of a password.
Server-side timerRuns a clock on a ticket that survives closing the app and can be stopped from the web.
My WorkCombines the technician’s assigned tickets, tasks, changes, schedule, timer, logged time and on-site actions by day.
Barcode and QR scanningScans QR, Code 128, Code 39, EAN-13 and EAN-8 to open an asset, or to create one when nothing matches.
Offline writesHolds tickets, comments, assets and time entries on the device and delivers them when a signal returns.
MFASets up and verifies authenticator codes, with one-time recovery-code support.
Ticket attachmentsAdds private documents, library photos or camera photos to a ticket, up to 16 MB each.
Notification centreFilters unread items, marks all read, deletes items and opens their real workflow destination.
Approvals on the phoneApproves or rejects procurement and change approvals from either staff portal.
Report libraryQueues, tracks and opens account reports, with the financial types held back from technicians.
Ticket lifecycleMoves a ticket through eight statuses and posts internal or client-visible comments.
Field expensesCreates and submits expenses with document/photo/camera receipts; administrators can approve, reject and reimburse.
On-site asset actionsUpdates authorized asset status and appends timestamped field notes without destroying existing notes.
Field network lookupSearches subnets, VLANs and IP assignments across the current organization or MSP client scope.
Software/license inventoryShows existing licenses and seat/expiry status across managed clients through an MSP-scoped, read-only API; purchasing and provisioning remain absent.
Calendar executionJoins meetings, opens directions, responds/updates status and opens linked tickets, projects or changes.
Quote decisionsReviews/declines any actionable quote; signature acceptance is server-restricted to one-time physical hardware.
Orders and deliveryTracks organization-scoped shipments, items, carrier events and delivery estimates.
Invoice reviewShows invoices and balances without payment, checkout or payment-method controls.
Tenant brandingApplies the account’s resolved logo, colours and company name to the app chrome.

Built for MSPs and their clients

The same install serves all three audiences. Each membership names a workspace and real role. The user can move among those memberships and, where their role allows it, enter a lower-privilege view of the same workspace. An MSP administrator can therefore work as MSP Admin, Organization or End User without creating a second account; the API still enforces the assigned role.

OrganizationMSP
TicketsOwn staff work their own organization’s ticketsTechnicians work tickets across every client they service
My WorkAssigned tickets, tasks, changes and scheduleThe same day view across every visible managed organization
Client contextNot shown — there is one organizationPersistent All Clients / managed-client switch scopes operational lists
AssetsScan, create, update status and add field notesThe same field actions across clients they service
NetworkSearch subnets, VLANs and IP assignmentsSearch IPAM across managed organizations with client context
ExpensesFile costs and receipts; Org Admin decidesFile/rebill costs; MSP Admin decides and reimburses
ApprovalsOwn procurement and change approvalsApprovals across the clients they service
ReportsOwn account, including revenue for administratorsOwn account; technicians are refused the three financial types
BrandingTheir own brand, if entitledTheir brand carries through to the clients they onboard

The Customer portal is separate again: tickets, quotes, invoices, assets, knowledge articles, notifications and shipment tracking, with no staff or storefront surfaces.


How it works

  1. Sign in — password, the organization’s own identity provider, Apple, or a magic link. The organization’s SSO enforcement is applied on the device the same way it is on the web.
  2. Pick a role and workspace — choose an actual organization membership and its assigned role, or a lower-privilege view. Account, organization, role, portal, tenant headers and cached data switch together and survive token rotation.
  3. Work — My Work, tickets, attachments, timers/manual time, expenses, assets, IPAM lookup, calendar, approvals, projects, view-only invoices, quotes and shipments, each using the same tenant and role guards as the web.
  4. Go offline — a ticket, a comment, an asset or a stopped timer is written to device storage and delivered when a connection or a foreground event arrives. Nothing is discarded until the server accepts it.
  5. Get notified — a notification raised anywhere in the platform is pushed to the registered devices, subject to the person’s channel switches, category allowlist and quiet-hours window in their own timezone.
  6. Tap the notification — it opens the ticket, change, approval, project, calendar event, asset or invoice in whichever portal is currently active.

Security

ConcernHow it is handled
Token refreshThe refresh token is rotated and the old one blacklisted; the replacement preserves the explicitly selected workspace and permitted lower view.
SSO client secretsNever on the device. Solidlio is the OAuth client; the app only opens a browser and receives a one-time code valid for 60 seconds.
SSO browserThe system browser, not an embedded web view — which is also what Google requires.
BiometricsThe operating system reports pass or fail only. No biometric data reaches the app or the server. Signing out disables unlock.
Device push tokensBound to the authenticated caller; a client cannot register or delete another person’s device.
Sign-outClears tokens, the cached profile, the push registration, the biometric flag, the pending offline queue and any running-timer mirror.

Editions

The app is included on every tier. What it can show follows the same entitlements as the web portal.

Capability in the appFreeStarter / EssentialsGrowth / ProfessionalScale / BusinessEnterprise
Tickets, assets, time tracking
Projects● (MSP only)
SLA indicatorsBasicBasic / Adv.Adv.Adv.
Change managementView onlyBasicCABAdv.
Tenant branding in the chromeLogo onlyFull
Enterprise SSO sign-in

Platform

PlatformsiOS and Android, from one shared codebase
TabletsSupported on iPad
AppearanceFollows the device light/dark setting
AuthenticationPassword, Microsoft Entra ID, Google Workspace, Apple Sign In, magic link, biometric unlock
Pushthe Apple and Google push services, with per-category preferences and quiet hours
OfflineWrites only — queued on the device and replayed. No offline reading.
APIThe same gateway and guards as the web portal; the app holds no permission model of its own
CommerceNo storefront, catalog, cart, checkout, payment method, payment SDK, subscription creation or external purchase prompt
CameraQR, Code 128, Code 39, EAN-13 and EAN-8 asset scanning; support and expense-receipt photos

What it does not do

Stated here rather than left for a customer to discover.

  • No offline reading; the offline support covers writes only.
  • Signature capture is quote acceptance only, not technician sign-off on a completed job.
  • No mobile storefront, catalog, general invoice payment, software/license acquisition or subscription provisioning.
  • No AI assistant in the app.
  • Branding, SLA policies, queues and role assignments are configured on the web. Assigned roles and their permitted views can be switched in the app.

The work is not at the desk, and neither is the software.

See this working on a real account.

Book a walkthrough and we will run this capability against your own clients, devices and tickets.

Book a demo All features

A 30-minute walkthrough against your own workflow. No slides.