Operate
Tenant administration
Administering a Konstrukt tenant — navigation, plan lifecycle and the default plan, the plan admin landing, plan documentation, System settings (features, themes, maintenance, console, Kai, advanced) and the help menu.
A tenant is one customer environment at https://{tenant}.konstrukt.app, holding any number of plans, their apps and users. Administration happens at two levels: tenant level (System, Users, Integration) and plan level (the admin landing of each plan). This page covers both, except security and integration, which have their own pages.
Navigation#
| Element | Swedish label | Purpose |
|---|---|---|
| Plans | Planer | Plan list and the structure tree of each plan |
| Integration | Integration | Import configurations, jobs, transport accounts, API keys — see Data integration |
| Users | Användare | Users, roles and groups — see Security and access |
| System | System | Tenant-wide settings (below) |
The left rail holds these four entries; its panel can be pinned. The top bar holds Notifications, Act as (Agera som, switch to another role), Go to admin (Gå till admin), Settings (Inställningar), Help (Hjälp) and Kai.
Under a plan, the structure tree lists the plan's apps directly, followed by Apps (Appar), Access lists (Behörighetslistor), Data model & logic (Datamodell & logik: Dimensions, Value types, Calculations, Flows — Dimensioner · Värdetyper · Beräkningar · Flows) and Archived plans (Arkiverade planer).
In lists, the chevron at the start of a row expands a summary panel; clicking the name opens the object.
Plans#
A plan is the top-level container of a data model: dimensions, value types, calculations, references and apps. Users only see plans they have access to.
Plan list#
The plan list offers grid and list views, search and sorting. One plan carries the DEFAULT badge.
The default plan (isDefault) is the implicit context for Kex: a script without from plan reads from — and a write statement writes to — the default plan. Scripts that work on another plan state it explicitly, per query with from plan, or for the rest of the script with use plan:
sum(Amount) group by Department from plan 3
Plan overview#
Opening a plan shows Recent apps, All apps and Notes (Senaste appar · Alla appar · Anteckningar). Notes show the plan documentation.
Lifecycle#
| Step | MCP tool | Notes |
|---|---|---|
| Create | create_plan |
Empty, or a copy of an existing active plan (copyFromPlanId) |
| Rename | update_plan |
Only provided fields change |
| Archive | archive_plan |
Sets the plan inactive; it moves to Archived plans (Arkiverade planer) |
| Delete | delete_plan |
Only possible for an archived plan; permanent |
Archiving is the normal way to retire a plan: archived plans remain listed (list_plans returns them with isActive: false) and can be included in SQL views on request.
Delete is permanent
Deleting a plan cannot be undone. Archive first, verify that nothing depends on the plan (cross-plan calculations, SQL consumers, integrations), then delete.
A copy includes the whole plan: model, current plan data, references and everything else in the plan. Only the history tables are left out. Two consequences:
- Point-in-time references are empty in the copy, because they read from history. Data references keep their stored data.
- Copying a plan, then archiving and deleting the original, is a way to clear a plan's history (see Data retention).
Plan versions: v1 and v2#
Plans are either v2 (current) or v1 (legacy). Legacy plans exist only on some tenants and are flagged isLegacy. Dataset expressions in Kex and writing app configuration through MCP are v2 features; v1 apps can be read but not written as JSON. New plans are v2.
Plan admin landing#
The admin landing of a plan groups its configuration in four areas, using the product's own descriptions:
| Group | Swedish label | Items | Description |
|---|---|---|---|
| Data model | Datamodell | Dimensions (Dimensioner), Value types (Värdetyper) | Connect dimensions with value types to create a data model. Dimensions are the categories of the plan (products, employees, markets, periods); value types structure the numbers and values stored in the plan, including imported reference data. |
| Interaction | Interaktion | Apps (Appar), Access lists (Behörighetslistor) | Set up the visual environment for users. Apps are the views through which users see and edit plan data; access lists control which data each group can see. |
| Data logic | Datalogik | Calculations (Beräkningar) | Calculate new values automatically when plan data changes. |
| Other | Övrigt | Plan documentation (Plandokumentation) | Describe how the plan is used, for end users and for administrators. |
See Data model, Apps, Security and access and Calculations.
Plan documentation#
Plan documentation (Plandokumentation) has two separate variants:
| Variant | Audience | Path |
|---|---|---|
| User (Slutanvändare Konstrukt) | End users of the plan's apps | /admin/plans/{planId}/description |
| Admin (Admin) | Administrators maintaining the plan | /admin/plans/{planId}/description/Admin |
For agent-facing documentation of a plan, use tenant MCP documents instead; see AI agents and MCP.
Both variants are edited in a rich-text editor (font, size, bold, lists, alignment, text colour, links, images, uploaded images and clear formatting) and saved with Save (Spara). The user variant is shown on the end user's landing page for the plan; the admin variant only on this page.
System#
System (System) holds tenant-wide settings.
| Section | Swedish label | Purpose |
|---|---|---|
| Features | Funktioner | Feature flags for the tenant |
| Themes | Teman | Accent colours and logo (white-labelling) |
| Maintenance | Underhåll | Maintenance operations |
| Console | Konsol | Kex console |
| Kai | Kai | Usage of the in-product assistant |
| MCP | MCP | Instructions and resource files for AI agents |
| Advanced | Avancerad | Low-level system settings |
Features#
| Feature | Swedish label | Area |
|---|---|---|
| API keys | API-nycklar | Integrations with API keys: create keys and build your own integrations |
| Charts | Diagram | Chart components in apps |
| Dark mode | Mörkt läge | Lets users switch between light and dark theme |
| Kai | Kai | Enables the Kai assistant |
| New initial-value logic | Ny initialvärdeslogik | The improved client-side expansion algorithm for initial values; an old flag that is normally on |
| Themes | Teman | Custom accent colours and logo |
Changes take effect with Save settings (Spara inställningar).
The page is available to tenant administrators, who can switch the flags themselves. In the English interface the initial-value flag is labelled New Initial Values (beta).
See Initial values and performance for how initial values affect the client.
Themes#
Themes (Teman) let a tenant carry the customer's own brand. The editor has:
- a logo for light mode and a logo for dark mode (upload or remove);
- four accent colours (Accentfärg 1–4);
- fonts for normal, bold and italic text (default Roboto);
- a live preview of switches, checkboxes, progress bars, buttons, navigation tabs, headings, text and form fields.
Reset to Konstrukt theme (Återställ till Konstrukt-Tema) restores the original logo, fonts and accent colours. The feature is enabled with the Teman feature flag.
Maintenance#
Maintenance (Underhåll) has:
| Setting | Swedish label | Purpose |
|---|---|---|
| Clear cache | Rensa cache | Clears the tenant's server cache |
| Server status | Serverstatus | Online, or offline for maintenance |
| Users with access in offline mode | Användare som har access i offline läge | Users who can still sign in while the tenant is offline |
When the tenant is offline, ordinary users cannot sign in. Only the users listed under Users with access in offline mode can.
Console#
The Kex console (Konsol) runs Kex scripts directly against a plan: a plan selector, an editor with line numbers, live parse errors, and Apply (Verkställ) to execute.
The console can write
A script with a write statement changes data when applied. Validate and test read-only first; outside calculations, a plain write upserts into the target value type. See Kex.
Kai#
System → Kai shows Kai usage per month: the credit limit, credits used and remaining, and usage per user. See AI agents and MCP.
Beta
Kai is a beta feature under development. The credit limit is a technical usage limit.
MCP#
System → MCP holds the documents that AI agents connected over MCP can read. Server instructions (Serverinstruktioner) are read by all agents at konstrukt://TenantInstructions.md, which Konstrukt's own MCP instructions point them to. Use them to describe the tenant: what the plans are for, naming conventions, and anything agents should always keep in mind. Further resource files can be added here, and can also be written by agents with administrator rights. See Tenant knowledge base.
Advanced#
Advanced (Avancerad) is a list of low-level system settings as key–value pairs: for example date formats, cache timeouts, the default plan, the tenant's current data-migration version and whether calculations run when dimension values or properties change.
Change only with support
As the interface warns, changing system settings can cause unexpected behaviour or make the tenant unavailable. Contact Konstrukt support before changing anything here.
Help menu#
The Help menu (Hjälp) in the top bar is also the in-product entry point to documentation and support.
| Item | Swedish label | Purpose |
|---|---|---|
| Release notes | Release Notes | Changes per version |
| User guide | Användarguide | End-user documentation |
| Administrator guide | Administratörsguide | Administrator documentation |
| Admin tasks | Adminuppgifter | Task-oriented administrator help |
| FAQ | FAQ | Frequently asked questions |
| Kex | Kex | Reference documentation for the Kex expression language (Kex reference, served by each tenant at the same path) |
| Keyboard shortcuts | Kortkommandon | Shortcut overview |
| Take a screenshot for support | Ta en skärmbild för supporten | Captures the current view for a support case |
| Copy debug information | Kopiera Debug-information | Copies debug information to include in a support case |
When reporting an issue, include the debug information and a screenshot, plus the URL: app URLs carry the plan, app, workspace and data-type selection, so a link reproduces the view.
New versions are rolled out in release tracks. Administrators are notified in the interface after a release, and the release notes are in the Help menu. See Releases.
For agents
There are no MCP tools for feature flags, themes, maintenance, advanced settings, API keys or plan documentation. Plan lifecycle is available through list_plans, create_plan, update_plan, archive_plan and delete_plan; always check isDefault before writing scripts, because write targets resolve in the default plan. Never call delete_plan without explicit user confirmation.