​

Projects

An organization is the tenant and security boundary in Erdo. A project is a work context inside that organization: use projects to separate customers, developments, campaigns, or other initiatives without creating another organization. Choose a project from the app switcher to focus the workspace, or choose All projects for an explicit organization-wide view. The selection is kept per browser tab and per organization, so two tabs can work in different projects without changing each other’s context.

​

What project context filters

The active project filters project-owned lists before pagination, including:

• conversations and their generated pages or artifacts;
• datasets, jobs, heartbeats and heartbeat proposals;
• job executions, workstreams and experiments;
• agent runs, run analytics, and user-visible actions tied to project conversations;
• event pipelines;
• Activity items tied to project threads, jobs or workstreams; and
• Attention items tied to project workstreams.

New resources created while a project is selected are attached to that project. Pages generated from a conversation inherit that conversation’s projects as well as the active project. Organization-level resources remain shared. These include integrations, agents, organization settings, shared Knowledge, the audit history, and standalone organization alerts or approvals. Selecting a project does not weaken or replace organization RBAC, and a direct resource URL still uses the resource’s normal organization permissions.

​

API, MCP and CLI

List or create projects with GET /v1/projects, POST /v1/projects, erdo_list_projects, erdo_create_project, or erdo project list/create. Pass the selected project on subsequent API requests with X-Project-ID. Omit the header for All projects. See API authentication and request context and MCP request context for the complete header behaviour.