DATIUSDocs
Back to App

Core Concepts

Datius's data model has three layers: organizations, workspaces, and signals. Understanding how they nest makes everything else — API keys, permissions, ingestion — straightforward.

Organizations

An organization is the top-level tenant — typically one per company or team. Every user gets a personal organization automatically, and can belong to any number of additional ones. Organizations hold billing/plan settings and are where org-wide API keys and roles live.

Workspaces

A workspace is an isolated telemetry namespace within an organization — most teams create one per product, environment, or data domain (e.g. "Production" vs. "Staging"). Signals, telemetry data, dashboards, reports, and workspace-scoped API keys all belong to exactly one workspace, and data never crosses workspace boundaries.

Signals

A signal is a typed, named event definition — the thing you actually ingest values against. Each signal has:

  • A key — the machine-readable identifier used in ingestion calls (e.g. order_completed).
  • A data type — counter, gauge, currency, percentage, or duration — which governs how dashboards format and aggregate its values.
  • An optional tag schema — structured metadata fields attached to every event; see Signal Schemas & Tags.

Signals can be deactivated (hidden from new ingestion without deleting history) or, if they've never received data, deleted outright.

Roles & permissions

Access follows a GCP-style resource hierarchy — permissions granted at the organization level cascade down to every workspace inside it.

Organization roles

  • roles/org.admin — full control over the organization, including membership and org-wide settings.
  • roles/org.creator — can create new workspaces within the organization.

Any authenticated member without an explicit role is an implicit roles/org.member — the baseline granted by simply belonging to a workspace in the organization.

Workspace roles

  • roles/workspace.owner — full control, including deleting the workspace and managing its API keys and members.
  • roles/workspace.editor — can create/edit signals, alerts, and view all workspace data.
  • roles/workspace.viewer — read-only access to dashboards, telemetry, and reports.

How it connects

In short: an organization contains workspaces, a workspace contains signals, and events ingested against a signal are what power that workspace's dashboards, live telemetry, and reports. See Authentication for how API keys map onto this hierarchy.