Skip to main content

Multi-Tenancy, Security & Governance

Each business is isolated, each location is scoped, and every sensitive action is recorded. This governance layer is what makes iShopMaster safe for multi-branch operations and staff with varied access.

Isolation and scoping

Data separation is structural, not just a filter.

Database-per-tenant
Each business is isolated in its own database.
Branch scoping
Within a business, stock and operations are scoped per branch.

Access control and approvals

Staff see and do only what their role allows, with sign-off where it matters.

RBAC
Role-based permissions across view, create, edit, delete, approve, export and manage.
Approvals
Approval workflows gate sensitive operations.

Audit trail and entitlements

Actions are recorded and capacity is metered by plan.

Forensic audit
Sensitive actions, including price changes, are logged.
Entitlements & quotas
Plan-based features and metered limits (items, IMEI units, branches, warehouses, API calls).

Frequently Asked Questions

How is each business’s data kept separate?

iShopMaster uses database-per-tenant isolation, with per-branch scoping of stock and operations within each business.

Can I control what staff can do?

Yes — role-based access control across view/create/edit/delete/approve/export/manage, plus approval workflows for sensitive actions.

Is there an audit trail?

Yes — a forensic audit trail records sensitive actions, including price changes.

Explore the rest of the system

← Full system overviewBook a demo