Create accounts for repair technicians, shop managers and front-desk staff on Fixh IT, with a user level and granular permissions per shop and per module (repairs, warehouse, POS, documents).
In a growing smartphone and PC repair shop, the owner can no longer handle every repair, till sale or customer handover alone: you need repair technicians, front-desk staff and shop managers with different levels of access to the software. On Fixh IT this is managed from Company > Staff management > Users, where every employee gets their own account with a user level and specific permissions on every module and every shop, without ever having to share the owner's credentials.
Why it matters for a repair shop
A repair shop handles sensitive data every day: spare part purchase costs, repair margins, cash takings, customer data. Giving every employee the same unrestricted access as the owner exposes the business to unnecessary mistakes and risks: a repair technician does not necessarily need to see a shop's financial reports, just as front-desk staff should not be able to edit the price list. Granular permission management lets you match exactly what each person can see and do in the software to their real role in the lab or on the shop floor, cutting down on operational errors and keeping sensitive data under control even as the repair center grows and hires new staff.
In practice
When you create a new staff user from Company > Staff management, you enter first name, last name, email, one or two phone numbers, the interface language and a password the employee will use to log in: the account is created and active immediately, no email confirmation is required. You also assign a user level (uLevel) from 1 to 9: 1 is the repair technician, 2 the shop manager, 3 the company admin, while levels 7, 8 and 9 are reserved for supervisors, super admins and the owner. An admin can only create employees with a level equal to or lower than their own (never higher), so a shop manager can never promote a colleague to a more powerful role than their own.
The most important part is the granular permissions: from every employee's permissions tab you can configure, shop by shop and module by module (Shop, Lab/Repairs, Warehouse, POS, Documents, Customers, Marketplace, Hub), four separate actions: view, create, edit and delete. This combination allows very precise configurations: a technician can have full access to the Repairs module of their shop but no access to the Warehouse, or a manager can handle Repairs and POS across two different shops but not touch fiscal Documents. Only levels 1 (technician) and 2 (manager) actually respect these granular permissions: higher administrative levels (3, 7, 8, 9) always have full access to every shop and module, with nothing to configure, just like the company owner.
Every employee also has a default shop, the one they are automatically placed in when logging in, which you can change at any time, and can be deactivated instead of deleted: deactivating an account means the former employee can no longer log in, but the whole history of repairs, sales and movements they recorded stays intact and linked to their name. You can also block an employee's access to the internal company chat, stating a reason, without touching their other permissions. The number of employees you can activate still depends on the company's subscription plan: if you reach your plan's limit, you will need to deactivate an existing account or upgrade before adding a new one.
Quick guide
- Go to Company > Staff management > Users.
- Click "Add user" and enter the employee's first name, last name, email, phone and language.
- Set a login password and choose the user level (uLevel) to assign them, no higher than your own.
- Select the employee's default shop.
- Save the user, then open their permissions tab.
- For every shop they need access to, toggle view/create/edit/delete on the individual modules (Repairs, Warehouse, POS, Documents, Customers, etc.).
- Save the permissions: the employee can log in right away with the credentials you gave them.
Real use cases
In a smartphone repair shop with two technicians and one front-desk employee, the owner creates two level-1 accounts for the repair technicians, giving them full access to the shop's Lab/Repairs module but no visibility on the Warehouse or fiscal Documents; for the front-desk employee, they create an account limited to POS and read access to Customers, with no ability to change prices.
In a network with three repair locations, the owner appoints a level-2 manager for each shop with full permissions on Repairs, Warehouse and POS, but only for their own shop: this way each manager runs their own shop independently, without being able to see or edit data from the other shops of the same company.
When a technician leaves the repair center, instead of deleting the account the owner deactivates it from Company > Staff management: repairs already handled by the technician remain visible in the history under their name, useful in case of warranty disputes, but the former employee can no longer log into the software.
Tips and best practices
Apply the principle of least privilege: give each employee only the modules and actions their role actually needs, adding more permissions later if a real need arises, rather than starting with full access. Review assigned permissions periodically, especially when an employee changes role or shop. Use levels 1 and 2 for operational staff (technicians and shop managers) and reserve the higher administrative levels for a few trusted people, since they grant full, unconditional access to every shop.
Common mistakes to avoid
A frequent mistake is creating every user with a high administrative level "for convenience", to avoid configuring permissions: this exposes sensitive data from every shop to people who should only see their own. Another mistake is deleting the account of an employee who leaves the company instead of deactivating it, losing traceability of the repairs they handled. Finally, forgetting to restrict a technician's default shop and permissions can accidentally let them see repair or customer data from another shop in the network.
Frequently asked questions
Does the employee receive an invitation email to activate the account? No, the account is created already active from Company > Staff management: you set the initial password yourself and share it with the employee along with their login email.
Can I give an employee access to several shops at once? Yes, the permissions tab lets you configure view/create/edit/delete for every module on each company shop you want to give them access to.
What is the difference between levels 1-2 and levels 7-9? Levels 1 (technician) and 2 (manager) respect the granular permissions configured shop by shop and module by module; levels 3, 7, 8 and 9 always have full access to every shop and module, like the owner.
Can I change an employee's role and permissions later? Yes, you can update their uLevel, default shop and granular permissions at any time from the same section.
What happens if I reach the maximum number of users allowed by my plan? You will not be able to create new accounts until you deactivate an existing user or upgrade your subscription plan.
Can I block only an employee's internal chat without touching their other permissions? Yes, you can disable a single employee's access to the company chat with a stated reason, independently from their permissions on other modules.
