At a glance
Ontologie provides two levels of organization: the workspace (tenant) fully isolates data between organizations, and the space (canvas) segments the ontology into logical zones within the same workspace.
Workspace
A workspace represents an isolated working environment. Each organization has one or more workspaces, and the data in one workspace is never accessible from another.
Members and roles
Each workspace hosts members with an assigned role:
| Role | Permissions |
|---|---|
| Owner | Full access: configuration, billing, workspace deletion |
| Administrator | Manage members, settings, and governance |
| Editor | Create and modify entities, relations, documents |
| Viewer | Read-only access, no modifications allowed |
Data isolation
- Entities, relations, documents, and events are strictly scoped to the workspace.
- API keys and Live Data connectors are specific to each workspace.
- Agents and workflows can only access data within their own workspace.
Space (Canvas)
A space is a canvas within a workspace. It lets you segment your ontology into logical zones for better organization.
What are spaces for?
- Separation by business domain: one space for Sales, one for Logistics, one for HR.
- Separation by project: one space per team or initiative.
- Experimentation: a space may organize a prototype; use a separate test workspace to avoid interaction with production usage.
Behavior
- Each space has its own entities and relations.
- Entities can be linked across spaces within the same workspace.
- A workspace has at least one default space.
Workspace → space hierarchy
View the diagram description
%%{init: {'theme': 'base'}}%%
flowchart TD
Org["Organization"] --> WS1["Workspace A"]
Org --> WS2["Workspace B"]
WS1 --> E1["Supply Chain Space"]
WS1 --> E2["HR Space"]
WS1 --> E3["Finance Space"]
WS2 --> E4["Project X Space"]
WS2 --> E5["Project Y Space"]
classDef light fill:#dce6f1,stroke:#234a7a,stroke-width:2px,color:#1f2a37
classDef dark fill:#e8a848,stroke:#c48a2a,stroke-width:2px,color:#1f2a37
classDef accent fill:#5ab5a0,stroke:#3d8b76,stroke-width:2px,color:#1f2a37
class Org light
class WS1,WS2 dark
class E1,E2,E3,E4,E5 accent
Concrete example: a company with two subsidiaries uses one workspace per subsidiary. Subsidiary A has three spaces (Supply Chain, HR, Finance), each with its own entity model. Data from Subsidiary B is never accessible from Subsidiary A.
Summary
| Workspace | Space | |
|---|---|---|
| Level | Tenant (organization) | Canvas (subset) |
| Isolation | Complete: no access between workspaces | Logical: entities can be linked across spaces |
| Members | Shared across all spaces in the workspace | Accessible to all workspace members |
| Data | Fully partitioned | Segmented but interconnectable |
| Use case | Separate organizations or environments | Organize by domain, project, or team |
Related views / modules
Need help?
Contact us: Support and contact.
Test permissions rather than inferring them from a canvas
A space is logical organization, not a tenant boundary. Use distinct workspaces with explicitly authorized access when organizations require isolation. “Production” and “Draft” are names, not independent environments.
Test using actual identities: a reader, an editor and an API key for integrations. Test an allowed read and a disallowed write. Agent context settings and descriptive classifications must not be treated as effective permissions without verification.
Modules also depend on workspace activation. If a documented section is absent, check permissions and enabled modules before looking for an alternative route.
