| Name | Roles | Status | CORE | Pre-Core | ||
|---|---|---|---|---|---|---|
| Loading… | ||||||
Edit User
| Code | Name | Plain-language access | |
|---|---|---|---|
| Loading roles… | |||
| Code | Name | Plain-language access | Members | |
|---|---|---|---|---|
| Loading… | ||||
Maintenance Mode
When enabled, the public maintenance endpoint returns true and the frontend can display a banner. Changes take effect on next request — no restart needed.
Gmail BCC Address
Blind-copied on every outbound Gmail send (project @mention notifications). Leave blank to send with no BCC.
Settings PIN
PIN required to unlock the Settings panel inside CORE (project workspace → gear icon). Checked server-side — never shipped to the browser. Keep it 4 characters — the unlock screen's input won't accept more.
Uniformat Code → CSI Division Mapping
Powers CSI-division auto-tagging when a SqFt Model is uploaded (project Takeoffs tab). Uploading a revised workbook replaces the entire mapping.
Record a Database Clone
Log that you just refreshed this database from another environment. Updates the “Last DB Clone” status above and appends a db_clone event.
The catalog behind each study's Document Follow-up checklist — one row per objective, with a Best (●) and Acceptable (○) document and, optionally, the project inputs it can verify. Only PPA / Acquisition is seeded today; add rows here to cover New Construction and Improvement.
| Study | Objective | Best (●) | Acceptable (○) | Condition | Sort | Active | Actions |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
The project fields the checklist tracks (Entity Name, Purchase Price, etc.). Labels, formula descriptions, sort order, and visibility are editable here. A newly added input has no built-in CORE data source — its value stays blank unless a developer wires one up — but it can still be tracked and verified against documents like any other input. The key is fixed once created.
| Key | Name | Computed | Formula Description | Auto-Verify | Sort | Active | Actions |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Same catalog as the Documents tab (core_followup_requirements) — one row per requirement — edited
through the simpler v9 model: a single Name and Tip instead of separate Best/Acceptable documents. Saving here
sets both Best and Acceptable to the same Name, so the two tabs stay compatible; project inputs are managed on
the Documents tab.
| Study | Name | Tip | Kind | Sort | Active | Actions |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Same core_followup_input_fields table as the Documents tab — add, rename, reorder, or retire the
project fields the checklist tracks. A newly added input has no built-in CORE data source (its value stays
blank until a developer wires one up), but it can still be tracked and confirmed against documents like any
other input, and immediately appears in the "Confirms these project inputs" list above.
| Key | Name | Computed | Formula Description | Sort | Active | Actions |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Zoho CRM Stage Backfill
Fetches the current Stage from Zoho CRM for every Pre-Core EOB record that has a Deal ID. By default only fills in records with a blank Stage; enable Force to overwrite all. Processing runs in the background — if the Pre-Core history tab is open it will update live via the stage SSE stream.
Zoho Deal Notes Backfill
Fetches all notes from Zoho CRM for every Pre-Core EOB record that has a Deal ID and syncs them into the core_zoho_notes table. Always does a full replace per deal — any deleted Zoho notes will be removed. Processing runs in the background at ~700ms per record to stay within Zoho's rate limit.
Zoho Pipeline Stages
Manage the CRM pipeline stages shown as filter buttons in Pre-Core. Stage Name must exactly match the Zoho CRM value. Display Label is the shorter text shown on the button — leave blank to use the full stage name.
| # | Stage Name | Display Label | Pipeline | Color | Active | Actions |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Recent System Events
Append-only audit log. Most recent 100 events shown; filter by type to drill in.
| When | Event | By | Details |
|---|---|---|---|
| Loading… | |||
QC1 Submission Requirements
Every project must satisfy all of these before it can advance to QC1. Enforced in code today — not yet individually toggleable.
- Site Inspection completed or waived (only checked for study types that have one seeded)
- Every document requirement Received or Waived — none still Pending
- Every project input confirmed or waived