Set up the foundation — people, access, structure and the system itself

1) Enter the legal name in Arabic and English — both are used, so fill both.
2) Add the commercial registration and tax number: these print on invoices and are what the e-invoicing addon submits.
3) Set the head-office address, phone and email.

1) Upload the logo for the sidebar, the login screen and printed documents.
2) On Color System, set your primary colour once.

Countries ship pre-loaded. Add the states and cities you actually operate in — every address field in the system (customers, vendors, branches, employees) picks from these lists, so an unlisted city cannot be selected later.

Each list has Import and Export. Download the template, fill it in a spreadsheet and upload — far quicker than typing dozens of cities one at a time.

1) Create one branch per real location — a shop, a warehouse site, a regional office.
2) Give each a name in both languages and an address.
3) If you will use attendance, drop the map pin and set the allowed radius: staff can then only check in from inside it.

Review them against how your organisation actually works, then duplicate and adjust rather than starting empty.

1) Name the role in both languages.
2) Expand a module group and tick what the role may do. Each group splits into Operations (daily work) and Settings (configuration), so you can grant the work without granting the configuration.
3) Use "select all" on a group when a role genuinely owns that whole area, and the counter beside each group to check you granted what you meant to.

1) Enter their name, email and mobile.
2) Attach the role — this is the whole access decision.
3) Set their branch, and mark the account active.

Download the template, fill one row per person, upload. Import history shows exactly which rows succeeded and why any failed.

When someone leaves, switch the account to inactive. They can no longer sign in, and every document they created keeps their name on it.

For each area, choose how wide the role can see: only their own records, their branch, or everything. A branch manager is usually "branch"; a group financial controller is "all".

Name the exact branches, warehouses, cash boxes or bank accounts one user may touch. Leave it empty and the role's scope decides; fill it and it wins.

Every signed-in session across the system: who, which device and browser, which IP, and when it was last active.

End any session you do not recognise. The user is signed out immediately, and their "remember me" is invalidated too — so the device cannot silently sign itself back in.

Successful and failed attempts alike, with time, IP and device. Repeated failures against one account, or a success from an unexpected country, are the two patterns worth acting on.

Anyone can see their own sessions and sign out everywhere else — confirming with their password. Left a laptop signed in at home? Two clicks.

Configure at least email. Add SMS or WhatsApp if you will notify people who do not live in their inbox — field staff, customers, drivers.

For each notification type: switch it on or off, pick the channels, and choose the recipients — named people, whole roles, or whole departments.

Address roles, not people. "Warehouse Manager" survives the person changing; a named recipient means the alerts stop the day they leave.

Rewrite the title and body of any notification in Arabic and English. Useful when the default is technically right but does not sound like your organisation.

Every image, video and document in the system, with what it is attached to. Search, filter by type, and remove what is no longer needed.

Keep files on the server, or point storage at cloud storage. Set the maximum upload size and which file types are accepted.

Generate a share link. Anyone with the link can view that one file without an account — and you can revoke it later.

Who created, edited or deleted what, when, and from which address — with the before and after values of each changed field. Filter by person, by record type or by date.

Publish an announcement to everyone, to particular roles, or to particular branches — a holiday, a policy change, planned downtime.

Search for any label and override it. If your organisation says "client" rather than "customer", or uses a particular Arabic term, change it once and it changes everywhere.

Take a backup on demand — always before a major change — and download it. Past backups are listed with their date and size.

One page covering the application, security posture, PHP, extensions, filesystem, database, queue, scheduler, cache and logs — each check green, amber or red with what to do about it.

See what is installed and what your licence entitles you to, enable or disable a module, and apply an available update.

Every recurring job — reminders, digests, imports, cleanups — with its frequency and when it last ran. A task that has never run is the usual reason a nightly email stopped arriving.