Access & control

Give each user exactly the access they need

Five ready-made roles and granular per-module permissions keep your books tight — staff raise documents, suppliers see their own, and only admins touch the settings that matter.

Business event Debit account Credit account P&L Balance sheet Trial balance
Every event posts balanced debits and credits that roll straight into P&L, balance sheet and trial balance.

Five roles, ready on day one

Kanakku ships with sensible defaults so you can onboard a team without designing a permission matrix from scratch. Each role maps to a real job, and you tune access from there.

  • Default roles: Admin, Vendor, Staff, Maintainer, Supplier
  • Admins manage settings, users, gateways and the chart of accounts
  • Staff raise and manage documents without touching configuration
  • Suppliers and vendors get scoped access to their own records

Granular permissions, audited actions

Go beyond the defaults with per-module control over who can view, create, edit, approve or delete. Pair it with maker-checker so sensitive changes are reviewed before they hit the ledger.

  • Per-module view / create / edit / delete permissions
  • Gate high-value documents behind maker-checker approval
  • Scope users to their own customers, suppliers or projects
  • Self-hosted — no third party ever sees your access policy

What you get

Sensible defaults

Five built-in roles cover most teams without any setup.

Granular control

Tune view, create, edit and delete rights per module.

Maker-checker

Route sensitive changes through an approval step before posting.

Least privilege

Scope each user to only the records and actions their job needs.

Works with

Popular with

Frequently asked questions

What roles does Kanakku include by default?
Five: Admin, Vendor, Staff, Maintainer and Supplier — each mapped to a real job, and adjustable from there.
Can I control permissions per module?
Yes. Access is granular — you set view, create, edit and delete rights per module, not just one global level.
Can I require approval for sensitive changes?
Yes. Maker-checker routes high-value documents through pending → approved/rejected before they post to the ledger.
Where is access policy stored?
On your own self-hosted instance. No external service ever sees your users or their permissions.

Own your accounting stack — start today.

Self-hosted, source-included, white-label ready. No per-seat SaaS lock-in.