Sharing vessels with an insurer
The operator chooses which vessels an underwriter can see. Everything else stays private.
An underwriter works inside the operator's workspace as a member with access to Connected insurance only. In the demo that is Tom Achebe from North Quay Mutual, who has view on Insurance and none on everything else.
You choose the vessels
Each vessel has a shared with insurer flag. Only someone with publish on Insurance can turn it on. In the demo, 6 of the 18 vessels are shared.
What the underwriter sees
For shared vessels only:
- the vessel itself (name, type, flag, size)
- the risk score and its drivers
- sensor anomalies
- daily emissions and CII ratings
- policies, premium adjustments and claims
What the underwriter never sees
- vessels that are not shared. The database returns no rows for them.
- alerts and work orders. They belong to Predictive maintenance, which the underwriter has no access to.
- crew messages, notes and the audit log.
How it is enforced
A vessel is visible when you have view on Fleet monitor, or you have view on Insurance and the vessel is shared. Every table with per-vessel data applies the same check. This happens in Postgres, so it holds even if a page has a bug. The RLS test suite signs in as the underwriter and checks that exactly the shared vessels come back.
Billing & renewal
The 1-month trial after a 10% deposit, the 3-year contract with a year-1 exit, annual billing, renewal, Cancel trial, Cancel renewal, no refunds for the year already started, and what each order stores.
Health, severity and failure probability
How a sensor reading becomes an alert with odds and a time window.