# Core concepts

> Definitions of the platform's core objects — tenant, plan, dimension, dimension value, property, value type, reference, history, calculation, Kex, dataset, app, workspace, component, action and access list — and how they relate.

This page defines the objects the rest of the documentation builds on. Each definition links to the page that covers the object in detail.

```flow
Tenant -> Plan | model container -> Dimensions | + properties -> Value types | measures over dimensions
Plan -> Calculations | Kex scripts -> Value types | written data
Plan -> Apps -> Datasets | value types + dimensions -> Workspaces -> Components | tables, charts, metrics, actions
```

## Tenant

A tenant is one customer environment. It has its own host name (`https://{tenant}.konstrukt.app`), users, plans, integrations and settings, and its data is isolated from other tenants. Each tenant serves its own REST API, SQL views and MCP server.

## Plan

A plan is the top-level container for a complete data model: dimensions, value types, calculations and apps. A plan is **active** or **archived**; only archived plans can be deleted. A plan can be created as a copy of another active plan.

One plan in each tenant is the **default plan**. Scripts run outside a plan context — from the console, the REST API or the MCP server — are resolved in the default plan, and this includes the target of `write` statements. A calculation runs in the context of the plan it belongs to. Data from other plans is read with `from plan <id>`; this changes where data is read from, not where it is written. `use plan <id>` switches the context for the rest of a script, including write targets.

Solutions usually consist of several plans with distinct roles — for example one for shared master data, one for planning and one for reporting — that read from each other. See [Architecture](architecture.html#plans-as-building-blocks).

!!! note "Plan versions"
    Plans are either **v2** (current) or **v1** (legacy). v1 plans exist only on some older tenants. This documentation describes v2.

## Dimension

A dimension is a categorical axis, such as `Account`, `Department`, `Employee` or `Month`. Its members are **dimension values**, each with a **code** and a **name**. A dimension belongs to a plan and can be used by any number of value types in that plan. Time is modelled as ordinary dimensions, such as `Month` with codes like `202601`.

## Property

A property (*egenskap*) is an extra column on each value of a dimension: `Department.Region`, `Employee.StartDate`, `Account.Type`. A dimension can have any number of properties. A property can be **bound to another dimension**, so that its values are values of that dimension. This creates hierarchies and mappings, such as `Account → AccountGroup`. Properties can hold several values, separated by `;`. See [Data model](data-model.html#properties).

## Value type

A value type (*värdetyp*) is a measure: one value column — number, date or text — stored over zero or more dimensions. `Amount` over `Account × Department × Month` is a three-dimensional cube; `Price` over `Product` is one-dimensional; a value type with no dimensions holds a single value. Think of it as a fact table with exactly one value column. See [Data model](data-model.html#value-types).

Each stored row records who or what wrote it: a user, an import or a calculation. This is its line state (see [Line states](data-model.html#line-states)).

## Reference

A reference (*referens*) is a named version of plan data kept for comparison, such as "Budget 2026 approved" or "Forecast March". It is either:

- a **data reference**, which stores its own copy of the data; or
- a **point-in-time reference**, which stores only a timestamp and reads the plan's history as of that moment.

See [References and history](references-history.html).

## History

Every change to value-type data is kept. Any earlier state of the data can be queried with `from history <datetime>`. History underlies point-in-time references, auditing and traceability. See [References and history](references-history.html#history).

## Calculation

A calculation (*beräkning*) is a saved Kex script that reads dimensions and value types and writes to one or more value types. Calculations run automatically when the data they read changes. The platform orders them by a dependency graph derived from what each one reads and writes. Calculations can be authored in a guided editor or as free script. See [Calculations](calculations.html).

## Kex

Kex is Konstrukt's query and scripting language, for reading, filtering, joining, aggregating and writing data. It is used in calculations, actions, the Kex console, the REST API and the MCP server. App datasets use a lighter expression dialect, Kex Lite. See [Kex](kex.html).

## App

An app is an access-controlled end-user interface that belongs to one plan. It consists of:

- **Datasets**: selections of value types and dimensions with expressions, initial values, locked values and row-level access. See [Datasets](datasets.html).
- **Workspaces**: pages with filters, data-type selection and a layout of components. See [Workspaces and components](components.html).
- **Components**: tables (grids), text, metrics, charts and actions placed in a workspace.
- **Actions**: forms that collect input and run a Kex script, for example "add employee" or "close month". See [Actions](actions.html).

## Access control

- Users belong to **groups** and hold **roles**.
- **Access lists** restrict which dimension values a user may see or edit.
- Apps and datasets can be restricted to specific users and groups.
- A value type can be marked sensitive, which hides its values from users who lack access to it.

See [Security and access](security.html).

## How the objects relate

| Object | Belongs to | Identified by |
|---|---|---|
| Plan | Tenant | Integer ID |
| Dimension | Plan | String ID, e.g. `Account` |
| Property | Dimension | Integer ID, plus code and name |
| Value type | Plan | String ID, e.g. `Amount` |
| Reference | Plan | Integer ID and name |
| Calculation | Plan | Integer ID |
| App | Plan | GUID |
| Dataset, workspace, component | App | ID within the app configuration |

## Related

- [Platform overview](overview.html)
- [Data model](data-model.html)
- [Calculations](calculations.html)
- [Glossary](glossary.html)
