Every company and user under one account
Add each subsidiary with its own currency, fiscal year and document numbers, then give every user a role that decides what they can see, enter, change and approve.
How an account is set up
Add your subsidiaries
Each one has its own code, currency, country, tax number, fiscal year start, time zone and logo. Currency and country are fixed once saved.
Control and safeguards
Read-only without the grant
A role that only views an area sees its records read-only, and the server refuses the change anyway.
Sign-in protection
Five wrong passwords in ten minutes lock the account for fifteen. A new sign-in ends the earlier session, and a reused session token ends it outright.
Two-step sign-in
Require an authenticator-app code after the password for any office user, with backup codes for a lost phone and a reset by the admin.
Audit trail
Every record shows who created it and who changed it last. Changes to users, roles, permissions and numbering are logged with who, when, from which address, and the record before and after.
Archive and restore
Deleting a user, role or master record archives it, and restore brings it back. A subsidiary that still holds warehouses or customers cannot be archived.
Edit conflicts caught
If someone saved the record after you opened it, your save is refused with a prompt to refresh, so neither edit is lost without notice.
Features in this module
- Roles that decide who does whatFive starter roles, your own custom roles, and a level per area from View to Approve.
- Several companies, one accountEach subsidiary keeps its own currency, fiscal year, time zone and numbering.
- Document numbers in your formatBuild document numbers from the subsidiary code, year, fiscal year, month and user’s initials, preview sample numbers, and keep each subsidiary’s sequences apart.
- Who changed what, and whenChanges to users, roles, permissions and numbering are logged with who, when, from where, and the record before and after.
- Sign-in that resists guessingAccounts lock after repeated wrong passwords, a stolen session token ends the session, office users can need a second step, and reps’ devices can be signed out.
Questions buyers ask about companies and users
Is each company’s data kept apart?
Yes. Every read is filtered to your account, and records that belong to a subsidiary are filtered to the one the user works in. A user tied to one subsidiary never sees another’s.
Can we cut someone’s access straight away?
Yes. Deactivating a user, tying them to one subsidiary or switching on two-step sign-in ends their open sessions at once. For a field rep, the office sees the active device and can sign it out.
Can we change the starter roles?
No. The five starter roles stay as shipped. Create your own role, set its level per area and assign it instead.
Is the interface in Arabic?
Yes. Each user switches between Arabic and English from the top bar, and Arabic reads right to left.
How do users hear about things that need them?
A bell in the top bar counts unread notifications, such as an e-invoicing certificate about to expire, and marks them read. Service announcements, such as planned maintenance, show as a banner.
Not in Axon Suite yet
Said here so neither side spends a demo on it.
- Single sign-on with Microsoft, Google or SAML
- IP allow-lists for sign-in
- Password expiry and reuse rules
- Limiting a user to some subsidiaries but not all
- More than one role per user