Admin, settings, security, module access, audit, and approvals

Users and roles — access control

What it is. Users creates accounts and assigns roles, unlocks, and resets them. Roles defines the company role set and the permission matrix; system roles are read-only so the built-in safety floor cannot be edited away.

How to use it. Create a user and assign one or more roles; the Users table shows status, roles, and last sign-in so you can audit access at a glance. Build custom roles under Roles by composing permissions, and keep system roles for the standard tiers.

Use it wisely. Grant least privilege — assign the narrowest role that lets someone do their job, and use the last-sign-in column to spot dormant accounts. Pair roles with approvals to enforce segregation of duties: the person who creates a transaction should not be the only one who can approve it.

Module Access — entitlements and seats

What it is. Module Access activates marketplace modules for the organization and assigns seats to specific users. Each optional module shows an Activated toggle (On/Off) and a Seats count with a Manage seats link — so you control both whether a capability is on and who can use it.

How to use it. Toggle a module On to make it available to the tenant, then assign seats to the users who need it. In the demo, CRM is On with one seat assigned, while HR, Group Consolidation, Rental Management, Exhibition, Point of Sale, Manufacturing, and the various Advanced modules are available but Off. Turning a module on makes its navigation and routes appear for entitled users.

Use it wisely. Activation and seats are separate decisions: turning a module on does not give everyone access — assign seats deliberately to control cost and surface area. If a user reports a missing module, check Module Access first; the route gating that redirects them to the marketplace is this entitlement system working as designed, not a fault.

Organization and branches

What it is. Organization holds the company's identity and structure; Branches defines the locations or business units the organization operates, so data can be scoped and reported by branch.

How to use it. Set the organization details under Organization, then define each operating location under Branches. Branches give you a structural dimension for reporting and access without splitting into separate tenants.

Use it wisely. Model branches to match how you actually report — too many fragments your numbers, too few hides them. Set this up before transacting so every document is attributed correctly from the start.

Finance defaults — accounting, currencies, exchange rates

What it is. Accounting Defaults sets the accounts and posting rules documents use by default; Currencies defines the currencies you transact in; Exchange Rate Settings controls how rates are sourced and applied. Together they make finance behave consistently without per-document decisions.

Use it wisely. Get the default accounts right before invoicing — they determine where revenue, receivables, and tax post, and fixing mis-posted history is far harder than configuring once. Keep exchange rates current so foreign-currency balances are never silently misstated (see the Finance page).

Display, translations, and localisation

What it is. Display controls presentation preferences (formats, theme defaults); Translations and Languages manage the interface languages — English, Arabic, Spanish, and French are present, and Arabic reflows the shell right-to-left.

Use it wisely. Set display formats to local convention up front so dates and numbers read naturally for every user. Use translations to tailor terminology to your industry, and demo the RTL language switch as a concrete localisation proof point.

Audit log — traceability

What it is. The Audit Log records who did what and when across the system. It is the evidence trail behind every configuration change and sensitive action.

Use it wisely. Reach for the audit log first when investigating "who changed this?" rather than guessing. Treat it as read-only history — its value is that it cannot be quietly rewritten.

Approvals — control and segregation of duties

What it is. The Approvals screen is the worklist for items awaiting sign-off. It is how the system enforces that significant actions get a second pair of eyes.

Use it wisely. Route material transactions through approvals and make the approver someone other than the originator. Clear the queue by deciding, not by ignoring; notifications surface waiting approvals so they do not stall work.

Webhooks and notifications

What it is. Webhooks let external systems receive events from the ERP for integration; Notifications (the toolbar bell) surface approvals, reminders, and background-job results inside the app.

Use it wisely. Use webhooks for genuine event-driven integration rather than polling, and keep signing secrets and endpoint URLs in secure configuration, out of screenshots. Treat notifications as a worklist to act on, not noise to dismiss.