User roles and access: who can do what
Every platform role on one page: super admin, central staff, company admin and staff, branch in-charge, merchants, warehouse supervisor, courier and visitor, with where each signs in and where access is configured.
Last updated 22 October 2026 · Last verified 22 October 2026
Purpose#
Every account has a type. The type decides where the person signs in, which panel opens and what they may do. This page lists all roles, who creates each one and where access is configured, so you can pick the right guide for your own role.
The roles at a glance#
| Role | Where they work | What they can do |
|---|---|---|
| Super admin | Central panel on the main domain | Runs the platform: companies, plans, finance, shipping companies, coverage areas, warehouses, payment gateways, settings, website content. |
| Central staff | The same central panel | Accounts added under Users & Roles; their role controls the support, Users & Roles, companies, plans, settings and website-content entries. |
| Company admin | Company panel on the company's own subdomain | Runs the company: parcels, merchants, couriers, branches, dispatch, settlements, reports. Only admins also see Delivery pricing, Integrations and API and Payment gateways for your merchants. |
| Company staff | The same company panel | Accounts added under Users & Roles; the role they are given sets their permissions. |
| Branch in-charge | The same company panel | A staff user assigned to a branch; the parcel list shows only that branch's parcels. |
| Merchant of a delivery company | Merchant panel | Creates parcels that go through the company; uses My wallet, Pickup locations, Parcel report and Support. No store connections, API, webhooks, own shipping-company accounts, platform plans, platform wallet top-up or withdrawal, or account statement. |
| Independent merchant | Merchant panel | The same, plus store connections, Webhook and API, My shipping company accounts, Plan and subscription, Account statement and My delivery company (own couriers and dispatch). |
| Warehouse supervisor | Warehouse panel («لوحة المستودع», Arabic in every interface language) | Records stock in and releases parcels at the linked warehouse. |
| Courier | No web panel; a mobile client of the courier API | Sees and updates only the parcels assigned to them. |
| Visitor or recipient | Public pages | Tracks a parcel on the public tracking page, signs up, or ships without an account when the super admin has enabled it. |
Who creates each account and how they sign in#
- Central staff: a super admin adds them on the main domain under Users & Roles → Users. Give these accounts only to people you trust with the platform.
- Company admin: created with the company by the super admin, or by the company on the company sign-up page (confirmed with a one-time code, OTP). Admins add company staff under Users & Roles → Users.
- Merchants: company staff add them, or they sign up on the company's site. Independent merchants sign up on the main domain through the Register as a merchant page or are added by the super admin.
- Couriers: company staff, or an independent merchant for their own company, add them under Couriers and commissions.
- Warehouse supervisors: the super admin creates them in the warehouse administration with a name, mobile number and password.
Everyone uses the same sign-in page: Email or mobile number and Password. A super admin signs in on the main domain only; a company address rejects the account. On the main domain every other account is sent to its own company's domain after a correct password, normally through a one-time link valid for 2 minutes; on a company domain only that company's accounts are accepted. Supervisors land on the warehouse panel, everyone else on the dashboard of their own panel. Couriers sign in from the courier app with their courier ID, mobile number or email and the password. An inactive or unverified account cannot sign in.
Where access is configured#
Create or edit a role
Open Users & Roles → Roles, press + (or edit a role), tick the permissions of each module and save with Save (Save Change when editing). On the main domain the list holds the super-admin permissions (dashboard, companies, plans, users and roles, support, settings, website content); on a company domain it holds the company permissions.
Give the role to a person
Open Users & Roles → Users, add or edit a user and choose the role. Saving copies the role's permissions to the user. To change one person only, open the row menu, choose Permissions, tick the boxes and press Submit. Choosing a Hub on the user form replaces the permissions with a fixed short list.
Check the company owner's permissions
The company's first admin receives the permissions of the plan's modules when the super admin creates or edits the company and whenever its plan is switched or paid for. A company that signed up by itself starts with an empty permission list and an expired subscription until a plan is activated.
Common mistakes#
- Super admin signing in on a company address. It is rejected; use the main domain.
- Expecting a role edit to change current users. It changes only the role; users keep their permissions until saved again or edited under Permissions.
- Adding couriers or merchants from the Users screen. It lists and creates staff accounts only. Use Couriers and commissions and the merchants screens.
- A merchant of a delivery company opening store, API or webhook pages. The links are hidden, and a direct link returns to the dashboard with a warning that begins «حسابك تابع لشركة توصيل» (Arabic in every interface language).
Limits and permissions#
- Account-type rules are enforced on the server. A super admin always passes; any other account must match the account type the page requires, otherwise the request is refused with HTTP 403 (an error page on the web, JSON for the API) and a message listing the allowed roles, and a suspended account gets HTTP 401.
- When your account lacks the permission a staff screen needs, the menu entry is hidden and opening the link directly sends you to the home page without a message (no 403 page).
- Merchants, couriers and warehouse supervisors are not managed through roles; their access follows the account type. A merchant edits their own profile and password from the avatar menu (Profile, Change password). The warehouse panel is for supervisor accounts linked to a warehouse; others get a 403 page.
- A company needs an active subscription, except platform-owned and merchant-owned companies. An independent merchant needs an active merchant plan when the platform has active merchant plans.
- The checks recognise three company staff types (admin, in-charge, hub), but the screens create admin-type accounts only; the in-charge screen assigns an existing admin-type user to a branch.
API
POST /api/v10/deliveryman/login