Administrators and Power Users can define remote clocking modes to determine if, how, and from where employees report their work when they are not at a company location. These modes can be set company-wide or customized for individual users based on their roles and company policies.
Generally, the remote clocking mode in Fluida should reflect the employee's labor contract. However, depending on which features are active, certain settings may be more effective.
Company Policy | Remote Clocking Mode |
Remote work is not allowed | |
Remote work is allowed, but tracking isn't necessary | |
Remote work is only allowed in approved locations | |
Remote work is allowed from any location |
Remote work is not allowed
If an employee is not authorized to work remotely, choose Not allowed / Not required.
If you use the Attendance Management feature, you can set "Remote Work" to Not allowed in the user's settings. Fluida will then automatically set their remote clocking mode to Not allowed / Not required, and it can no longer be customized.
Employees don't need to clock in while working remotely
If you don't need to track exact hours worked off-site, select Not allowed / Not required.
With this mode, users working outside a company office do not need to clock in to confirm their presence. If their attendance calendar already shows they are off-site (via a "Change Location" or a "Remote Work" request), the system will mark them as present without expecting any clocking data.
💡 Fluida does not strictly block manual clock-ins for remote locations; see the Q&A section for more details.
💡 If a user does not have an assigned shift (e.g., the company doesn't use the Attendance Management feature), Fluida cannot calculate total hours worked. In this case, consider a different remote mode.
Remote work is limited to specific enabled areas
If an employee is only authorized to work from specific locations—such as their home, a second residence, or a temporary vacation spot—select Enabled areas only (GPS). You must then create Personal Areas by specifying the address and allowed radius for each.
In this mode, the user must clock in using their smartphone. Fluida uses the device's GPS to verify and certify that the person is at an authorized work location.
💡 To protect privacy, the entry will simply be recorded as "Remote," without disclosing the specific personal area used.
Remote work is allowed from anywhere
If an employee works from changing locations and you don't need to verify their position, select From anywhere (no validation).
In this mode, users report their work by manually entering a clock-in for the "Remote" location. Fluida does not verify the location via GPS or Bluetooth, allowing entries to be made from any computer or mobile device.
Troubleshooting
Why can users still clock in remotely if their mode is "Not allowed / Not required"?
To ensure employees can always report their work in case of configuration errors or emergencies, Fluida never strictly blocks manual entries for unauthorized locations.
This applies even to users set to Not allowed / Not required. When adding or editing an entry, they will see "Remote" listed under unauthorized locations, but they can still select it. If they do, the manager responsible for approving forced clock-ins will be notified and can choose to approve or reject the entry based on company policy.
💡 If a user is authorized to self-approve their forced entries, the company will not receive a notification when they clock in at unauthorized locations.
