Skip to main content

Workspace

Workspace is a private IMOS environment where one tenant keeps its data, settings and users.

type: platform-surface · status: draft · abstraction: entity

What it is​

A Workspace is one tenant's private area in IMOS. It holds that tenant's Records, Assets, settings and customisations.

A tenant is the customer organisation using IMOS. A Workspace is the secure platform environment provided for that tenant. The terms are separate because they describe different things: tenant describes the customer, while Workspace describes the boundary around its data, configuration and access. In the current model, one tenant operates through one Workspace.

Each Workspace is isolated from every other Workspace. Identities do not belong directly to a Workspace. A person or service can work there only through an Access Scope, which carries the permissions granted by that Workspace.

Why it exists​

Manufacturers must keep their data, access and ways of working separate from other customers. A Workspace provides that boundary while letting every tenant use shared platform definitions where they apply.

Relationships​

Outgoing

  • enables → Module (many-to-many) — Workspaces selectively enable Modules to expand a tenant's available feature set and object graph.

Neighbourhood​

Stakeholder summaries​

  • Product — A Workspace is the boundary for one tenant's data, settings and customisations. Tenant additions stay private to that Workspace.
  • Investor — A Workspace gives each customer an isolated operating environment while preserving shared canonical definitions across the platform.
  • Marketing — A Workspace is your organisation's private area in IMOS, containing its data, settings and customisations.
  • Engineering — A Workspace is the tenant isolation boundary. It owns private Records, Assets and schema extensions, while Identities act through Workspace-specific Access Scopes.