BC
Brad CodyAdministrator
Current productAccess and application shell
Reverse spec drafted

Global create menu

Shared entry point for creating permitted records from anywhere in the application.

Observed route/adminFuture Spec 04
Current maturityVisible quick action; contents not verified
Evidence confidencePartially verified
Last reviewedAugust 4, 2026
Visual evidenceDeferred during UI updates

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.

ElementCurrent behaviorVerification
+ Create triggerAppears in the Overview header next to Search, Help and Notifications.Verified live
Action menuNot opened or inventoried.Unverified
Create form or routeNot observed.Unverified

User journeys

Current flows

01

Create a record

  1. Open Create
  2. Choose an available action
  3. Complete the relevant form
  4. Save
  5. Open the new canonical record
Observed result

Only the trigger is verified.

State model

Current and expected states

Closed

The + Create trigger is visible.

Open

Not verified.

Action unavailable

Permission filtering not verified.

Creating

Not verified.

Success or validation failure

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.
Dependencies
Active WorkspacePermission serviceModule enablementShared formsCanonical create commands

Known current limitations · 3 mapped

What is missing, broken or unverified

Future Spec 04 owns closure →
  1. Menu contents have not been captured.
  2. Contextual actions and route availability are unknown.
  3. 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

Documented

Roles and access

Documented

Routes and entry points

Documented

Page and component anatomy

Documented

Fields and displayed data

Documented

Primary actions

Documented

Forms and validation

Documented

States and transitions

Documented

Empty, loading and error states

Documented

Responsive behavior

Partial

Accessibility behavior

Partial

Activity and audit events

Partial

Data sources and persistence

Documented

Notifications and automation

Partial

Known defects and limitations

Documented

Reusable component dependencies

Documented

Future-spec conflicts

Partial

Visual and repository evidence

Deferred

Acceptance of current baseline

Documented