Concepts
Keep tenant, workspace, project, task, session, and approval concepts straight as work grows.
Before you begin
Use the app’s current scope marker as your starting point. A tenant provides organization context, a workspace groups shared access and settings, and a project focuses work.
Core model
Example lifecycle
- In workspace
Acme Engineering, projectPublic docs, a member submits taskClarify the installation guide. - Labor0 creates a graph with a documentation step and a verification step.
- The first session prepares a plan and the task becomes Waiting for approval.
- A reviewer selects Approve. A later session edits and verifies the files.
- The task can finish while retaining both sessions and the approval decision as separate records.
Expected result
Changing a workspace changes which projects and settings are visible. Changing a project changes task, graph, session, and binding context without changing workspace-owned members or connections. Starting another execution attempt creates another session; it does not create another task unless the requested outcome itself is new.
Permission guidance
Scope and role together determine what an actor can view or change. Do not infer permission from a URL or from another person’s screen.
If scope feels wrong
Symptom: a project or setting is missing. Likely cause: the wrong workspace or project is selected. Safe recovery: return to the app’s scope selector, confirm the visible name, and retry the action.