One set of records. Four ways in.
A provider, its client, the client's staff and the technician in the van all work from the same tickets, assets, projects and invoices. Each gets the view that fits their job and nothing that does not belong to them.
Each audience gets its own view of the same records
Where a person lands is decided by their role and their organization. It is a boundary, not a theme.
Provider portal
Technicians, dispatchers and the people who run the practice
Every client you look after in one view, filterable to one. Your own catalogue, margins, commissions and billing alongside.
Client portal
The client's own IT team or office manager
Their tickets, devices, projects, contracts and invoices, with notes their own staff write kept away from end users.
End-user portal
The people a client employs
Raise a request, follow it, see their own devices, read the answer, approve a quote, pay an invoice. Nothing internal is visible here.
Mobile app
Technicians on the road
Assigned tickets, the day's schedule, time capture and push notifications, on iOS and Android.
Four layers of conversation on a single ticket
Every comment is marked for an audience. Three groups share the ticket and each reads only its own layer, so the history stays intact when a job changes hands.
| Layer | Who can read it | What it is for |
|---|---|---|
| Public | The end user, their IT team and the provider | The reply the customer reads |
| Client internal | The client's IT team and the provider | Discussion the end user should not see |
| Provider internal | The provider only | Notes the client never sees |
| Escalation | The provider and whoever they escalated to | A specialist thread, kept off the customer's view |
Six decisions the rest of the product follows from
One record for the whole job
A ticket knows the device it is about, the contract it is covered by, the time spent on it and the invoice that time reached. Nothing is re-keyed between modules, because there are no modules to re-key between.
Approvals that hold
When a change is submitted, the sign-offs it needs are fixed at that moment. Editing the approval rule afterwards cannot quietly change who had to agree.
Money that adds up
An invoice's balance is always recalculated from the payments, refunds and credits behind it. A refund issued from the dashboard and a cheque typed in by hand produce the same figure.
One price everywhere
Markup profiles, contract prices, volume rules, bundles and margin floors are applied once. The product page, the cart and the checkout all show the same number.
AI that stays on a budget
Each AI action has a credit price and is charged before it runs, so a plan's allowance is a ceiling that holds rather than an estimate. Turn it off and everything else keeps working.
Your brand, all the way down
Logo, colours and legal identity flow from the platform to the provider to each client, across the portal, every email and the sign-in page on your own domain.
A record of who did what, that nobody can tidy up later
Every administrative action is written to an audit trail with the person, their role at the time, what they changed, when and from where. There is no way to edit or delete an entry through the product. When a provider and a client work together, the events are recorded on both sides, so neither depends on the other's records to show when access began and ended.
Anyone with a login can request a copy of their personal data or ask for it to be erased from their own portal page, on every plan. Each request carries a 30-day deadline and a report of exactly what was affected.
Solidlio produces audit and privacy records intended to support SOC 2, ISO 27001, PIPEDA and GDPR programmes. Tridacom IT Solutions Inc. does not currently hold a SOC 2 or ISO 27001 certification for Solidlio. Whether these mechanisms satisfy a given obligation is a question for your own advisers.
What you need to know, in plain terms
- Where it runs
- Microsoft Azure, Canada Central region. Backups are copied to a second Canadian region and kept for 35 days.
- Encryption
- TLS on every connection. Credentials and integration secrets encrypted at rest with AES-256; one-time codes and links stored only as one-way hashes.
- Signing in
- Single sign-on with Microsoft Entra ID or Google Workspace, directory provisioning from Entra ID or Okta, and authenticator-app two-factor for password accounts.
- Access control
- Six role levels and per-organization membership decide what every request may touch. A provider reaches only the clients that granted it access.
- Money and tax
- Amounts are stored exactly, never as approximations. GST, PST, HST and QST are calculated from the client's own province, for all thirteen provinces and territories. CAD, USD and EUR are supported.
Everything on this page is documented, in public, before you talk to anyone.
Every capability has its own page and a user guide. When you are ready, book a walkthrough against your own workflow.