Record Files
Upload, list, filter, sort, export, column selection and open actions for record files.
/admin/leads/:id?tab=filesFuture Spec 14 →Current-state summary
The Files tab keeps briefs, plans, images, spreadsheets, archives and correspondence on the record. The live opportunity shows an upload empty state. Earlier evidence shows a populated reusable grid with select all, filtering, sorting, export, column selection and metadata including document, source, upload date, size, uploader and actions.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Upload actions | Primary and empty-state Upload files actions are available. | Verified live |
| Scope copy | Explains supported document purposes and types. | Verified live |
| Empty state | No files uploaded with a direct upload action. | Verified live |
| Populated grid | Earlier evidence shows selection, filter, sort, export and configurable columns. | Verified from earlier product evidence |
| File metadata | Shows name/type, source, date, size, uploader and Open action. | Verified from earlier product evidence |
User journeys
Current flows
Upload
- Open Files
- Select Upload files
- Choose supported files
- Validate and scan
- Store file
- Create metadata and Activity event
Review files
- Open populated Files
- Filter or sort
- Choose columns
- Open a document or export metadata
State model
Current and expected states
Dedicated empty state and upload actions.
Progress, cancellation and retry were not observed.
Enterprise grid with file metadata and actions.
Not observed.
Product rules
Non-negotiable boundaries
- File bytes and metadata are Workspace-scoped.
- Opening or downloading enforces access at request time.
- Source and uploader provenance are retained.
- Replacing a file must not silently destroy the prior version.
- Exports include only authorized metadata.
- Uploads require type, size and malware controls.
Known current limitations · 4 mapped
What is missing, broken or unverified
Future Spec 14 owns closure →- Upload progress, retry and failure behavior are unverified.
- Versioning, folders, tags, preview and approval status are not visible.
- Retention and deletion rules are not documented in the current UI.
- External cloud-file links and Project inheritance are unverified.
Future alignment
Required evolution
- 01Create one file service reused by records, Projects, tasks, messages, POs and provider operations.
- 02Add versioning, classification, previews and source linkage.
- 03Support client/provider visibility without copying the file.
- 04Preserve audit evidence for replacement, archive and access.
Current baseline
Acceptance record
- Upload entry points and explicit empty state exist.
- Populated state uses the shared grid.
- Core provenance metadata is visible.
- Access and export remain Workspace- and permission-scoped.
Reverse-spec completeness
Documentation coverage
The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.
Purpose and user outcome
DocumentedRoles and access
DocumentedRoutes and entry points
DocumentedPage and component anatomy
DocumentedFields and displayed data
DocumentedPrimary actions
DocumentedForms and validation
DocumentedStates and transitions
DocumentedEmpty, loading and error states
DocumentedResponsive behavior
PartialAccessibility behavior
PartialActivity and audit events
PartialData sources and persistence
DocumentedNotifications and automation
PartialKnown defects and limitations
DocumentedReusable component dependencies
DocumentedFuture-spec conflicts
PartialVisual and repository evidence
DeferredAcceptance of current baseline
Documented