Settings context checkpoint
Active workspace: default
Confirm workspace identity before billing follow-up, SSO readiness, or dedicated-environment governance updates.
Workspace context was loaded from environment fallback values. Use metadata-backed session context before production rollout.
Live metadata is unavailable. Treat this as preview data until you reconfirm metadata-backed identity and tenant on /session.
Admin follow-up contextSettings
You navigated here via the admin Week 8 readiness summary. Continue the targeted onboarding, billing, verification, or go-live review for this workspace, capture the outcome on that surface, then return to the filtered admin readiness view. This is navigation-only context and does not change identity, impersonate a member, or automate remediation.
Audit export continuity
Reuse the same Latest export receipt from /settings so the filename, filters, and SHA-256 stay chained from settings through verification, go-live, and back into this admin handoff. This manual evidence relay is navigation-only; open the receipt, carry the proof in the workspace surfaces, and then return here to complete the queue or readiness loop.
Current workspace: default · Week 8 focus: Go-live ready
Treat this as the manual admin → workspace surface → admin loop: follow the requested surface, capture evidence or outcome notes there, then use the return link below to restore the admin context and keep the focus state aligned.
Returning keeps the same admin filter state in place so the operator can continue the governance review without rerunning the drill-down manually.
Workspace configuration
Review workspace tenancy, self-serve billing follow-up, subscription status, and retention defaults while keeping the verification/go-live/admin-readiness governance lane connected.
Enterprise evidence lane
Use Settings as the manual governance surface for self-serve billing follow-up, portal-return status, audit export, SSO readiness, and dedicated-environment planning. This page helps you review what the current workspace is entitled to, then carry the same evidence trail into verification, go-live, or admin readiness.
These controls only preserve workspace handoff context and surface billing/status cues. They do not open support workflows, trigger automatic remediation, or impersonate another role.
Admin readiness follow-up
This workspace is aligned with the Week 8 mock go-live readiness focus. Review billing posture, usage evidence, and feature gating before returning to the admin snapshot.
Return to admin readiness viewBilling and readiness closure lane
Use this lane to keep plan/billing, audit-export, and feature-gating follow-up in one governance path: resolve settings changes here, attach verification evidence, rehearse go-live readiness, then return to admin readiness focus.
Use the admin readiness return actions below once the settings evidence is ready to hand back.
Navigation only: these links preserve governance context across settings, verification, go-live, and admin readiness without automation, support tooling, or impersonation.
Plan limit and usage pressure
Usage has not accumulated yet for the current period. Keep this lane ready so the first run, storage growth, and provider expansion can be checked against plan limits when they appear.
Current period
- to -
This lane is still navigation-only: compare usage against plan limits, decide whether billing action is needed, then keep the same workspace evidence path through verification and back to admin.
Workspace
Loading workspace settings...
Display name
default
Tenant
tenant_demo
Workspace slug
default
Data region
global
Plan and access
Monthly price
Custom / free
Active members
0
Plan limits
Feature readiness
Enterprise capabilities are surfaced per workspace plan. Audit export is downloadable when enabled, and the SSO and dedicated-environment sections below expose readiness when the current plan includes those features.
Single Sign-On
Contract source information is unavailable.
Connection mode
workspace
Provider
Not configured
Supported protocols
Readiness checklist
This workspace can preview SSO requirements here, but provider setup stays locked until the plan includes the feature.
- Upgrade to a plan with SSO support.
- Choose OIDC or SAML as the connection protocol.
- Configure identity provider metadata and domain mapping.
Configuration skeleton
Use these inputs to validate request completeness, then submit a controlled live write when the workspace is eligible. Success here records configuration intent; rollout still depends on readiness and delivery status.
Preflight summary
Protocol: OIDC · Domains: 0 · Metadata host: -
Entity ID: -
Submit status: SSO configuration requires workspace owner or admin access before controlled live write is enabled.
Current workspace role: -. Coordinate the final SSO controlled live write with a workspace owner or admin.
- SSO write flow is locked until plan upgrade.
- Metadata URL is required for preflight.
- At least one domain is required for preflight.
Upgrade required
SSO configuration is available as a plan-gated enterprise surface. Upgrade this workspace to unlock provider setup.
SSO evidence lane
After the SSO preflight and controlled write, capture the verification run, status, and notes that prove the identity provider can gate the workspace. Keep those references tied to the same workspace context.
SSO remains plan gated; keep this lane ready with the recorded run notes so the supported upgrade can reference them once it is unlocked.
Use the admin readiness return action below once the SSO evidence is ready to hand back.
Navigation only—this lane keeps the manual verification flow, artifact linkage, and admin-return path together.
Dedicated environment
Contract source information is unavailable.
Deployment model
single tenant
Target region
Not selected
Isolation summary
Dedicated environment provisioning and isolation orchestration remain staged for this workspace.
Readiness checklist
- Upgrade to a plan with dedicated environment support.
- Confirm region and compliance boundaries for the target deployment.
- Review network and access isolation requirements before provisioning.
Provisioning intake skeleton
This intake panel validates the request locally, then lets operators submit a controlled live write when the workspace is eligible. A successful submit records the provisioning request; actual rollout still follows readiness and delivery governance.
Preflight summary
Region: - · Classification: internal
Requester: -
Capacity: - · SLA: -
Submit status: Dedicated environment configuration requires workspace owner or admin access before controlled live write is enabled.
Current workspace role: -. Coordinate the final dedicated-environment controlled live write with a workspace owner or admin.
- Dedicated environment write flow is locked until plan upgrade.
- Target region is required for preflight.
- Requester email is required for preflight.
Upgrade required
Dedicated environment delivery is exposed as a plan-gated readiness surface in this slice. Upgrade to unlock workspace-level provisioning intake.
Dedicated environment evidence lane
Dedicated environment provisioning is staged. Keep the associated delivery notes, compliance summaries, and operator decisions tied to verification and go-live so the readiness path is transparent.
Dedicated environment is still plan gated; once the workspace upgrade unlocks it, keep this lane ready with the recorded readiness notes before returning to admin readiness.
Use the admin readiness return action below once the dedicated-environment evidence is ready to hand back.
Navigation only—keep the manual handoff path, documented notes, and admin return process tied to this lane.
Billing and subscription
Current plan billing
Custom / free
Billing period
- to -
Subscription status
workspace_managed
Billing provider
workspace_managed
Cancel at period end
Disabled
Status summary
Billing summary pending.
Self-serve enabled: no (workspace-managed fallback)
Manage-plan billing intent
You arrived with intent to inspect the plan binding. Confirm the upgrade readiness before returning to verification evidence or usage pressure to keep the Week 8 trace aligned.
This intent-aware guidance is purely navigational; it keeps the plan workstream traceable without triggering automation or impersonation.
Audit export continuity
Audit export is not enabled on this workspace plan. Upgrade to unlock export downloads.
Navigation-only manual relay: these links preserve the workspace context but do not automatically attach the receipt or close rollout steps for you.
Feature is currently plan-gated. UI shows fallback guidance until entitlement changes.
Issue: Audit export is not available on the current plan.
Date filters are applied as UTC day boundaries in this slice.
Governance closure tip: export audit events here, then attach the file in verification, carry it into the go-live drill, and end the loop by returning to the admin readiness view.
Format
From (optional)
To (optional)
Export disabled reason: current plan does not include audit export.
Audit export evidence lane
Audit exports are the recorded events used for compliance verification—keep each download, filter note, and file hash tied to this workspace before you carry the evidence into verification or go-live.
Audit export is still plan gated; once the upgrade unlocks it, return here to note the intended download parameters before continuing the Week 7/8 trail.
Use the admin readiness return action below once the export evidence is ready to hand back.
Navigation only—keep the manual export evidence path aligned with the verification/go-live lane before you slide back into admin readiness.
Usage dashboard
Current billing window: - to -
No usage recorded for this period yet.
Observability and retention
Structured audit events retain the original trace and request identifiers.
Hot retention should follow the active workspace plan and downstream compliance obligations.
Workspace context now drives tenant routing, so operator review should happen against the selected workspace before deploy or replay actions.