Klarun Documentation
Documentation
Everything you need to set up, configure, and use Klarun — your data team's operating system.
This documentation covers all six modules (Reporting, Governance, Platform, People, Intelligence, and Projects), Organization Settings, and the Roles system. Use the sidebar to jump to any section.
Get Started
What is Klarun
Klarun is a Data Ecosystem OS — a single platform that gives data leaders and their teams full operational visibility over every layer of their data organization: the reports they produce, the assets they govern, the people they manage, the platform they run, and the investments they make.
It is designed for CTOs, heads of data, and BI managers who need to operate at scale without the overhead of custom tooling. Rather than spreading context across Notion pages, spreadsheets, and disconnected BI portals, Klarun centralizes it — and connects to the tools your team already uses (Power BI, Databricks) to pull live data automatically.
Klarun follows a hybrid input model: some data is imported automatically through integrations, while other data is registered manually by your team. Both types live in the same interface and can be enriched, tagged, and acted upon in the same way.
Module Summary
Klarun is organized into six modules. Each module covers a distinct area of your data operation.
ReportingReport Catalog · Maturity Benchmark
Centralizes all reports, dashboards, and BI assets across your organization.GovernanceDashboard · Data Assets · Quality · Contracts
Tracks data assets, quality issues, vendor contracts, and governance health.PlatformArchitecture · Platform Health
Documents your data platform architecture and tracks infrastructure incidents.PeopleData Team · Team Management · Onboarding · AI Manager
Registry of your data organization, workforce analytics, and onboarding library.IntelligenceFinOps · Benchmark · AI Manager · ROI
Financial operations, spending analysis, benchmarks, and return-on-investment tracking.ProjectsObjectives · Key Results · Initiatives · ROI
OKR framework and initiative tracking for your data strategy.Starting with Klarun
Follow these steps when setting up Klarun for the first time. The order matters — organization settings and integrations unlock data that later steps depend on.
01
Complete Organization Settings
Go to Settings → Organization. Fill in your organization name, industry, company size, fiscal year start month, and timezone. These values power FinOps reports and benchmark comparisons.
02
Verify your domain
Still in Settings → Organization, register your company email domain. Once verified, anyone with a matching email can join via an invite link — no one-off codes required.
03
Invite your team
Go to Settings → Membership and generate an invite link. Choose multi-use (whole team), email, domain, or single-use types. Assign roles before or after members join.
04
Connect integrations
In Settings → Integrations, connect Power BI and / or Databricks. Once connected, Klarun syncs all reports and assets from those platforms automatically.
05
Populate Reporting
In Reporting → Report Catalog, your synced reports will appear immediately. Enrich them with Domain, Subdomain, Owner, and Schedule. Manually register any reports from other tools.
06
Build out People
In People → Data Team, add every member of your data organization. Complete profiles — role, squad, seniority, skills, platforms, and languages — unlock Team Management analytics and AI Manager insights.
07
Add onboarding resources
In People → Onboarding, upload documents, paste links, or write text notes in each of the eight onboarding sections. New joiners access everything from this page.
08
Register platform architecture
In Platform → Architecture, document your data layers and infrastructure components. In Platform → Health, add any ongoing incidents or known issues.
09
Set up Governance
Data Assets are synced from integrations. In Governance → Contracts, add your data source contracts and SLAs. In Governance → Quality, log active quality issues.
10
Configure Intelligence
In Intelligence → FinOps, enter your budget plan and actual monthly spending per platform and category. The benchmark and ROI pages use your organization profile and data team entries.
11
Define Projects (OKRs)
In Projects → Objectives, create your strategic goals. Link Key Results to each objective, then create Initiatives — the concrete work items — on the Initiatives kanban.
Free Plan
Klarun offers a free plan that lets you get started without a credit card. It is designed for small teams exploring the platform or for organizations that primarily need the core Reporting module.
Free — $0 / month
- Up to 5 users
- Core reporting module
- Basic data governance
- Community support
To unlock all modules — Reporting, Governance, Platform, People, Projects, and FinOps — plus Power BI and Databricks integrations, upgrade to the
Business plan ($700 / month) or higher. See the
pricing page for a full comparison.
Module
Reporting
What it is
The Reporting module is the central registry for all reports, dashboards, and data products in your organization. It gives every stakeholder a single place to find what exists, who owns it, how often it refreshes, and where to open it.
Pages: Report Catalog, Maturity Benchmark
What it can be used for
Report discoveryLet any stakeholder find reports across all BI tools from one search.
Ownership trackingKnow who is responsible for each report and who to contact for updates.
Refresh visibilitySurface report freshness — daily, hourly, or on demand — to consumers.
Catalog enrichmentTag reports with domains and subdomains to enable business-aligned filtering.
Maturity assessmentBenchmark your organization's reporting maturity across key dimensions.
How to fill it
Reports enter the catalog in two ways: automatic sync from connected integrations (Power BI, Databricks) or manual registration for any other tool.
Report Catalog fields
| Field | Description |
|---|
| Report Name | Display name of the report or dashboard. |
| Link | URL that opens the report. Auto-filled from Power BI / Databricks sync. |
| Description | Free-text context — what the report shows, who it is for. |
| Domain | Top-level business domain (e.g. Finance, Marketing). Manually set. |
| Subdomain | Sub-classification within the domain (e.g. Revenue, Attribution). |
| Workspace | Origin workspace. Auto-filled and locked when synced from a BI tool. |
| Owner | Email address of the person responsible for this report. |
| Schedule | How often the report refreshes (e.g. Daily, Hourly, On demand). |
| Tool | BI tool used to build the report (e.g. Power BI, Looker, Metabase). |
| Status | Active · Pending Review · Maintenance · Deprecated. |
| Tags | Free-form labels for search and filtering. |
Sync note: When a report is imported from Power BI or Databricks, the fields Report Name, Link, Tool, and Workspace are locked and overwritten on each sync. All other fields — Domain, Subdomain, Owner, Schedule, Description, and Tags — remain editable and are preserved across syncs.
Access notes
reporting_adminCan register, edit, delete, and manage all reports. Access to integration sync.
reporting_contributorCan register, edit, and delete reports.
reporting_viewerRead-only. Can browse, search, and open reports.
Module
Governance
What it is
The Governance module provides a unified view of your data ecosystem's health: all platform assets, their quality status, and the contracts governing your data sources.
Pages: Dashboard · Data Assets · Quality · Contracts
What it can be used for
Asset visibilitySee every report, semantic model, notebook, pipeline, and lakehouse in one place.
Health monitoringIdentify broken, orphaned, or stale assets before they impact consumers.
Quality trackingLog and resolve data quality issues with ownership and severity tracking.
Contract managementTrack SLAs, renewal dates, trust status, and criticality per data source.
Governance overviewDashboard KPIs showing total assets, health scores, and open quality issues.
How to fill it
Data Assets are populated automatically from Power BI and Databricks integrations — no manual entry needed. Assets are enriched with health flags (broken, orphan, stale) computed from integration metadata.
Contracts are entered manually. Each contract represents a data source your organization depends on. Fill in the fields below to track obligations and risk.
Contract fields
| Field | Description |
|---|
| Name | Display name for the data source or vendor contract. |
| Source Name | The underlying data source identifier. |
| Domain | Business domain this source belongs to. |
| Owner | Person accountable for this data source. |
| Criticality | Low · Medium · High · Critical — business impact if this source fails. |
| Trust | Watch · Stable · Deprecated — reliability status. |
| Contract Tier | None · Bronze · Silver · Gold — SLA tier agreed with the provider. |
| SLA | Expected availability or delivery window (e.g. "99.5% uptime"). |
| Classification | Internal · External · Confidential — data sensitivity level. |
| Consumers | Number of downstream consumers of this source. |
Quality issues are logged manually. Each issue captures the affected asset, description, severity, owner, and resolution status.
Access notes
governance_adminFull access. Can manage assets, create/edit/delete contracts and quality issues.
governance_contributorCan create and edit contracts and quality issues.
governance_viewerRead-only access to all governance pages.
Module
People
What it is
The People module is the hub for your data organization's human layer. It combines a team registry, workforce analytics, an onboarding resource library, and an AI-powered manager assistant.
Pages: Data Team · Team Management · Onboarding · AI Manager
What it can be used for
Team registryMaintain a live directory of every data team member with skills, platforms, and seniority.
Org chartVisualize the team hierarchy, grouped by seniority, with drill-down profile cards.
Workforce analyticsUnderstand team composition, skill coverage, seniority distribution, and domain ownership.
Critical skill alertsIdentify skills held by only one member — a key operational risk.
Onboarding libraryStore and share every resource a new data team joiner needs, organized by onboarding phase.
AI ManagerGet AI-generated insights, recommendations, and summaries about your team's capabilities.
How to fill it
Data Team — profile fields
| Field | Description |
|---|
| Name | Full name of the team member. |
| Role | Job title, selected from the standard data role list. |
| Squad | Team or chapter: Platform, AI / ML, Analytics, Governance. |
| Seniority | Trainee · Junior · Mid · Senior · Lead · Management. |
| Status | Active or Inactive. |
| Location | City or country. Free text. |
| Department | Wider business department. Free text. |
| LinkedIn | Profile URL, shown as a link on the member card. |
| Skills | Named skills with a proficiency level (1 Beginner → 5 Expert). |
| Platforms | Tools and platforms the member works with. |
| Languages | Programming or query languages (e.g. Python, SQL, R). |
| Domain Ownership | Business domains the member is responsible for. |
| Salary | Monthly gross salary. Visible to admins only. |
Onboarding — sections
The Onboarding page is organized into eight fixed sections. Admins populate each section with documents, links, or text content.
| Section | Goal | Typical content |
|---|
| Access | Remove all friction to start | System access, repo access, credentials, VPN setup |
| Business Context | Understand why the data exists | Company overview, key domains, core KPIs, data use cases |
| Ways of Working | How things get done | Dev workflow, sprint model, comms channels, Definition of Done |
| Data Architecture | Understand the big picture | Architecture diagrams, data flow, medallion strategy, key platforms |
| Engineering | How to build things | Coding standards, pipeline patterns, naming conventions, CI/CD |
| Analytics | How data is consumed | BI standards, semantic models, metrics layer, report best practices |
| Governance | Rules and responsibilities | Data ownership, access control, quality expectations, compliance |
| AI & ML | Advanced capabilities | ML workflows, feature engineering, model deployment, experiment tracking |
Resource types
DocumentUpload any file (PDF, DOCX, XLSX, etc.). Stored securely; a Download button appears on the card.
LinkPaste any URL (Confluence, Notion, YouTube, etc.). An Open button opens it in a new tab.
TextWrite plain text or Markdown directly in Klarun. Shown inline with a Show more / Show less toggle.
Access notes
people_adminCan add, edit, and delete team members and onboarding resources. Can view salary data.
people_contributorCan add and edit team members and onboarding resources. Cannot view salary data.
people_viewerRead-only access to profiles, org chart, Team Management analytics, and onboarding resources.
Module
Intelligence
What it is
The Intelligence module gives data leadership the financial and strategic visibility they need to run the data function as a business. It covers cost management, external benchmarking, AI-powered recommendations, and return-on-investment analysis.
Pages: FinOps (Overview · Budget · Actuals) · Benchmark · AI Manager · ROI
What it can be used for
Cost trackingMonitor planned vs. actual spending per platform and cost category, month by month.
Budget planningBuild out your data platform budget by tool and category for the fiscal year.
BenchmarkingCompare your team's maturity, cost structure, and coverage against industry peers.
ROI analysisQuantify the return on your data investments using a structured framework.
AI ManagerAI-generated strategic insights and recommendations based on your organization's data.
How to fill it
FinOps — Budget: Add budget lines for each data platform (e.g. Databricks, Snowflake, Power BI) broken down by cost category and month. The fiscal year calendar is driven by your Organization Settings → Fiscal Year Start.
FinOps — Actuals: Enter or import actual monthly spending for each platform and category. The Overview page computes variance between budget and actuals automatically.
Benchmark and ROI pages derive their analysis from your organization profile (industry, size) and the data in other modules (People, Reporting, Governance). No separate data entry is required, but the accuracy of results depends on keeping those modules up to date.
Access notes
finops_adminCan create, edit, and delete budget lines and actuals. Full FinOps access.
finops_contributorCan add and update budget lines and actuals.
finops_viewerRead-only access to all Intelligence pages.
The Benchmark and ROI pages are read-only and accessible to any role that has Intelligence module access. The data_exec_viewer and business_viewer org-wide roles also include access to these overview pages.
Module
Projects
What it is
The Projects module is Klarun's OKR (Objectives and Key Results) framework. It gives data teams a structured way to define their strategy, track measurable outcomes, and manage the concrete work items that deliver on those outcomes.
Pages: Objectives · Key Results · Initiatives · ROI
What it can be used for
Strategic alignmentConnect day-to-day work to high-level business goals through a three-tier hierarchy.
Outcome trackingMeasure progress against Key Results with numeric targets and milestones.
Initiative kanbanManage work items — initiatives — on a kanban board linked to Key Results.
ROI measurementAttach financial impact estimates to initiatives to quantify data team contribution.
How to fill it
Start top-down: create Objectives first, then add Key Results to each one, and finally create Initiatives under Key Results.
ObjectiveTitle, description, owner, quarter, status (On Track / At Risk / Off Track / Done).
Key ResultTitle, linked objective, metric type (number, percentage, binary), start value, target value, current value, due date.
InitiativeTitle, description, linked key result, owner, priority, status, start and end dates, estimated and actual impact (for ROI).
Access notes
projects_adminFull access. Can create, edit, delete objectives, key results, and initiatives.
projects_contributorCan create and update objectives, key results, and initiatives.
projects_viewerRead-only access to all Projects pages.
Configuration
Organization Settings
Settings are accessible from the sidebar under your organization name. The page is divided into four tabs: Organization, Integrations, Membership, and Billing. Only users with the org_admin role can modify settings.
Organization tab
Configure your organization profile. These values appear throughout the app and power features like FinOps and benchmarking.
| Field | Description |
|---|
| Name | Your organization's display name, shown throughout the app. |
| Description | Short description of your data team or organization. |
| Industry | Your company's industry sector. Used for benchmark comparisons. |
| Size | Headcount range of the overall company (not just the data team). |
| Website | Company website URL. |
| Country | Country of the organization's headquarters. |
| Timezone | Used to localize scheduled refresh times and reports. |
| Fiscal Year Start | The month your fiscal year begins. Affects FinOps period calculations. |
Domain verification
Register your company email domain to enable domain-based invite codes. Anyone with a matching email address can then join your workspace using a domain invite link, without needing a one-off code.
Verification is done via a one-time code sent to an admin email on the registered domain. Once verified, the domain is locked and used for all future domain invites.
Integrations tab
Connect your BI tools to Klarun. Synced integrations automatically populate Reports (Reporting module) and Assets (Governance module).
Power BI — setup steps
01
Create an Azure App Registration
Go to Azure Portal → Microsoft Entra ID → App registrations → New registration. Give it any name (e.g. "Klarun Integration"), select Single tenant, and click Register.
02
Add the Power BI API permission
Inside the app registration, open API permissions → Add a permission → Power BI Service → Application permissions. Select Tenant.Read.All, then click Add permissions.
Power BI Service → Application permissions → Tenant.Read.All03
Assign the Fabric Administrator role
In the Microsoft 365 admin center (admin.microsoft.com), assign the Fabric Administrator role to the service principal you just created.
04
Enable admin API access in Power BI
Open Power BI Admin Portal → Tenant settings → Developer settings. Enable "Allow service principals to use read-only admin APIs".
Power BI Admin Portal → Tenant settings → Developer settings → Allow service principals to use read-only admin APIs05
Create a client secret
Back in the app registration → Certificates & secrets → New client secret. Set an expiry, click Add, then copy the Value immediately — it is only shown once.
06
Connect in Klarun
Go to Settings → Integrations → Power BI → Connect. Enter your Tenant ID, Application (Client) ID, and the Client Secret value. Click Test connection — if successful, click Save & sync.
Why the admin API?The standard Power BI API only returns workspaces where the Service Principal is a direct member. The admin API returns all tenant workspaces — which is why the Fabric Administrator role and the “read-only admin APIs” setting are required.
Databricks
Connect one or more Databricks workspaces using a personal access token and workspace URL. Once connected, Klarun syncs notebooks, pipelines, and ML assets as Governance assets and enriches the Report Catalog with Databricks-backed reports.
Membership tab
Manage who belongs to your Klarun workspace. You can view all current members, change their roles, and create invite codes.
Invite code types
| Type | Behavior |
|---|
| Multi-use | Anyone with the link can join. Expires after 30 days. |
| Email | Only a specific email address can use this code. |
| Domain | Anyone with an email from a specified domain can join. |
| Single-use | One person only. Expires after 7 days. |
Billing tab
View your current plan and manage your subscription. Upgrading, downgrading, and entering payment details are all handled from this tab. Only users with the org_admin role can access the Billing tab.
Access control
Roles
Klarun uses a layered role system. Every member has one org-wide role that controls baseline access across the entire workspace, plus optional module-specific roles that grant elevated permissions within individual modules.
Org-wide roles
Assigned at the workspace level. Apply to all modules unless overridden by a module-specific role.
| Role | Description |
|---|
| org_admin | Full access to all modules and all organization settings. |
| org_member | Default role for new members. Read access to most content. |
| org_contributor | Can create and edit content across all modules. |
| org_viewer | Read-only access across the entire organization. |
| business_viewer | Focused read-only view. Can see reports, projects, and dashboards. |
| data_exec_viewer | Executive read-only view with access to high-level summaries. |
Module-specific roles
Each module has three tiers: admin, contributor, and viewer. Module roles are additive — assigning a module role to a member grants that permission level for that module regardless of their org-wide role.
| Module | Admin | Contributor | Viewer |
|---|
| Reporting | reporting_admin | reporting_contributor | reporting_viewer |
| Governance | governance_admin | governance_contributor | governance_viewer |
| Platform | platform_admin | platform_contributor | platform_viewer |
| People | people_admin | people_contributor | people_viewer |
| Projects | projects_admin | projects_contributor | projects_viewer |
| FinOps | finops_admin | finops_contributor | finops_viewer |
Permission matrix
Baseline permissions by role tier, applicable across all modules. Module admins have the same privileges as org admins within their module scope.
| Action | Admin | Contributor | Viewer |
|---|
| View all content | ✓ | ✓ | ✓ |
| Create, edit, and delete records | ✓ | ✓ | — |
| Manage organization settings | ✓ | — | — |
| Manage members and roles | ✓ | — | — |
| Manage integrations | ✓ | — | — |
| Generate and share invite links | ✓ | ✓ | — |
| View salary data (People module) | ✓ | — | — |
Roles are assigned from Settings → Membership. Select a member, click Edit roles, and choose from all available org-wide and module-specific roles. Changes take effect immediately on next page load.