48 modules organized into 8 categories, 6 actions per module (view, create, edit, delete, approve, export). A guard function on every page — access is limited to users with permission.
48 modules in 8 categories. 6 actions per module. Server-side guard function. Your tenant configures them; you manage them.
48 modules organized into 8 categories. Each profile configures 6 actions per module: view, create, edit, delete, approve and export. Rule: users can only grant permissions they have.
Access profiles show how many users are assigned to each one. Super Admin, Admin, Operator, Finance, Merchant, Distributor — and as many more as the tenant needs.
Every page and action passes through requirePermission() on the server. No permission = no access. Complete audit trail: who did what, when and from where.
Permission screens, user invitations and role management — all under your tenant's brand. The tenant's client never sees "Ezcale". You deliver it as a native feature.
Yes. There are 48 modules organized into 8 categories, each with 6 actions (view, create, edit, delete, approve, export). The tenant creates profiles and configures permissions per module. Security rule: it can only grant permissions it has itself.
Yes, within the scope allowed by the tenant. The merchant can invite users, assign roles and manage access — all limited by the permissions the tenant configured for that level.
Every action generates an immutable record: user, action, module, date/time and IP. The tenant exports reports for external audits or regulators. Retention is configurable under the tenant's policy.
Your tenant configures it. Your merchant uses it. Ezcale provides the technology. Set up in days.