Published with the canonical App and online-companion relationship reviewed on 8 August 2026.
Why this matters
Some insurance tasks are easier on a larger screen: finding a document among several attachments, reading a dated timeline or checking which question still needs a response. The public Insia experience treats the online client portal as the browser companion to the Insia App, not as a third public product. That avoids a common confusion in insurance technology: a different screen size does not change who owns the record, what the source document says or which human must make a consequential decision. The useful question is not “mobile or web?” but “which view makes the factual context clearer for this moment?”
Key points to carry into the work
- Use the browser companion when a wider view helps you inspect a policy register or document set.
- Treat mobile and web as different ways to access the same policyholder experience, not separate insurance products.
- Keep source documents, dates and open questions visible across both views.
- Do not assume that a portal view creates broker authority, account access for another person or a policy action.
- 01Name the insurance moment
- 02Choose a view
- 03Inspect current sources
- 04Prepare selected context
- 05Keep decisions human
Choose the right view for the work
Where Insia fits
The Insia App is ready to deploy across the App and its online companion for one policyholder experience. The compatibility route for the client portal leads into the App story because it is not a separate product, store listing or broker workspace.
Keep the boundary clear. The online companion does not become an insurer portal, a self-service quote service, a broker decision tool or a substitute for policy wording. Insia does not provide personal insurance advice or make insurance decisions through a browser view.
Checklist
- Is the browser view helping you inspect a real document or policy question more clearly?
- Can you see the current document date and source?
- Are App and online records treated as one policyholder experience?
- Is selected broker sharing tied to a clear purpose?
- Have you kept a human decision separate from a screen or task status?
Sources and scope
Sources support the external context in this guide. Current product capability and availability are explained on the linked Insia product page.
Common questions
Is the online client portal a separate Insia product?
No. It is the browser companion to the Insia App for the same policyholder experience. The public story does not treat it as a third product.
Can I use the portal to get insurance advice?
No. The portal can help organise documents, context and questions. It does not provide personal insurance advice or make a recommendation.
Does a larger screen show different policy authority?
No. A different view can make information easier to inspect, but it does not change the policyholder, the source documents or the permission boundary.
Can a broker see my entire portal record?
No. Sharing should remain selected and tied to an approved relationship and purpose rather than being treated as unrestricted access.
Can I create an account by joining App updates?
No. Joining App updates records consent for release information. Account creation happens separately after a verified release.
Put the context to work
Keep this insurance record in one place.
Explore how the Insia App keeps policies, documents, renewal context and permissioned broker requests together in one iPhone experience.
Join the App waitlist