Universe SaaS Restricted admin surface Sign in with a verified operator session to manage the platform.
Public site Sign in
Guest Verified access required
Universe Admin

Secure operator access for the blended Universe platform.

This area is restricted to verified operators. Sign in to manage tenants, content, commerce, email, automation, and service operations from the Universe control surface.

Admin Access
Checking
Waiting for verified access.
AI Assistant
Checking
Assistant status becomes available after sign-in.
Workspace Snapshot
0 / 0 / 0
Tenants, workspaces, and enabled modules.
Control Tower

Operational readiness

WaitingSign in to resolve operational readiness.
IssuesNo readiness issues loaded yet.

This control tower rolls package, domain, email, service, automation, identity, and usage health into one operator view.

Usage And Audit

Recent pressure and operator activity

UsageNo usage data loaded yet.
AuditNo recent audit activity loaded yet.
Resilience

Auth throttles and recovery freshness

WaitingSign in to inspect resilience coverage.
Rate limitsNo recent throttle events loaded yet.
Recovery Drills

Operator runbook evidence

RecoveryNo recovery drills loaded yet.

Record drills here so recovery freshness stops living only in operator memory.

Module Lineage

What the extraction already knows

Plan Packaging

Commercial baseline

Package Offers

Sellable bundles and add-ons

Usage Meters

AI and automation pricing units

Workspace Package

Current entitlement driver

WaitingSign in to inspect the active workspace package.
AccessModule gating state appears after package data loads.

Applying a package syncs the current workspace package subscription and grants plan-backed entitlements on the neutral Universe layer.

Package Builder

Upsert a sellable offer

Package offers can anchor a plan, include extra modules, and attach usage meters for AI or automation-heavy surfaces.

Wizer Routes

Workers AI orchestration map

Verified Access

Session and workspace resolution

SessionNo active verified session.
WorkspaceResolving runtime context.
AccessRole-boundary access appears after runtime resolution.

Request a verification code first. In development, the code is also returned in the response.

Access scopeVerified operators only.
Tenant contextChoose the tenant and workspace before signing in.
Protected surfaceOperational data stays hidden until the session is verified.
Tenant Provisioning

Create a sellable workspace

Master-admin only. This creates tenant, workspace, owner membership, default package entitlements, branding, locale, domain, and email policy in one pass.

Provisioning Result

Default stack attached

WaitingProvision a tenant workspace to see the generated defaults.
Identity Providers

Email-code, OIDC, Cloudflare Access, and enterprise SAML

WaitingLogin to inspect SSO providers.
EventsSSO login audit appears here.
Enterprise SSO

Provider governance for bigger customers

Enterprise SSO provider records can be prepared now. Redirect login activation returns after the Ory bridge is wired.

Branding Control

Platform, tenant, and workspace white-label setup

Platform branding stays on Universe-owned hosts; tenant and workspace branding takes over on white-labeled runtime hosts.

Resolved Branding

Active theme, host behavior, and profile chain

WaitingRuntime branding will appear after the first context refresh.
ProfilesSign in to inspect platform, tenant, and workspace overrides.
Locale Control

Platform, tenant, and workspace language defaults

Locale defaults resolve through the same platform, tenant, and workspace chain used by branding and Wizer.

Resolved Locale

Active language chain and runtime fallback

WaitingResolved locale will appear after the first context refresh.
ProfilesSign in to inspect platform, tenant, and workspace locale overrides.
Wizer Personality

Platform, tenant, and workspace AI behavior

This writes platform, tenant, or workspace prompt guidance into the shared Wizer layer without changing route selection.

Resolved Personality

Live profile chain reaching the worker

WaitingRuntime Wizer personality will appear after the first context refresh.
ProfilesSign in to inspect platform, tenant, and workspace Wizer overrides.
Domain Ownership

Neutral hostname inventory

WaitingSign in to inspect owned domains.
DNS Governance

Protected and editable records

WaitingSign in to inspect DNS records.
WaitingSign in to inspect DNS change logs.
Domain Control

Claim and assign routable domains

Claim the hostname first, then attach it to a tenant root, workspace root, or CMS domain.

Use `cms_primary` to project the claimed hostname into the current workspace CMS routing layer.

DNS Record Control

Manage only safe records

The backend blocks protected root and `www` routing records so platform hostnames stay hidden.

CMS Domains

First extracted Info Global slice

WaitingLogin to inspect CMS domains.
CMS Pages

Published and draft route inventory

WaitingLogin to inspect CMS pages.
Launch Readiness

Customer-facing go-live checklist

WaitingLogin to inspect launch readiness.
ChecklistLaunch readiness checks will appear after the first authenticated load.

This turns the imported CMS, publication, funnel, and domain data into an operator-facing launch checklist.

Launch Blockers

