Workspace/Home
Home
A product home for runtime flow, billing posture, review pressure, and the next best action inside this workspace.
Next actions
Keep the home surface tight: connect a runtime, confirm agent presence, and move into review or evidence only when the workspace actually needs it.
Workspace verdict
This workspace is ready to move forward through one governed launch path.
Recommended next move
Primary action
Start launch review for the highest-risk queued workflow.
Why now
Approval pressure, runtime posture, and launch blockers are already visible in one workspace.
Supporting detail
Use runtime governance, trust packets, and activity only after the launch decision is clear.
Workspace home
Usage, spend, runtime flow, and launch posture in one calm workspace home.
The first screen should read like a product home, not an operator wall. See your real runtime line, active commercial posture, review pressure, and the next place to act without losing context.
Plan pending · member · No recent activity
Governed actions
0
Last 7 days governed throughput
Resolved outcomes
0
Last 7 days completed actions
Governed spend
$0.00
Billing setup pending
Credit balance
$0.00
No active launch grants
Runtime line
Live windowed activity derived from governed actions, completions, review events, and billing snapshots inside this workspace.
Last 7 days
Governed actionsResolved outcomesReview events
First 3 minutesOpen this only if the workspace is still missing its first governed loop.
These three setup moves matter only when the workspace still needs its first connected agent, first action, or first review trail.
Step 1
Connect runtime
Start by bringing the first runtime lane and authority boundary into this workspace.
Connect runtime
Step 2
Open Trust Center
Open proof, support policy, DPA, subprocessor disclosure, and the buyer pack from one trust surface.
Open Trust Center
Step 3
Run first governed action
Use credentials or a connected agent to run the first governed action and confirm the review and evidence path.
Open Agents
Next actions
Start from the surfaces that move this workspace forward.
1 actions
Workspace signals
Recent changes and operating signals
1 items
Runtime governance packs
Switch runtime assurance posture by brand
9 brands
Anthropic
Keep Anthropic adoption legible across Claude surfaces instead of flattening everything into one assistant story.
Anthropic already spans desktop, hooks, and connector-style enterprise workflows. OSuite should present the buyer-visible controls, proof, and workspace authority layer above those surfaces.
Compare runtime governance by brand
Signals
4
Control matrix
0
Compliance posture
Show whether desktop, code hooks, and connector lanes land inside the same governed review path.
Evidence flow
Keep replay and proof export readable even when execution starts inside Anthropic-owned clients.
Identity and access
Separate workspace authority from the runtime surface so operators can tell who approved what.
Authority boundary
Anthropic keeps the user-facing client; OSuite keeps approvals, replay, and buyer-legible proof.
Billing status unavailable
Launch posture
Workspace-aware view
Workspace planPlan pending
PCAA volume remaining—
Open billing to complete workspace entitlement setup.
API key management is hidden for your current role.
Billing controls are routed to owner, admin, or billing admin roles.
Review queue
Role-gated
Approval operations are reserved for security, admin, and owner roles. This workspace view stays read-oriented for your current role.