Skip to main content

Domain Model Reference

This map explains record ownership and relationships. Menu groups and usage recommendations do not imply database parent/child relationships.

Companies and cycles​

Group (Holding)
  ├─ SaaS: entitlement set → modules, user/company limits, validity
  └─ Companies (Tenant)
       ├─ Organization units (tree)
       ├─ User memberships and company roles
       ├─ KPI register → measurement series, breakdowns, success criteria
       ├─ Planning periods
       │    ├─ Analyses, SWOT and focus areas
       │    └─ OKR cycles
       │         └─ Objectives → Key Results → Initiatives
       └─ Personal dashboards and report views

User account
  ├─ Platform role and account status
  ├─ Group memberships
  └─ Company memberships → unit membership/leadership

On-prem installations use the same entitlement engine with a signed license as its source. Changing a SaaS set in the database does not grant on-prem module access.

Planning period and OKR cycle​

A planning period is the strategic time window for analyses and focus areas. An OKR cycle is an execution window belonging to that planning period; it is not a child of a focus area. One OKR cycle can contain objectives linked to different focus areas.

Objectives and focus areas are connected through link records. A focus-area link does not change the objective's cycle relationship or organizational ownership.

Objective, key result and initiative​

  • Objective: A qualitative goal with its own key results and focus-area links.
  • Key Result: A measurable outcome belonging to an objective, with progress updates.
  • Initiative: Work belonging to a key result. The key-result relationship is required.

All three record types support owners and contributors. An objective owner can be derived from the unit leader; ownership/contribution affects progress-update authority and access to confidential records. Confidentiality also applies related-record and administrator/leader scopes; unit membership alone does not reveal a confidential record. See Roles & Permissions.

Continuous KPI, measurement and report usage​

A KPI is a continuous company record, not a copy under a BSC or cycle report. Its responsible person, owner unit, measurement series and success criteria belong to the KPI.

A report references a KPI through a KPI usage. The usage carries a report-specific weight. Several reports using one KPI share measurements while retaining their own weights. Viewing an old report or having report-edit access does not grant KPI measurement authority.

When a planning period closes, its report snapshots are preserved. A subsequently changed continuous KPI and a closed report snapshot serve different purposes. KPI Tracking is the canonical guide to measurements and closing behavior.

Access boundaries​

One user account can belong to several companies. Membership roles and unit assignments are company-scoped; Group Admins act within their group and Super Admins have platform scope. Tenant isolation and Group Management explain those boundaries.