01.software Documentation
Start workspace administration first, then route approved implementation handoffs to the right surface.
01.software Documentation
Use this page to choose the right human path. Tenant administrators and operators should start with ownership, access, feature scope, integrations, and readiness. Technical readers should use the implementation handoff only after the workspace owner has approved scope, credentials, and launch criteria.
Choose Your Path
Workspace Setup
Set owner, team access, billing state, and handoff responsibilities.
Tenant Management
Prepare tenant roles, team boundaries, and operational ownership.
Feature Planning
Choose the smallest feature set that fits your plan and launch goal.
Content Operations
Prepare publishing, forms, media, community, and event workflows.
Commerce Operations
Prepare catalog, customer, order, fulfillment, shipping, and support ownership.
Integrations & Keys
Approve keys, domains, analytics, webhooks, and AI-agent handoffs safely.
Launch Readiness
Confirm what must be ready before an internal or customer launch.
Implementation Handoff
Route approved technical work to SDK, API, MCP, or webhook surfaces without duplicating contract references.
Tenant Admin Path
- Start with Workspace Setup to confirm ownership and access.
- Use Tenant Management to align tenant roles, team boundaries, and operator responsibilities.
- Use Feature Planning to enable only what the first launch needs.
- Prepare Content Operations and Commerce Operations only for enabled areas.
- Review Integrations & Keys before handing credentials, domains, webhooks, or AI-agent access to a technical owner.
- Finish with Launch Readiness before opening the workspace to teams or customers.
Implementation Handoff Path
- Confirm the workspace owner, tenant-admin, and launch owner have approved the feature scope.
- Confirm credential ownership, allowed origins, webhook ownership, and readiness criteria in Integrations & Keys and Launch Readiness.
- Use Implementation Handoff to select the correct surface at a routing level.
- Use machine-readable contracts and package-owned references for exact SDK, API, CLI, or MCP details.
- Return to Launch Readiness before production exposure.
Operating Rhythm
| Cadence | Check | Owner |
|---|---|---|
| Weekly | Review access, content queues, failed webhooks, and readiness blockers | tenant-admin |
| Monthly | Review plan, billing, quotas, keys, analytics origins, and unused features | workspace owner |
| Incident | Pause launch or customer exposure when billing, keys, CORS, commerce, or moderation is blocked | workspace owner |
Next Actions
- New workspace: open Workspace Setup.
- Existing workspace: open Launch Readiness.
- Technical build already approved by the workspace owner: open Implementation Handoff.