Workspace seats
HealthyNew seat requests still fit inside the current workspace allowance.
Continue standard access review while onboarding stays inside the current seat runway.
ControlLayer
Workspace settings hub
The calmer shared workspace language now carries through the tenant settings hub so route readiness, rollout posture, and plan guardrails stay denser, more neutral, and easier to scan before any deeper write flow begins.
Route readiness
One calm hub for tenant-safe settings orientation
Operators can understand which settings lanes are live, which ones are still scaffolded, and when a plan limit changes the next safe move without widening this route into backend configuration work.
Settings data is read through the /v1/settings tenant-configuration API boundary. Module persistence, custom-field writes, and retention review metadata now live in their deeper settings lanes; provider-backed changes remain blocked.
Primary lane
Custom-field readiness
Best entry point for data-model readiness checks before a rollout decision.
Live routes
4
Ready lanes now share the API-backed tenant configuration and safe scope boundaries.
Scaffold watch
1
Tenant-side shells stay visible so membership follow-up does not disappear while deeper work lives elsewhere.
Billing handoffs
1
Guardrail warnings can still route straight into billing without taking over enforcement here.
Guardrail snapshot
The next safe escalation stays explicit
Shared billing posture now reads like part of the same workspace instead of a separate alert lane.
Workspace seats
New seat requests still fit inside the current workspace allowance.
Continue standard access review while onboarding stays inside the current seat runway.
What this hub owns
Navigation, readiness signals, and preview-safe summaries for the tenant settings surface.
What stays elsewhere
Module-toggle persistence, custom-field schema storage, and user-management write paths remain in their existing specialized lanes.
Admin crossover
Admins can still jump to the dedicated admin settings preview when the question is platform-wide rollout posture rather than one workspace's route map.
Ready lanes
2
custom fields and roles already have read-first previews for reviewer handoff
Guardrail watch
1
External share links is blocked before a harder stop appears
Blocked previews
1
blocked states stay visible without pretending the write path already lives here
Preview-only lanes
1
advisory limits still route into the right billing-backed follow-up surface
Settings lanes
Route-ready surfaces and scaffolded follow-ups
Each card now keeps route readiness, ownership, next-handoff framing, and the most useful highlights together so operators can choose the right settings lane without bouncing across partial shells.
Schema rollout
Custom-field readiness
Review field coverage, validation posture, and rollout blockers without widening into backend schema persistence work.
Best entry point for data-model readiness checks before a rollout decision.
typed preview coveragevalidation riskslaunch blockers
Open laneReview route
Privacy governance
Retention and AI privacy
Review data retention, export/delete request posture, AI prompt/output retention, and safe-stub deletion worker payloads without live destructive actions.
Use this lane when the question is what can be exported, retained, anonymised, or safely previewed before deletion.
retention postureAI privacyno live deletion
Open laneReview route
Access review
Workspace roles and approvals
Inspect role scope, approval boundaries, and least-privilege gaps through the current preview-safe role matrix.
Use this lane when the question is who should be allowed to do what.
role matrixapproval gatesover-permission watch
Open laneReview route
Feature rollout
Module controls
Review module availability, dependency warnings, plan-lock indicators, and affected route behavior from the tenant-scoped settings source.
Module persistence and service enforcement stay in the API; this lane now adds the tenant-facing rollout workspace.
rollout posturetenant visibilityhandoff to deeper lane
Open laneReview route
Membership workflow
Workspace users
The user-facing workspace route is still a shell, but this lane keeps membership review and invitation follow-up visible without colliding with admin-directory ownership.
Use the admin user directory work for deep workflow changes; use this lane for tenant-side orientation only.
membership reviewworkspace access cuesfuture invite handoff
Open laneReview route
Plan guardrails
Limit previews with the same calm shell rhythm
Warning, blocked, preview-only, and healthy limit states now sit in one tighter board so the next escalation is obvious without looking like a separate billing product.
AI review volume
WarningAI-assisted review volume is within two runs of the monthly plan cap.
Stage non-urgent AI review batches until finance decides whether to widen the allowance.
Document storage
HealthyCurrent document storage remains comfortably below the plan threshold.
Keep normal intake and retention policies in place.
Export previews
Preview onlyExport overage remains advisory until provider-backed posting is wired behind the adapter boundary.
Keep export-heavy planning in preview mode and do not treat charges as committed.
External share links
BlockedNew external links are paused because the tenant is eight links above the current monthly allowance. Existing data remains available while new creation is paused.
Let existing links remain accessible, but require plan review before generating another external link.
Hub boundaries
Keep the surface honest
This route stays directional. It helps an operator choose the next settings review without implying that any provider-backed change has already happened.
01
Read-first by design
This page should help someone orient themselves quickly. It should not imply that a provider-backed change has already happened or can happen here.
02
Non-overlapping handoff
The hub points into existing routes and current ownership lanes instead of taking over module-toggle, schema, or invitation logic from other agents.
03
Mobile behavior
Each settings lane collapses into a stacked card with direct links and short highlights so the route still scans cleanly on smaller screens.
Admin crossover
Escalate to the wider control picture when needed
The tenant hub stays close to workspace orientation. Platform-wide rollout and governance questions still belong to the admin preview.
Open admin settings preview
Review module rollout, reminder defaults, and custom-field readiness from the admin-facing surface when the question is larger than one tenant route map.