Requests / Intake

Requests / Intake shows a minimized internal queue for inbound needs, inquiries, service asks, custom requests, and internal follow-up. It is read-only today and keeps request handling distinct from orders or payment obligations.

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

Current area: Requests / Intake.

Surface ownership

Requests / Intake

Partially implemented

Current route: /dashboard/requests
Target route: admin.runsonlattice.com/workspaces/{workspace_slug}
View type: Live view
Access today: This area checks your access automatically before showing live information.

Live today

You don't have access to Requests.

Requests

Access required

This queue is limited to approved operators with Requests access.

Owns

What belongs here

Inbound needs, inquiries, service asks, custom requests, and internal follow-up
Internal operational intake records before orders, work orders, invoices, or payment obligations
Future request queue, triage, assignment, and conversion handoff

Exists now

What exists here today

The /dashboard/requests route now shows a minimized internal queue for one active workspace scope.
Saved request records and internal access rules support the read-only proof behind the scenes.
Archived requests stay out of the default queue view.

Next attach

What should Codex build next

Design queue actions, triage, assignment, archive behavior, and audit before request mutations.
Keep triage and review ahead of any fuller request detail surface.
Keep public intake and Portal visibility behind a later public-safe projection design.

Keep out of this slice

What must not be bundled here

No public intake forms, Portal lookup, or customer-facing follow-up in this slice.
No request editing, made-up request counts, or conversion workflow is included.
No automatic order, work order, invoice, payment obligation, notes, attachments, or conversions.

Behind the scenes

What supports this area today

Live data

Requests queue route

The existing Dashboard section route now reads a minimized internal queue for one active workspace scope.

Stored records

Saved request records

Request records already exist, while submitter details and freeform request payloads stay out of the first queue proof.

Access rules

Internal request access rules

The read proof uses internal team access rules, while public and Portal access remain excluded.