Chained trail
Each event is sealed with the previous hash: if someone alters a record, the integrity check points to it.
Audit & security
You know who did what, and nobody can erase their tracks.
Every data change, sign-in and sign-out lands in a hash-chained trail whose integrity you can verify. On top of that: more than 900 fine-grained permissions, IP rules, two-step verification and a modern password policy.
Without MKA
- An amount changed "by itself" and nobody knows who or when.
- Everyone logs in as admin because setting up roles is a pain.
- One leaked password is enough to get into the system from anywhere.
What you’ll measure
Trail integrity
100 %0 eslabones rotos
last check
Users with 2FA
86 %+34 pts
Failed sign-ins
37−41 %
per week
Users with admin role
3−9
Sample indicators with illustrative data. In MKA they are computed live from your operation.
Try it right here
The auditor tampers with a trail record and verifies integrity.
This is the internal auditor’s view: click "Verify integrity" and the chain comes out intact; filter by "Security" to see sign-ins only. Then "Tamper #1044 in the DB" simulates someone changing an amount straight in the database, and the next check stops in red exactly at the tampered link. "Watch it run" plays it for you.
Example flow
From a new user to a surprise-free audit
Step 1/5
The user is created
They get a role with just the right permissions, their warehouses and, if needed, IP rules.
OrganizationBenefits
Why Audit & security in MKA
Sign-ins and changes on one screen
Search, stats, a security-events filter and audit by entity or by user.
More than 900 permissions
Roles built from fine-grained permissions, with bulk role-permission upload.
Hardened sign-in
Two-step verification by email, temporary lockout, CAPTCHA and passwords per NIST 800-63B.
IP rules
Limit where people sign in from and bind each POS terminal to its till.
Per-warehouse permissions
Each user works only the warehouses assigned to them, enforced on the server.
In detail
Everything included
Audit trail
- Hash chain with integrity verification
- Search, stats and security-events filter
- Audit by entity and by user
- Sign-ins and sign-outs next to data changes
- Log viewer
Permissions and roles
- More than 900 fine-grained permissions
- Roles with bulk permission upload
- Per-warehouse permissions enforced on the server
- Menu visibility per user and role (permission > role > personal preference)
- Module activation per company
Access
- Two-step verification by email, per user, with a recovery flow
- Password policy per NIST 800-63B
- Temporary lockout after failed attempts and CAPTCHA
- IP access rules and POS terminals bound to their till
All-in-One
Connects with
Data flows between modules on its own: no integrations, no exporting or importing.
OrganizationA living org chart and a complete file for every person.AccountingJournal entries that build themselves from your documents.InventoryMulti-warehouse stock with approved transfers, kardex and counts that add up.Point of sale (POS)A fast till that keeps selling and invoicing even when the internet drops.Approval workflowsApprovals with roles, conditions and SLAs, designed without code.
FAQ
Is hiding a menu the same as removing a permission?
No. Menu visibility is presentation only; what protects the data are the permissions, which are enforced on the server.
What does the integrity check detect?
That a trail record was modified after it was written: its hash no longer matches the chain and the check shows where it broke.
More in Platform
See Audit & security with your data.
In 30 minutes we walk through your real flow: from sale to invoice, from stock to journal entry.