LATTICE

Authorized Workspace Access

Workspace operations scope

Tenant admin surface

Dashboard Surface Map

Account-scoped operations cockpit. This is the current protected workspace surface and the safest place to attach managed operations workflows.

Current route is /dashboard today. Target hosted tenant admin entry remains admin.runsonlattice.com/workspaces/{workspace_slug} later. Dashboard is tenant-scoped admin work; it is not Unity and not the public storefront.

You are here

Account areas

Use Dashboard for tenant admin work. Live areas come first, while planning areas stay visible without pretending they are active workflows.

Platform orientation

How to read this surface

Dashboard is the account-scoped business operating cockpit. It owns managed operations inside workspace scope: requests, people, assets, services, content, orders, payments handoff, access, and audit. It should not absorb Unity platform administration, global admin, customer auth, checkout, shipping, or deployment concerns.

Live views

Areas with verified reads should feel primary here.

Planning views

Future areas stay visible, but they should read like next steps rather than active workflows.

Owns

What this surface owns

  • Business snapshot for a single workspace scope
  • Links to orders, products, people, inventory, analytics, and future account modules
  • Current route doctrine versus future hosted account routing

Exists now

What works today

  • Protected dashboard shell is live at /dashboard.
  • Orders, products, analytics, customers, and inventory bootstraps resolve under current workspace auth.
  • The shared module catalog in lib/lattice/modules.ts now defines current and planned account modules.

Next build

What Codex should build next

  • Requests / Intake should be the next docs/schema-design module before cart or checkout work.
  • People / Customers, Assets / Spaces, Work Orders / Fulfillment, Media / Documents, Invoices / Payments, and Email / Notifications should stay cataloged as planned until requirements are approved.

Operating areas

Module map

Start with live areas, then use planning entries to see what is next. Future areas remain visible without implying runtime that has not been approved or wired yet.

Live view

Orders

Partially implemented

Access to Orders is unavailable right now.

Current protected read proof exists; order workflows deferred.

Open area

Live view

Products

Partially implemented

Access to Products is unavailable right now.

Current protected read proof exists; CRUD deferred.

Open area

Live view

People / Customers

Partially implemented

Access to People / Customers is unavailable right now.

Current protected read proof exists with minimized customer details; exports deferred.

Open area

Live view

Inventory / Assets

Partially implemented

Access to Inventory / Assets is unavailable right now.

Current protected read proof exists; assets/spaces, adjustments, and fulfillment deferred.

Open area

Planning view

Work Orders / Fulfillment

Deferred

Work Orders / Fulfillment should eventually own operational execution after requests, orders, invoices, or services become actionable. It is intentionally deferred until requests, inventory/assets, shipping doctrine, and order workflows are ready.

Explicitly deferred until requests, inventory/assets, and shipping doctrine are ready.

Open area

Live view

Analytics

Partially implemented

Access to Analytics is unavailable right now.

Protected route exists; reporting data model still needs approval.

Open area

Planning view

Content / Media

Planned

Content / Media will own account-editable copy, documents, media, and merchandising structure for the public shop once a dedicated content and media model is approved.

Public shop content, documents, and media should attach here later, not in the dashboard overview slice.

Open area

Planning view

Brand Settings

Partially implemented

Brand Settings owns account-facing identity and presentation doctrine under workspace scope. Tier 1 safe branding projection already exists for the public storefront contract, while tenant-admin review and publish controls remain deferred.

Tier 1 safe branding exists; tenant-admin review and publish controls are still ahead.

Open area

Planning view

Team Access

Planned

Team access should own account-level operator membership and delegated permissions when an account-safe access review surface is approved.

Account-safe membership review is planned here; current access doctrine lives in schema and Unity.

Open area

Planning view

Account Audit

Planned

Account Audit will summarize workspace-level high-risk changes once an audit event store exists. Today the doctrine is clear, but the event runtime is not built.

Audit doctrine is clear; event storage is not built yet.

Open area

Planning view

Settings

Planned

Settings should become the account operating control area for workspace-safe configuration after business modules are in place.

Account operating settings belong here later, after module boundaries settle.

Open area

Live view

Requests / Intake

Partially implemented

You don't have access to Requests.

A live request view exists today; triage and review should land before any fuller request detail surface.

Open area

Planning view

Invoices / Payments

Requires separate approval

Invoices / Payments is a future adapter-neutral financial event module. It requires separate approval before any runtime, payment adapter, or payment flow is added.

Future module; adapter-neutral event doctrine only, no payment runtime.

Open area

Planning view

Email / Notifications

Planned

Email / Notifications is the future account communication module for templates, delivery events, and customer-safe message history.

Future module; no mail adapter, template editor, or sending runtime yet.

Open area

Keep out of this slice

What must not be bundled here

  • Do not add payments, refunds, shipping, or customer exports into this orientation slice.
  • Do not treat future hosted account routing as already active runtime.