Screen Reference

Screens are listed in the order a user encounters them during a typical workflow.


Sign-In

Overview

Single-page authentication screen. Supports email + password login and SSO. Redirects back to the originally requested URL after sign-in.

Route & Access

Route/sign-in
Auth requiredNo — public
Redirect param?return=<original-path>

Auth Adapters

AdapterNotes
LocalEmail + password stored in the database
LDAPActive Directory / OpenLDAP
SAML 2.0Okta, Azure AD, etc.
OIDCGoogle Workspace, Auth0, etc.

Adapter is configured per tenant via org.auth_provider_configs.

Next: Dashboard →


Dashboard

Overview

Home screen after sign-in. Shows a snapshot of in-flight work across the tenant and a recent activity feed.

Route & Access

Route/dashboard
Auth requiredYes

KPI Cards

CardDescription
Active SubmissionsOpen submissions across the tenant
Open QuotesQuotes in draft or quoted status
Policies In-ForceActive policies (in_force status)
Pending EndorsementsPolicy transactions in pending_approval

Recent Activity Feed

Shows the last 10 submissions with: Customer name, Transaction Type, State, Status badge.

Next: Underwriting Queue →


Underwriting Queue

Overview

Full, paginated list of all submissions across the tenant. Used by underwriters to triage and action work items.

Route & Access

Route/dashboard/queue
Auth requiredYes

Columns

ColumnDescription
Submission #Unique submission identifier
CustomerLinked party name
Transaction Typenew_business or new_renewal
StateRisk state
SourceSubmission channel
StatusCurrent workflow status badge
Assigned ToUnderwriter the submission is assigned to
CreatedSubmission creation date

Filters

Filter bar above the table: Status (Open / Quoted / Bound).

Next: All Customers →


All Customers

Overview

Master list of all party records (persons and organizations) across the tenant.

Route & Access

Route/customers
Auth requiredYes

Table Columns

ColumnDescription
Party #System-assigned identifier
NameFull name (persons) or legal name (orgs)
Kindperson or organization
StateDomicile state
CreatedRecord creation date

Click any row to open the Customer Detail screen.

Next: New Customer →


New Customer

Overview

3-step wizard for creating a new party record. Hashes sensitive identifiers before persisting.

Route & Access

Route/customers/new
Auth requiredYes

Wizard Steps

Step 1 — Party

FieldNotes
Party KindPerson or Organization
First / Last NamePersons only
Legal NameOrganizations only
Date of BirthPersons only
Entity TypeOrganizations only (LLC, Corp, etc.)

Step 2 — Contact

FieldNotes
Address TypePill toggle: Mailing / Home / Business / Billing. Maps to party_contact_points.usage_type. Default: mailing
Street AddressLine 1 + Line 2
City, State, ZIP

Step 3 — Identifiers

FieldStorage
SSNHMAC hash + masked display (***-**-1234)
EINHMAC hash + masked display
Driver's LicenseHMAC hash + masked display

Raw values are never persisted.

Next: Customer Detail →


Customer Detail

Overview

Full record view for a single party, including contact points and their submission history.

Route & Access

Route/customers/[id]
Auth requiredYes

Sections

Party Header

Party number, name, kind badge.

Contact Points

Table of addresses, phone numbers, and emails on file with type labels.

Submissions

All submissions linked to this customer, with status badges and creation dates.

Next: New Submission →


New Submission

Overview

Transaction type selector and submission intake form. Determines whether this is a new business or renewal transaction.

Route & Access

Route/submissions/new
Auth requiredYes

Transaction Type Cards

Cardtransaction_typeExtra field
New Businessnew_business—
New Renewalnew_renewalPrior Policy # (optional)

Additional Fields

FieldNotes
CustomerSearch/select from existing parties
Line of BusinessProduct line dropdown
StateRisk state
Source ChannelDirect / Agent / Broker

Next: Submission Detail →


Submission Detail

Overview

Full summary view for a single submission. Used by underwriters to review intake data, manage quotes, and track status.

Route & Access

Route/submissions/[id]
Auth requiredYes

Header

FieldDescription
Submission #Unique submission identifier
StatusWorkflow status badge
Transaction Typenew_business or new_renewal
StateRisk state
Source ChannelSubmission origin
Assigned UnderwriterWho owns this submission

Body Sections

Linked Customer

Party name and party number linking back to the Customer Detail screen.

Quotes

List of quotes attached to this submission with status and premium (shown when quotes exist).

Next: AI Copilot →


AI Copilot (KALP)

Overview

Context-aware AI assistant accessible from every screen in the portal. Powered by the @policyone/ai-core package with pluggable LLM providers.

Trigger & Access

TriggerFloating chat bubble — bottom-right corner of every shell page
Auth requiredYes

Features

FeatureDescription
Persistent historyMessage history is kept for the duration of the browser session
Context injectionActive tenant, open submission, linked customer, and open policy are automatically included in every message
Markdown renderingResponses render with headings, tables, and code block highlighting
Agentic workflowsKALP can describe and chain multi-step underwriting actions on your behalf

Context Window

The injected context follows this priority order:

  1. Current tenant + user
  2. Open submission (if viewing a submission screen)
  3. Linked customer party
  4. Open policy (if one is in-force for this customer)