What still blocks public traffic

WaitingBlockers and warnings will appear after the first authenticated load.
Public routesRecent launchable page and funnel routes will appear here.
Preserved Builders

Open the battle-tested runtimes

The current Universe builder path preserves the proven Info Global runtimes instead of rewriting the page and funnel editing experience during the blend.

Builder Rule

Preserve first, adapt second

Page Builder Literal preserved runtime mounted on the neutral Universe CMS contract.
Funnel Builder Literal preserved runtime mounted on the new funnel graph and simulation bridge.
Rule Do not rewrite the builder UX while battle-tested legacy behavior is still the stronger asset.
CMS Domain Control

Create or update routed brands

Use this to manage CMS labels and primary brand routing after the hostname is claimed in Domain Control.

CMS Page Control

Publish the current route shell

This writes the live route payload and normalizes landing-builder sections into the public CMS contract.

Localization inventorySave the base page first, then add translated variants here.

Localized CMS variants keep the same route and publish state while overriding user-facing copy for the selected locale.

CMS Redirects

Legacy and campaign path routing

WaitingLogin to inspect redirects.
Redirect Control

Route old URLs without touching published pages

Use redirects for preserved campaigns, renamed pages, and launch aliases.

Glossary Inventory

Resolved translation terms by locale

WaitingLogin to inspect glossary entries.

Wizer and future translation tooling will honor the active glossary chain once entries are saved.

Glossary Control

Platform, tenant, and workspace terminology rules

Use glossary entries to keep Wizer, translations, and future localized slugs aligned on the same terminology.

Translation Memory

Exact-match translation reuse by locale and context

WaitingLogin to inspect translation memory entries.

Page and funnel localization writes will backfill exact-match translation memory here.

Translation Memory Control

Save reusable source-to-target text mappings

Context types let the same source phrase resolve differently for page copy, funnels, and future editor-side translation tooling.

CMS Assets

Media registry for the neutral builder layer

WaitingLogin to inspect CMS assets.
Asset Control

Register reusable media without tenant lock-in

This is the neutral asset inventory that future builder blocks and tenant themes can reuse.

CMS Publications

Recent publish history across the workspace

WaitingLogin to inspect CMS publication history.
Publishing Ops

Promote drafts and keep route history durable

Publish creates a durable snapshot and keeps the route path locked even if the page later returns to draft.

CMS Funnels

Route sequencing on top of the neutral CMS pages

WaitingLogin to inspect funnel inventory.
Funnel Control

Bind page paths into a sequenced offer journey

Steps can reference page IDs directly or page paths on the selected domain.

Localized Funnels

Locale-aware funnel overlays and step ordering

WaitingSave or load a base funnel, then inspect localized overlays here.
Funnel Localization

Override funnel copy and per-step routing metadata by locale

Use step localization JSON to reorder offers, localize offer keys, or attach locale-specific step metadata without cloning the base funnel.

CMS Quizzes

Funnel-adjacent quiz inventory

WaitingLogin to inspect quizzes.
Quiz Control

Define quiz questions and results

Questions and results are optional but should be updated before publishing a quiz.

Quiz Submissions

Latest quiz responses

WaitingLogin to inspect submissions.
Quiz Notes

What the public API will store

CaptureQuestion answers, score totals, and matched results.
RouteResults can link to CMS pages for funnel routing.
ConsentEmail is optional unless the quiz requires gated results.
Behavior Events

Live engagement telemetry

WaitingLogin to inspect behavior events.
Behavior Notes

Baseline tracking contract

EventTrack key events like lead capture, quiz starts, and checkouts.
ContextSession/visitor IDs stay optional for now.
MetadataFreeform JSON holds page and campaign attributes.
Automation Rules

Behavior-triggered sequences

WaitingLogin to inspect automation rules.
Automation Control

Define triggers and steps

Steps can reference template IDs or use webhook targets.

Email Governance

Managed providers, routing, and professional mail

WaitingLogin to inspect email providers.
Master Delivery Control

Configure managed providers and backup routing

Provider governance is master-admin only. Tenants do not choose or see the backend provider chain.

Professional Domains

Managed professional mail domain inventory

WaitingLogin to inspect professional mail domains.
Professional Domain Control

Attach managed mail to a governed domain

Platform-managed domains will lock Qbox MX/SPF and optional DMARC. Tenant-external mode leaves MX and sender policy under the customer.

Professional Mailboxes

Mailbox inventory for dashboard-native mail

WaitingLogin to inspect managed mailboxes.
Mailbox Control

Store mailbox inventory and optional vendor sync

Mailboxes default to API-enabled with vendor webmail disabled. Immediate vendor creation is optional and does not store the password in Universe.

Native Inbox

Dashboard-native professional inbox

