Several companies, one database
Each company has its own registration data and its own structure, while customers and items are shared — no need to create them several times. Operators get access to selected companies and switch between them in the header, without signing out.
An organisational structure familiar from Comarch ERP XL
Modelled on the Comarch ERP XL structure, so its users will find their way quickly — though it is not a copy. A tree of branches, departments and centres for each company. Select a node to see its sub-nodes, operators and employees — for the whole subtree too. A node in use is archived rather than deleted.
An employee is not always a user
The employee register (position, centre, employment period, contact details) is separate from operator accounts. A warehouse worker needn't have a login, and a warehouse workstation can have an account with no person attached.
A password or a Windows account
Password sign-in with a complexity policy, a forced change at first sign-in and a lockout after several failed attempts — or a Windows domain account with no separate password. You can also allow Windows sign-in only.
Roles and per-operator exceptions
You grant permissions through roles (e.g. Sales, Accounting, Read only). When one person needs a little more or less, add an exception on their record — grant or revoke a single right — without creating a new role. Without edit rights a record opens read only, and menu items with no access simply aren't shown.
You can tell where every right comes from
The operator record has an effective-permissions table. Each right shows its source — a role, an exception, a substitution or system administrator — and whether it has been revoked.
Holiday cover
For a set period the substitute gets the permissions of the person they cover for, optionally with access to that person's companies. The substitution expires on its own and can be revoked early. It is not transitive — a substitute's substitute gets nothing.
Sessions and a sign-in log
A list of the operator's active sessions with browser, IP address and last activity — with “Sign out” for one session or all of them. The sign-in log records successful and failed attempts, with the reason for refusal.
View as operator
An administrator can open the application with a chosen operator's permissions and see exactly what they see — read only, with a clear bar at the top. The start and end of each view are logged.