Operate Organization context
Organization owner/admin is effective admin in every Organization Workspace. Workspace admin/editor assignments consume the shared Editor-capacity pool.
FOR TEAMS
Give agents useful context without losing the team boundary.
Select one Workspace from the CLI. Membership, roles, and artifact visibility—not possession of a URL—control what people and agents can retrieve.
Start freeORGANIZATION CONTEXT
Keep the Workspace boundary clear.
Every login starts with an Organization and a default Workspace. Free and Pro keep a clear owner/editor boundary with viewer sharing; Team and Business add the shared Editor-capacity pool. Membership, roles, and visibility control what people and agents can access.
Explore TeamOne Workspace at a timeSearch and Graph do not cross Workspace boundaries
Three Workspace rolesadmin, editor, and viewer
Authorization before retrievalPrivate content stays visible only to its owner
ACCESS MODEL
Choose who can view and retrieve each artifact.
visibilitywho can viewauthentication
publicAnyone on the internetNot required for viewingworkspaceActive members of the owning WorkspaceRequiredprivateThe creator onlyRequired · defaultWORKSPACE SCOPE
Set a default Workspace—or choose one for a single command.
Search and Graph resolve one Workspace. A workspace key selects the boundary; it never grants access by itself.
- Default Organization
- With no Workspace selected, led uses the oldest active Workspace in your default Organization.
- Persistent
led use-workspace <WORKSPACE_KEY>selects a Workspace for later operations.- One command
--workspace <WORKSPACE_KEY>targets a Workspace without changing the saved selection.- Authorization
- Membership, role, visibility, and private ownership are evaluated before retrieval.
Review without editing
Team and Business support unlimited viewers without consuming an Editor slot.