The same records, from outside.
Brokers, agents and insureds sign in to the records your underwriters already work in, scoped to the relationship they hold on your book. No second system, and nothing to reconcile afterwards.
One person record, one login. Every broker, agent and insured on your book is already a person. Granting one access turns that record into a sign-in, and the relationships it carries decide what opens.
They already exist.
A broker of record, a producing agent, a named insured. Each is a person on the account long before anyone asks for a password.
Access is one action.
Grant access from the person record. A login is created against their email and linked back, so the contact and the user never drift into two people.
Scope binds at sign-in.
A view can require a record before it will run. Bound to whoever signed in, one shared view returns one broker's book and nobody else's.
Give them a page.
Arrange the tabs, tiles and widgets an outside party lands on, in the same layout builder your own teams already use.
“Our brokers stopped emailing us for status. That gave an underwriter back most of a day every week.”
One graph, four vantage points. The role a person holds decides which records answer, so one platform serves the people inside your walls and the people outside them.
Brokers and agents.
File new business, watch a quote move through referral and bind, and pull the policy and its documents without asking anyone for a copy.
Insureds.
The coverages in force, the certificates on file, and a way to report a loss against the policy that actually responds.
Capital partners.
The carrier behind your paper reads written premium, loss ratio and referral volume on the book it backs, at the grain the binder asks for.
Auditors and examiners.
A read-only seat over exactly the records in scope, reading the same change history your own team is measured on.
The boundary is not a screen. Scope is enforced in the database rather than in the interface, so a portal user who guesses at a record outside their organisation gets an empty result rather than somebody else's account.
Scoped at the tenant
The rule sits under the query, not in front of it. A record from another organisation returns nothing instead of leaking.
One history
What a portal user changes lands in the same record history as your own team's, with who and when attached.
Roles you already run
Broker, agent, insured, auditor and capital partner are first-class roles rather than a permissions bolt-on.
What they send you lands as work. A portal only earns its keep if what arrives through it opens a record, rather than becoming a second inbox somebody has to triage.
New business.
A submission filed in the portal opens on the same board an emailed one does, stamped with the channel it came from so you can see which brokers have moved over.
Documents.
An uploaded loss run or schedule of values is read on arrival, and every value it yields stays linked to the page it came from.
First notice of loss.
An insured reports a loss and it opens a draft claim against the responding policy, waiting on an adjuster to confirm before anything is committed.
One platform, every seat.
The same records, reachable by everyone with a stake in them. Live, connected, and never re-keyed between systems.
Draw the boundary with us.
Bring the status email your brokers keep sending. We will show you the view that makes it unnecessary.
Usually 30 minutes, with an underwriter on the call.