Identity and access
Single sign-on through Microsoft Entra ID, with automatic user provisioning. Close an account in Entra and access to Komma closes at the same moment — which is the half of offboarding people usually forget.
Integrations
Fits the tools you already run.
Single sign-on, calendars, chat, job boards and six Nordic payroll engines — connected, not exported. You should not have to change the rest of your stack to change your HR system.
Microsoft Entra
Microsoft 365
Teams
Slack
Google Workspace
LinkedIn
DATEV
ZapierWhat connects where
Four kinds of connection
Calendar and chat
Absence and shifts appear in Microsoft 365 and Google Workspace calendars. Approvals and Karma nudges can arrive in Teams or Slack instead of another inbox nobody reads.
Job boards
Publish a job to LinkedIn and Indeed from the same screen you wrote it on, and pull applications back into the pipeline rather than into an email folder.
Payroll engines
Approved gross pay lines hand over to Zenegy, Danløn, Dataløn, Visma, Lessor or Intect, and the engine's return data comes back for reconciliation. You keep the engine you already run.
Payroll
Six Nordic engines
Komma builds and validates gross. The final gross-to-net calculation, A-skat, AM-bidrag, eIndkomst and payslips stay where they are.
ZenegyGross handoff and return data
DanlønGross handoff and return data
DatalønGross handoff and return data
VismaGross handoff and return data
LessorGross handoff and return data
IntectGross handoff and return data
Running something else? Tell us which engine and we will say honestly whether it is a fit today.
API
A real API, with a role model in front of it
Every module is reachable over a documented REST API, so employee data, absence, pay lines and candidates can feed a BI tool, an intranet or a system nobody else has heard of. What makes it safe to hand out is the layer in front of it: a key is issued against a data role, and the role decides which objects and which fields that key may read. A key built for headcount reporting cannot return a salary, a CPR number or the reason somebody is on sick leave — not because the caller filters them out afterwards, but because they never leave Komma.
- Documented REST endpoints across every module, plus webhooks on real events
- Each key is issued against a data role rather than against a person
- The role decides objects and fields — salary, CPR and absence reasons can be excluded
- Scope, rate limit and expiry per key; revoke one without touching the rest
- Every call in the audit log with its key, endpoint and what it returned
Active keys
4
issued, 1 expiring
Calls
8.412
in the last 24 hours
Blocked by role
37
fields the role excludes
KeyData roleLast used
BIInsights BIRead only2 min ago
INIntranet feedRead only1 hour ago
LØPayroll exportRead onlyLast pay run
OBOnboarding botRead and writeYesterday
What the Insights BI key may read4 / 8
✓Name
✓Department
✓Job title
✓Start date
✕Salary
✕CPR number
✕Absence reason
✕Bank details
Everything else
Zapier for the long tail
No integration list covers every tool a company runs. Zapier handles the ones that matter to you but not to everybody — and because Komma is one dataset, a trigger fires on the event itself rather than on a nightly export landing somewhere.
- Triggers on real events: a hire, a leaver, an approved absence
- The same role-based access applies to what a connection can see
- Every outbound call recorded in the audit log
- DATEV for accounting hand-off where you need it
Connected
6
of 8 available
Sync events
1.240
last 24 hours
Failures
0
last 7 days
IntegrationStatusLast sync
ENMicrosoft Entra IDConnected2 min ago
TETeamsConnected14 min ago
ZEZenegyPay run onlyLast run
ZAZapierAvailable—
Will it fit your stack?
Tell us what you run today. If something important is missing we would rather say so before a demo than after one.