Identity and access
Give owners, accountants, managers and counter staff only the workflows their responsibilities require.
- Role-based module permissions
- Owner-only sensitive controls
- Account recovery safeguards
- Timely user deactivation

DukaanMatic combines local resilience with secure connected services, controlled access and traceable activity—so owners can operate confidently without losing visibility.

Security is applied across people, devices, data and synchronization—not treated as a single feature.
Give owners, accountants, managers and counter staff only the workflows their responsibilities require.
Reduce unnecessary exposure while business information moves between supported DukaanMatic services.
Keep users, branches and business records inside the correct organisational context.
Preserve useful operational context for important changes and user activity where the workflow supports it.
Support recoverability through connected backup workflows and operational safeguards while preserving local continuity.
Continue essential local work through an outage, then synchronize pending changes when connectivity returns.
Short, practical walkthroughs explain what owners configure, what staff experience and what to review when something changes.
VIDEO GUIDE · 9 minMap counter, purchasing, accounting and owner responsibilities to the minimum access each role needs.
VIDEO GUIDE · 7 minUnderstand local continuity, pending changes and the checks to make before and after synchronization resumes.
VIDEO GUIDE · 10 minUse transaction, user and time context to investigate changes without exposing more business data than necessary.
Security controls work together throughout the lifecycle of business activity.
DukaanMatic protects the service foundation. Business owners remain responsible for authorised users, device safety and appropriate operational access.
Yes. DukaanMatic is designed for local continuity in core workflows. Connected features and pending synchronization resume when connectivity returns.
No. Role-based permissions are designed to limit users to the workflows and information appropriate for their responsibilities.
No. The Privacy Policy explains the limited operational and service-provider uses of information required to deliver and protect the service.
Email [email protected] with clear reproduction details. Avoid including passwords, full financial exports or other unnecessary sensitive information.