Workspaces and projects
Separate shared workspace resources from project definitions and executions
A workspace is the membership and authorization boundary. A project organizes a body of work inside that workspace. Choose both before creating resources, querying data or interpreting a missing-resource error.
What belongs where
| Scope | Resources |
|---|---|
| Workspace | Members, API keys and limits; plugin installations; data endpoints; shared standalone skills and applicable write policies |
| Project | Pipeline definitions and runs; ontology definitions, compiled packages, bindings and queries; forecasters and predictions; project assertion workflows |
Endpoints belong to the workspace. Projects reference the same endpoint rather than owning separate copies. A project provides execution or ontology context when an operation needs it. Assertions carry workspace scope and may also carry project scope; project workflows use records in the selected project.
Shared resource does not mean universal access
Installing a plugin makes its capabilities available in the workspace. It does not grant every member or API caller access to every target. Workspace membership, project access, operation permissions, endpoint policy and external credentials still determine what a caller can do.
A workspace MCP connection requires projectId for project actions. A project-scoped connection already binds the project. Discover the schema from the endpoint you are actually using rather than copying scope fields indiscriminately.
Example: two maintenance projects
A workspace installs one Postgres read capability and creates an equipment endpoint. Reliability and Maintenance planning projects can reference that endpoint while keeping their own ontology, queries and pipeline versions. Changing the shared endpoint can affect both projects; creating a new project does not duplicate the underlying database.
When P-101 appears in one project but not another, check the selected project, bindings and permissions before installing the connection again.
Start here
You need a Semogram account with access to the intended workspace. Follow workspace setup to select or create the appropriate workspace and project. For endpoint ownership and reuse, read Data Endpoints.
For administrative controls and the complete access model, see Workspace management.