WaitingLogin to inspect professional inbox counts.
WaitingMailbox messages will appear after a managed mailbox is selected.

This inbox stays inside Universe. Vendor webmail remains disabled and hidden.

Message Detail

Selected mailbox thread

WaitingSelect a professional mailbox message to inspect the detail view.
Email Templates

Automation messaging inventory

WaitingLogin to inspect email templates.
Email Template Control

Store reusable email content

Templates stay tenant-owned, and delivery now resolves from workspace branding plus the active provider.

Automation Runs

Latest automation triggers

WaitingLogin to inspect automation runs.

Queue-first automation now runs through a recoverable execution layer before email delivery sweeps.

Email Outbox

Queued or sent email activity

WaitingLogin to inspect email outbox.

Use preview mode to validate branded sends before adding a live provider key.

Email Suppressions

Delivery blocks and recovery safety

WaitingLogin to inspect suppression rules.
Suppression Control

Block sends without deleting automation

Suppressions turn matching outbox rows into skipped audit records instead of deleting queued automation history.

Member Documents

Protected delivery catalog

WaitingLogin to inspect member documents.
Member Document Control

Create delivery records before checkout automation

This slice manages metadata and entitlements first. File upload automation can be added after the neutral pipeline settles.

Entitlements

Grant product and document access manually

Manual grants bridge the gap until checkout and member onboarding start issuing entitlements automatically.

Customer Snapshot

What one member can access right now

WaitingLoad a customer snapshot after login.

This matches the public member-content flow that a verified member session can read from the public worker.

Commerce Products

Neutral checkout catalog

WaitingLogin to inspect commerce products.
Product Control

Create products that issue member access

These products feed the live public checkout sandbox and automatically grant member product access after paid completion.

Commerce Orders

Live purchase records

WaitingOrders will appear after checkout completion.
Commerce Leads

Lead-first funnel inventory

WaitingLeads will appear after the public checkout flow captures them.
Billing Providers

Workspace-owned payment configuration

WaitingLogin to inspect billing providers.
Stripe Governance

Keep checkout behavior and move key ownership into the workspace

Keep the provider inactive until both Stripe keys are ready. Empty fields will clear the stored values.

Billing Rotation Audit

Credential changes without exposing stored secrets

WaitingLogin to inspect billing secret rotations.
Stripe Secret Rotation

Replace keys or re-seal existing secrets

Use this for key replacement or seal-key re-encryption. Blank fields preserve the current stored values.

Commerce Offers

One-click upsell and downsell inventory

WaitingOffers will appear after the one-click slice is configured.
Saved Payment Profiles

Reusable payment methods captured from paid Stripe orders

WaitingPayment profiles will appear after successful Stripe purchases.
Offer Control

Configure the one-click transition rules

This defines the reusable offer contract that the public one-click routes will execute.

One-Click Flow

Off-session Stripe baseline

CaptureA normal Stripe checkout stores the reusable customer and payment method.
OfferA one-click offer links a paid source order to a target product.
ChargeIf the saved method supports it, Universe attempts an off-session payment intent.
FallbackIf Stripe requires action, the checkout stays open for customer confirmation.
Service Providers

Optional Veloxt service-pack operators

WaitingSwitch to the Veloxt workspace and login to inspect service providers.
Service Orders

Customer service timeline inventory

WaitingService orders will appear after the service pack is enabled on the active workspace.
Provider Control

Register dispatchable providers

Provider onboarding now uses the shared Universe flow; this form still supports direct operator edits.

Use the provider ID from the list above to move an application into review, verify it, or reject it.

Scheduled reminder automation now runs every 5 minutes. Use this as a manual override for the current workspace.

Service Order Control

Create service orders manually or from a paid commerce order

If a commerce order is provided, customer and package fields can stay empty and Universe will bootstrap from the paid order.

Schedule + Assignment

Set windows and dispatch a provider

This controls the live shared service window, dispatch, reminders, and technician execution loop.

Evidence Control

Attach before/after evidence to the customer timeline

Evidence now supports governed delivery URLs and audience-specific download policy on the live shared service layer.

Evidence Policy

Control who can see and download service evidence

WaitingPolicy inventory will appear after the service worker deploy succeeds.
WaitingRetention inventory will appear after the lifecycle slice deploy succeeds.

These rules decide whether evidence stays downloadable, metadata-only, or hidden for each audience.

Retention controls can retire evidence access and delete expired R2 objects while keeping the audit record.

Operator Routing

Route service milestones into the operator outbox

WaitingDashboard operator notifications will appear after the service worker deploy succeeds.
WaitingOperator notification routes will appear after the service worker deploy succeeds.
WaitingDispatch history will appear after the first routed service event.

Routed events create dispatch rows and queued transactional outbox records for operator follow-up.