Amwal Tech logoDocs

User Roles and Permissions

Amwal implements strict Role-Based Access Control (RBAC) to ensure data security, segregation of duties, and compliance with Saudi Central Bank (SAMA) financial security standards. By assigning granular roles, organizations can empower staff to perform daily duties while preventing unauthorized configuration changes, credential leaks, or fraudulent refunds.


1. Role Definitions & Scopes

Rendering diagram...

1. Owner (Root Administrator)

The Owner is the primary account holder tied to the corporate Commercial Registration (CR) and primary authorized signatory:

  • Full System Authority: Complete unrestricted access across all stores, settings, bank accounts, and developer tooling.
  • Organization Governance: Only role authorized to modify bank IBAN payout designations and delete organization accounts.
  • Key Authority: Full visibility into Sandbox and Production API Secret Keys.

2. Admin (Store Administrator)

The Admin manages day-to-day business operations across stores:

  • User Administration: Invite, edit, and deactivate team members (excluding Owner profiles).
  • Technical Configuration: Create new stores, configure webhook listeners, and manage plugin integration settings.
  • Reporting & Auditing: Full access to real-time sales feeds, settlement ledgers, and transaction refund capabilities.

3. Accounting (Finance & Bookkeeping)

The Accounting role is tailored for CFOs, financial controllers, and internal auditors:

  • Financial Reconciliation: Inspect daily settlement batches, SARIE interbank transfer reference codes, and net payout amounts.
  • Tax Compliance: Download ZATCA and SAMA-compliant electronic VAT tax invoices (PDF/Excel/CSV).
  • Strict Restrictions: Cannot alter store configurations, issue refunds, invite users, or view API Secret Keys.

4. Operation (Fulfillment & Customer Support)

The Operation role supports customer service and warehouse fulfillment teams:

  • Transaction Inspection: Search payments by order ID, buyer phone number, or transaction hash to verify payment receipt.
  • Customer Remediation: Issue partial or full card refunds for returned items within permissible banking timeframes.
  • Strict Restrictions: Cannot access settlement payout statements, corporate banking details, or system settings.

5. Supervisor (Branch Manager)

The Supervisor oversees physical retail sales counters and in-store staff:

  • Branch Operations: Monitor cashier sales performance, generate in-store payment links, and present checkout QR codes.
  • Branch Audit: Review localized transaction history specific to their assigned branch location.
  • Strict Restrictions: Cannot view organization-wide financial statements or access online store API settings.

6. Cashier (POS Counter Operator)

The Cashier is a streamlined, distraction-free role designed for fast-paced retail checkout counters:

  • Checkout Link Generation: Create instant SMS payment links and display scannable on-screen QR codes for walk-in shoppers.
  • Real-Time Verification: Use the Get Status button to confirm successful customer payment authorization before handing over merchandise.
  • Strict Restrictions: Cannot issue refunds, view financial statements, or modify store settings.

2. Granular Permissions Matrix

Feature / ActionOwnerAdminAccountingOperationSupervisorCashier
Manage Organization & IBANFullNoneNoneNoneNoneNone
Create & Manage StoresFullFullNoneNoneNoneNone
Invite & Manage UsersFullFullNoneNoneNoneNone
View API Secret KeysFullFullNoneNoneNoneNone
Configure WebhooksFullFullNoneNoneNoneNone
Create Payment Links & QRFullFullView OnlyView OnlyBranchBranch
View Transactions FeedAllAllAllAllBranchBranch
Issue Payment RefundsFullFullNoneFullNoneNone
View Settlement PayoutsFullFullFullNoneNoneNone
Download ZATCA VAT InvoicesFullFullFullNoneNoneNone
Manage Branch LocationsFullFullNoneNoneNoneNone

3. Best Practices for Enterprise Security

Principle of Least Privilege (PoLP)

Always assign staff the minimum role required for their daily tasks. For example, store cashiers should never be assigned the Admin or Operation role, which prevents accidental store misconfigurations or unauthorized refunds.

On this page