👤 User Management

The User Management page centralizes everything related to the identities working in the system: creating and editing accounts, permissions, store assignments, activation/deactivation for work, and bulk user import. From here you ensure that those who need to work – can log in and scan, and those who shouldn't – won't see stores/actions that haven't been assigned to them.

🏁 How to Access

• On phone: ☰ at the top right → Users.
• On computer: Hover over the menu on the left → Users.

🧭 What You See at the Top – "Fixed Business Employee Password"

At the top of the page the business's fixed employee code is displayed. Regular employees log in with:

• Their phone number + the fixed code. Manager users log in with a personal password (defined for the user themselves).

💡 Recommendation: Share the fixed code only with employees who actually count.

✨ Top Area – Main Actions

• ➕ Create New Employee Account (green button): Manual creation of a single user.
• 📥 Import Users (gray button): Quick loading – pulling all users from an external system (if integration is configured).

🗂️ The Table – Key Fields

• User Nickname – the name that will appear in reports ("who counted").
• Phone – for login – the user's login identifier.
• Password – for login – for a regular employee the business's fixed code is shown; for a manager – a personal password.
• Permissions – user role (see details below).
• Recently Active? – flag that the user was connected and performed scanning actions in the last 10 minutes.
• Edit User Account – button that opens a full settings dialog.
• (For main managers there is also a Reset Main User Password button).

👑 System Roles (Permissions)

Role names may vary between organizations; the principle is the same.

• Company Manager / System Admin Can see all stores, configure users, edit catalog, set up/merge locations, perform summary exports and dangerous deletions.
• Branch Manager Access only to the stores assigned to them. Can manage counts in the store, view reports, mark locations as completed, export summaries for their stores.
• Employee/Counter Scans and performs counting in the app. Sees only the stores assigned to them; no management permissions.

🔐 Important: Not every user has access to every store. Assignment is per user. This ensures separation between teams and stores.

🧾 User Creation/Edit Screen – What to Fill and What It Does

Whether clicking Create New Employee Account or Open Employee Details Edit Dialog, the same convenient dialog opens that centralizes all user settings. Here's how it's structured:

👤 Basic Details

• Employee Full Name – the name that will appear in reports ("counter").
• Phone – for login – the mobile number the employee will use to log in. 💡 Changing the number here changes the employee's login method – no need to create a new user.

🔐 User Permissions (Access Level)

A dropdown menu that defines the user's access level:

• Employee – Counting Permissions Only For counters. They see only the stores assigned to them, and generally without access to management settings.
• Sub-Manager – Management and Control Permissions For store/team lead. Gets access to relevant management screens (e.g. locations/export), still limited to their assigned stores.
• Inactive User – Cannot Log into the System Blocks login and use, without deleting history. ✅ Recommended to deactivate rather than delete – past reports are preserved with user association.

🧰 Specific Permission Toggles

Toggles that extend/restrict specific capabilities:

• Cost Price View Permission
  • On: The user can see cost price data if entered in the system.
  • Off: Cost prices will not appear for them at all.
• Add and Edit Items from Catalog Permission
  • On: Can add/update catalog items.
  • Off: Cannot change the catalog.
• Delete Items from Catalog Permission
  • On: Can delete catalog items.
  • Off: Deletion is blocked (recommended to leave off except for managers).
• View ERP Quantity Permission
  • On: The user will see the "Quantity by ERP" column in the count page and reports (existing balances imported from the external system).
  • Off: ERP quantity column is hidden (useful when you don't want the counter influenced by existing ERP data).
• Full Order Management Access (orders module only)
  • On: The user receives manager-level capabilities for the Orders Management page only – they can create new orders, edit existing ones, run auto-assign, and assign orders to other employees, even though their general role is "Employee". The user will not gain access to other management areas (catalog, users, branches, etc.).
  • Off: The user will only see orders personally assigned to them, just like a regular picker.
  • 💡 Ideal for an operations manager / shipping manager – someone who runs the full order lifecycle but shouldn't be exposed to cost prices, user management, or sensitive settings.
  • 🏢 Branch view: An employee with this permission sees in the orders branch picker only the branches authorized for them (as defined in the branch list further down), not the full company list.

💡 Recommended: Give access to cost and catalog only to managers/team leads. For employees – keep minimum permissions.

🏢 Permitted Stores – Who Has Access to Where?

The user will see and work only in the stores you mark here.

• Search/multi-select stores from the list.
• Shortcut buttons: Grant Access to All Stores / Remove Access from All Stores.
• If no store is assigned – the employee won't see any stores and won't be able to work.

🔎 Reminder: Store permissions are per user. This is the security mechanism that prevents cross-store exposure.

💾 Save and Close

At the bottom of the dialog: Save/Create Employee and Close. Saving is immediate, and the permissions/stores set take effect at that moment.

🔁 Password Reset

For a Regular Employee

In each employee's row there is a Reset Password button inside the details edit dialog. Clicking it allows setting a new password for that employee. Useful when an employee forgot their password and the regular "forgot password" process can't be used.

For Main Manager

In the main manager user's row you'll see Reset Main User Password. Clicking it sets a new password for the manager (does not affect the employees' fixed code).

🔒 Soft Delete

When putting a user into "Inactive" status, the user is not deleted from the system but deactivated:

• They won't be able to log in and perform counts.
• Their history (all scans they performed) is preserved and associated with their name in reports.
• Can be reactivated at any time by changing the permission back to "Employee" or "Sub-Manager".

🔐 Recommended: Never delete a user who has performed counts in the past. Prefer to deactivate (set to "Inactive") to maintain the integrity of historical reports.

📋 Bulk Permissions Update

Using the "Bulk Permissions Update" button (found at the top of the management page) you can update a specific permission for all company employees at once:

• Select the permission to update (e.g. cost view permission, access to a new store).
• Select the action: Enable / Disable.
• Click Confirm – all company users will be updated immediately.

Useful when adding a new store and wanting to grant all employees access to it, or when changing a global permissions policy.

✅ Recommended Processes (Best Practices)

1. Assign stores before starting work Verify every employee who is going to Store X has permission for Store X – otherwise they simply won't see it.
2. Cyclical management of "Active to Work?" Temporary employees? Activate at the start of the project, deactivate at the end. History remains – access is blocked.
3. Consistent names The username will appear in reports. Uniformity (first name + last name) makes productivity management easier.

🧪 Live Examples

• External contractor for a counting project Create "employee" users with the relevant stores only; mark as active. At project end – remove the mark.
• New branch manager in a chain Add user as "sub-manager", assign only their stores. They can export summaries, manage locations and lead counts—but won't see other stores.
• Employee phone number change Edit the "Phone – for login" field. No need to create a new user; history is preserved.