Configuration

EstimateIQ is configured entirely in-app (with matching API endpoints — see the API reference). Nothing here requires a redeploy. This page covers the data model; the Settings screens page describes the UI.

App registrations (Entra / Microsoft Graph)

To ingest carrier email and integrate with Microsoft 365, EstimateIQ stores Entra ID app registrations used to call Microsoft Graph.

Secrets at rest

Client secrets are encrypted at rest with AES-256-GCM (key derived from REVSRC_SECRET_KEY). The UI only ever displays the last 4 characters of a secret — the plaintext is never returned once stored. Use POST /api/app-registrations/:id/validate to confirm a registration’s credentials still work. Certificate-based auth (thumbprint) and multi-tenant registrations are both supported.

Mailboxes, domains, subject rules & filters

Carrier correspondence is routed into estimates via:

• Email accounts (/api/email-accounts) — the mailboxes EstimateIQ watches (address, folder, direction, sync toggle, linked app registration).
• Domains (/api/domains) — sender domains associated with carriers.
• Subject rules (/api/subject-rules) — ordered patterns (contains / prefix / exact / regex) that classify incoming mail and pull out the estimate number so it attaches to the right estimate.
• Filters (/api/filters) — additional saved / ingestion filters (?scope=).

These feed the inbox triage and the mail-ingest queue.

Estimators

Estimators (/api/estimators) are the GRS users who own estimates. Assignment drives the follow-up queue and the SLA clock (which runs while the ball is with us). See Estimators.

SLA timers & phase multipliers

• SLA policies (/api/sla-policies) define the base response window (ball with us) and the carrier audit window, plus the warnPct / escalatePct thresholds that color the aging states. A global policy applies everywhere; per-carrier rows override it.
• Phase multipliers (/api/phases) scale the budget per phase of the loop (mitigation, demolition, reconstruction, contents), so early rounds and late-stage supplements can carry different urgency. A 1.5× multiplier gives 50% more room.

Together these determine when a follow-up is due and when an estimate shows overdue. See Ball-in-court model.

Per-carrier rules engine

Carriers behave differently, so EstimateIQ ships a rules engine with per-carrier when / then rules that fire when an auditor revision lands — matching on the AI-parsed reason codes (any / all), round, RCV delta, loss type, and phase, and producing priority overrides, SLA overrides, assignments, escalations, tags, and follow-ups. The Carriers guide documents the full shape and the dry-run tester (POST /api/carriers/:carrierId/rules/preview).

Settings keys

GET /api/settings / PUT /api/settings/:key hold app-wide values, including:

Key	Purpose
aiConfig	Gateway model + system prompts (edited from AI settings).
outboundWebhookUrl	Where status changes fan out (see Webhooks).
statusMap	Per-deployment overrides for the external→internal status map.