Tenant, workspace, and project scope
Labor0 keeps enterprise, tenant, workspace, and project attribution explicit so work, usage, and permissions stay tied to the right organization context.
Public documentation
Labor0 public documentation for onboarding, product concepts, MCP setup, pricing, credits, and handoff into the authenticated Labor0 app.
Guides
Start with an authenticated workspace, repository access, and visible controls before expanding Labor0 automation.
Labor0 keeps organization scope, project work, agent execution, QA, and review paths explicit.
Labor0 MCP setup uses workspace-scoped endpoints and Labor0 tokens managed from the authenticated app.
Labor0 uses credits to make AI/provider and hosted runtime usage visible before billable work expands.
Onboarding
Workspace setup happens in the authenticated Labor0 app so membership, billing, and repository access stay protected.
Add repository access and knowledge sources before asking Labor0 to plan or execute engineering work.
Use plan review, QA evidence, budget visibility, and human approval paths before expanding automation.
Concepts
Labor0 keeps enterprise, tenant, workspace, and project attribution explicit so work, usage, and permissions stay tied to the right organization context.
Memberships grant access at enterprise, tenant, or workspace scope, while tenant-owned user groups provide reusable audiences without granting product access.
Requests become task graphs with dependencies, graph update previews, repository bindings, agent sessions, plan approval, and pull request follow-up state visible.
Labor0 routes QA findings, review comments, and operator prompts back into follow-up work instead of leaving them as side notes.
MCP