Nama Mobile App — Overview, Navigation & Settings
Nama Mobile is the mobile front end for the Nama ERP system. It puts a connected endpoint in the hands of the employee, the sales rep, the warehouse keeper and the maintenance technician — all talking to the same ERP server the back-office team uses. From the phone they can clock in, issue invoices, count stock and follow up customer visits.
The big picture before we start
The app works offline-first: when you log in it downloads a copy of the data it needs (customers, items, currencies, vacation types… depending on the licensed modules) and stores it locally on the device, then syncs documents back to the server whenever a connection is available. That means a field rep can keep working even on a weak network.
The app supports Arabic and English, and ships under different brands (white labeling) for Nama's various customers — such as NAMASOFT, SoftVision, Exceed, Capital and Cleopatra. Each build carries its own name and icon but shares the same features described in this guide.
What this guide covers
We split the app documentation into pages by the kind of work involved:
- This page — logging in, the home screen, navigating between modules, and settings (language, printer, sync).
- Employee Self-Service — Attendance & Leaves — electronic attendance, vacations, permissions, missions, loans and HR documents.
- Sales, Inventory & Item Inquiry — sales documents, stock transfers, electronic stock taking and item inquiry.
- Customer Service, Delivery & Receipts — customer visits, maintenance, questionnaires, delivery vouchers and electronic receipts.
- Mobile QR Integrator Guide — responding to scanned QR codes to create/update entities.
Logging in and connecting to the server
The first time you open the app the login screen appears, and you need:
- Server URL — the link to your organization's ERP server. You can type it in, or scan a QR code that holds the link to save the trouble.
- Username and password — the same Nama user credentials.
Advanced login options
- NTLM/HTTP authentication: for environments that use Windows authentication, you can enable separate NTLM credentials.
- Skip SSL verification: for development environments or servers with self-signed certificates only.
After a successful login the app fetches the user settings and licensed modules from the server and builds the menus and shortcuts accordingly — so what each user sees differs by their permissions and the modules enabled for their organization.
The password is used only for that first login. The server then gives the phone an API key of the user's own — an API Credentials record it creates automatically the first time — and the app signs every later request with that key instead. See The API Credentials record each app user gets.
Biometric login
The app can ask for a fingerprint or face scan on every launch as an extra layer of protection. It is on by default, and the administrator can switch it off with Disable Biometric Login In Mobile in the Mobile Apps Configurations screen.
The home screen
The home screen is the employee's daily launch point. At the top it shows the user's name, employee number and the notifications bell, then come the cards:
- Check-in card — a quick "Check In / Check Out" button without opening the payroll menu.
- Information panel — a summary of the current workday (today's hours, whether you've checked in, days attended this month).
- Monthly attendance — colored cards summarizing the month: actual attendance, required hours, lateness, overtime, permission hours, and days of holidays, vacations, missions and absence.
Below the summary are quick shortcuts for the most frequent actions, such as requesting a vacation or a permission. The administrator can replace this whole home page with a grid of shortcut cards of their own — see Customizing the home screen and the menu below.
The bottom navigation bar
The bottom of the screen has five fixed tabs. Their number and order are the same for every user; what the administrator can change is what sits behind the Home, Menu and More tabs.
| Tab | Purpose |
|---|---|
| Home | The home screen and attendance panel |
| Menu | All modules and documents available to the user |
| Approvals | Documents awaiting the user's approval (with a counter) |
| Chats | Internal messaging (with an unread counter) |
| More | Settings and utilities |
The menu and module groups
The Menu tab shows the licensed modules as grouped cards, with a search box for quick access to any screen.
The groups shown change with your organization's license and your permissions; examples include Accounts, Basics, Human Resources, Payroll, Customer Service, Shipping, Sales and Warehouse Management. Opening any group reveals its detailed screens:
The Basics group, for example, gathers the shared screens: approvals, notifications, the Dashboard, customer/currency/item data, reports, plus the note types (remark, detailed remark, meeting remark).
The menu order is customizable
The administrator can completely redefine the structure of menus and groups on the server side (see Customizing the home screen and the menu), so your order may differ from the screenshots.
Approvals, notifications and messages
- Approvals: the list of documents awaiting your approval (vacations, permissions, requests…). You can review each document's summary and approve or reject it from the device directly.
- Notifications (the bell at the top): a list of alerts from the system, with the ability to open the document linked to an alert directly, mark all as read, or delete them.
- Messages: internal chat between system users supporting text, images, video and voice messages, working in real time over a persistent connection to the server.
More and Settings
The More tab gathers settings and utilities:
- Settings — which may be protected by an administrator PIN if the organization enables it.
- Create Device ID document — to register the device fingerprint when linking it to the system.
- Additional items defined by the administrator on the server side.
The Settings screen
Settings are divided into several tabs:
General settings
- Language: Arabic or English.
- Server URL, email and device code.
Printer settings — the app supports a wide range of thermal printers including Bluetooth printers, Sunmi devices, C75 and others. You can set:
- Printer type, paper width (mm or pixels) and height.
- Paper size (80/72/58 mm) and the print command (ESC/TSC/CPCL) depending on the printer type.
- The wait time before printing.
On a Sunmi handheld (such as the V2s) the device's built-in printer prints invoices, receipt vouchers and electronic payment vouchers straight from the app.
Other settings
- Save server logs: to enable logging server calls and review them later when diagnosing an issue.
- Fetch logo: to download the company logo used in printing documents.
- Reload app data: to force the app to re-sync all settings and data from the server.
Changing the password and admin PIN
From the profile screen the user can change their password, and the administrator can change the Admin PIN that protects access to the Settings screen.
The setup QR code from Qr Info in the web interface's user menu carries the PIN only when an administrator opens it. A regular user's QR leaves the phone's PIN unchanged, and a new phone set up from it has no PIN until an administrator scans their own QR on it or sets the PIN here.
Customizing the home screen and the menu
Out of the box every user gets the same home page (the attendance card and the monthly summary) and the same menu, built from the organization's licensed modules. A delivery driver does not need the attendance dashboard, though, and a sales rep would rather open straight on a new sales order. Two screens in the ERP let the administrator reshape what each user sees, without touching the phones:
- Mobile App Menu Definition — decides which groups and screens appear in the Menu and More tabs, and which shortcut grid replaces the home page.
- Mobile App Shortcut — a set of shortcut cards (icon, colours, and the screen each card opens).
Both are under Basic → Mobile Apps.
Which menu definition a user gets
The app picks the menu definition in this order:
- The Mobile App Menu Definition set on the user's own record, if there is one.
- Otherwise, the menu definition that has System Default Menu ticked.
- Otherwise, the built-in menu.
So a typical setup is one definition marked as the system default for everyone, plus a few special ones (drivers, sales reps) assigned directly on those users. The user sees the change after logging in again or using Reload app data.
Building a menu definition
The quickest start is the Create Mobile App Default Menu button on a new record: it fills both grids with the standard layout — the groups Basics, Accounting, Payroll, Shipments, CRM, Sales, Warehouse Management and so on, each with its usual screens — which you can then trim or rearrange.
The record has two grids:
Groups — one line per card on the Menu tab:
| Column | Purpose |
|---|---|
| Code | A short code that the items grid refers to |
| Arabic / English | The group title in each language |
| Group Icon Name | The card's icon, chosen from the suggested list |
Target Items — one line per screen:
| Column | Purpose |
|---|---|
| Group Code | The group the screen belongs to. Leave it empty to put the item in the More tab instead of the Menu tab |
| Link Target | The app screen to open (vacation request, sales order, customer visit, settings, log out…) |
| App Shortcut | Required when the target is Home Shortcut: the shortcut set to open |
| App Home Replacement | Makes this screen the user's home page — see below |
Screens from modules the organization is not licensed for stay hidden, even when they are listed here.
The header has two more options:
- Add To Default Menu — when ticked, your groups are added to the built-in menu and your More items are added after the built-in ones. When it is not ticked, your definition replaces the built-in menu and More tab entirely, so remember to include items such as Settings and Log out.
- Home Shortcuts — see the next section.
Replacing the home page with shortcut cards
To give a user a home page made of big shortcut cards, first create a Mobile App Shortcut record. Each line of its grid is one card:
| Column | Purpose |
|---|---|
| Target Item | The screen the card opens; it also gives the card its title |
| Shortcut Type | Create View opens a new, empty document of that kind. List View opens the list of existing records |
| Group Icon Name | The card's icon, using the same icon names as the menu groups |
| Icon Color / Background Color | The card's colours |
Then pick that record in the Home Shortcuts field of the menu definition. From then on the user's Home tab shows only this grid of cards; the attendance card and the monthly summary no longer appear.
A shortcut set can also sit in the menu rather than on the home page: add a Target Items line with the target Home Shortcut and pick the shortcut set in its App Shortcut column. Without a group code it appears as a Shortcut card on the Menu tab that opens the grid of cards.
Opening the app on a different screen
Tick App Home Replacement on one Target Items line to make that screen the user's home: whenever the app would go back to the home page, it opens this screen instead — useful for a driver who should always land on their delivery tasks. Only one line per definition may carry the option, and it takes effect only on a line that has a Group Code.
Syncing and working offline
On login — or when you use Reload app data — the app fetches the reference data and stores it locally. Documents created in the field can be saved as drafts on the device and then synced to the server later, depending on the organization's settings. When settings change on the server the app can be notified in real time and reload the settings automatically.
Server settings that control the app's behavior
Most of the app's behavior is configured centrally from the Mobile Apps Configurations screen in the ERP (Basic → Mobile Apps, last item), not from the phone. This screen is the administrator's reference for everything related to the app, including for example:
- Specifying the books allowed for each document type (attendance, vacations, permissions, stock taking, receipts, delivery…).
- Controlling biometric login, showing/hiding the save-as-draft option, and the number of decimal places of line totals.
- Setting the criteria that determine which customers or items are allowed to be sent to the app.
- Authoring the print templates for documents and receipts.
- Restricting the creation of some documents (attendance, vacations, stock taking, receipts) to the app only, or allowing their editing for authorized users only.
Every option of that screen, tab by tab, is explained in Mobile Apps Configurations — option reference.
Your organization's license also determines which modules appear in the app at all (Human Resources, Sales, Maintenance, Warehouse Management/WMS, Stock Taking, Delivery…); if a module is not licensed, its screens will not appear in the menu.
The other administrator screens under Basic → Mobile Apps — screen layouts, card titles, label wording, lookup filters, the mobile dashboard and binding users to their phones — are mapped in Administering Nama Mobile from the ERP.