Global create menu
Shared entry point for creating permitted records from anywhere in the application.
/adminFuture Spec 04 →Current-state summary
The Overview top utility bar exposes a + Create control. The trigger is visible, but its menu, permission filtering, keyboard behavior, created record types and post-create destinations have not been observed.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| + Create trigger | Appears in the Overview header next to Search, Help and Notifications. | Verified live |
| Action menu | Not opened or inventoried. | Unverified |
| Create form or route | Not observed. | Unverified |
User journeys
Current flows
Create a record
- Open Create
- Choose an available action
- Complete the relevant form
- Save
- Open the new canonical record
State model
Current and expected states
The + Create trigger is visible.
Not verified.
Permission filtering not verified.
Not verified.
Depends on target form; not verified.
Product rules
Non-negotiable boundaries
- Only actions supported by the active Workspace and effective permissions may appear.
- Creation must write a canonical record through its owning module.
- Switching Workspace must change the action list.
- The menu must not bypass required fields, approval or conversion rules.
Known current limitations · 3 mapped
What is missing, broken or unverified
Future Spec 04 owns closure →- Menu contents have not been captured.
- Contextual actions and route availability are unknown.
- Mobile and keyboard behavior are unknown.
Future alignment
Required evolution
- 01Support contextual actions such as Project Opportunity, Project, Task, appointment, file, teammate invitation, Offer or Proposal.
- 02Use the same command and form components as destination modules.
Current baseline
Acceptance record
- The trigger is present.
- No unsupported create capability is claimed as current behavior.
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