Users
In short
Who works in the program and what they can do. Three tabs: "Users" (sign-ins, roles, blocking), "Employees and rates" (all workers with position and hourly cost, including those without sign-in) and "What roles can do".
Why it matters
- Give an employee access with the right permissions, and only where they work.
- Close access for someone who leaves, and know mechanics' hourly cost.
Who can
Sign-ins and roles: the administrator only. "Employees and rates": also the branch manager, for the employees of their branch, their hourly cost and the link to a sign-in (only sign-ins of their branch). The administrator and finance roles require sign-in with a second factor (MFA).
How to do it
- Invite. "Invite employee" → full name, login, interface language, role and "Where it applies" (whole installation, the whole company or one branch) → "Create and issue password". Hand over the temporary password in person: the employee changes it at the first sign-in.
- Roles. On the user card, "Assign role" (several roles in different branches are possible) or "Remove role". What each role gives is in "What roles can do".
- Access. "Reset password", "Reset MFA" (new phone), "Lift sign-in pause" after wrong passwords, "Block" / "Unblock".
- "Link by email": instead of a temporary password, the user gets an email link and sets the new password themselves. The link works once for 30 minutes; the current password keeps working until a new one is set, and the second factor does not change. At most once an hour per user. The card needs an email ("Email for the new-password link": an installation-wide administrator changes it; users change their own with their current password). The link lifts the sign-in pause after wrong passwords; blocking or changing the email, password or second factor cancels a link already sent.
- "Main user of the installation": the software vendor can send them such an email at your request (for example, if all administrators forgot their passwords). Set by an installation-wide administrator.
- Employees and rates. "Add employee" → position, hourly cost, branches. "Program access" is optional: an employee can work without signing in (for example, a mechanic on repair orders).
Common messages
- "sign-in paused until …" — many wrong passwords in a row; wait or press "Lift sign-in pause".
- "password change pending" — the employee has not signed in with the temporary password yet.
- "MFA not set up" on a role that requires a second factor — the program asks to set it up at sign-in.
Questions and answers
Can a user be deleted? No, only "Block": sign-in and all open sessions are closed, while their documents and audit log entries remain. "Unblock" restores access with the same roles. The last installation-wide administrator cannot be blocked: "Not allowed: the installation would have no installation-wide administrator left. Assign another one first."
How many wrong passwords are allowed? After 5 failed attempts within 15 minutes, sign-in with that login is paused for up to 15 minutes: "Too many failed attempts. Try again in … min." Second-factor codes are counted the same way, separately; from one IP address, up to 30 failures in 15 minutes. To lift the pause earlier, the administrator presses "Lift sign-in pause".
How do I change my own password? The program has no screen for it: the password is changed at sign-in after "Reset password". The administrator issues a temporary password, and at sign-in the program asks you to choose your own: at least 10 characters and not containing the login. An administrator does not change their own password, second factor or blocking either: another administrator does.
Why was the employee signed out after a role was assigned? The administrator and "Finance / accountant" roles require a second factor: if the employee has not set up MFA yet, their open sessions are ended, and at the next sign-in the program asks them to set up an authenticator app. "Reset password", "Reset MFA" and "Block" also end their open sessions.
Why can't the administrator see an employee in the list? An administrator of one company or branch sees and manages only users whose roles all lie within their scope. If a user has roles in other companies, an installation-wide administrator manages them: "The user has roles outside your scope: an installation-wide administrator manages them." A user without roles is visible only to an installation-wide administrator.
Where next
- "Audit log" — who did what in the program.
- "Companies" — the branches where roles apply.