You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi All, Not sure if this is a possiblity or options somewhere in the system already
Question: We want to hide the Kiosk Clock on (Non Global) Activity from staff.
The reason for requesting this option or feature is because we do not want to give staff the ability to stop that time clock activity from their desks or workstations for a number of reasons. Giving our staff the ability to stop their clock on activity either intensionally or by accident makes tracking staff times and days for pay a little difficult for our HR Deparment.
Things we have tried:
We have tried to make this TimeTrack non global activity Hidden (Using the Not Visible option on the activity itself) but then if we do this, you are unable to clock onto Kiosk mode using this activity - Comes up with an error saying we do not have permsision to start this activity. The moment we make it visible again, you can clock on to the kiosk as per normal.
The Kimai system does absoluteley everything else we require, its just this one little pain point we are trying to get past. If there is any advice we are welcome to it and of course, your support is much appreciated.
Describe the solution you'd like
The ability to hide that timeclock (kiosk) entry from staff so they cannot stop it either intensionally or by accident during the day from their workstations logged into their Kimai portal. The only way staff can stop that particular entry is by swiping their barcode etc at the Kiosk upon exiting the building.
Describe alternatives you've considered
We have considered setting up x 2 user accounts for each staff member as a workaround for this issue
One for Clocking On and Clocking off each day at the Kiosk and one seperate account for timesheet entries.
Example: 1.Adam_KioskClock 2. Adam_Timesheet
By Doing this, the Timesheet user cannot accidently or intensionally stop their Clock On Timesheet Entry.
Screenshots
Kiosk Mode Settings
User Mapped to Non Global Time Clock Activity
Sign in at the kiosk when activity is set to visible
We can see this entry in his timesheet –
This is where the problem lay for us:
We do not want staff to be able to stop this entry from their portal – We think they nay do this by accident by hitting the stop button highlighted below inadvertently from their desks while logged into their Kimai portals.
Timesheet Entry for Kiosk Clock On Activity we want to hide -
If we try to make this TimeClock Acitity (Not Visible) – We get the below error signing in at the kiosk
The text was updated successfully, but these errors were encountered:
For now, you can only create two accounts per user: one for attendance times and one for billable hours.
The other option that could be added via the Kiosk plugin (as new feature request) would be a config setting, which disables any manual interaction with records of a Kiosk activity.
Thankyou for the feedback. That sounds fine, we will do x 2 accounts for now which gets us around the issue.
Absolutely yes, that would be an amazing feature if it could be added to the Kiosk Plugin then we can just have it all tied to the one user account per staff member-
We have been testing the demo version and setup a hosted version on premise which we have been using for a Pilot program at the moment (Proof of Concept) for our business. We will likely purchase the kiosk plugin and custom fields plugin in the coming weeks. :)
Describe the problem
Hi All, Not sure if this is a possiblity or options somewhere in the system already
Question: We want to hide the Kiosk Clock on (Non Global) Activity from staff.
The reason for requesting this option or feature is because we do not want to give staff the ability to stop that time clock activity from their desks or workstations for a number of reasons. Giving our staff the ability to stop their clock on activity either intensionally or by accident makes tracking staff times and days for pay a little difficult for our HR Deparment.
Things we have tried:
We have tried to make this TimeTrack non global activity Hidden (Using the Not Visible option on the activity itself) but then if we do this, you are unable to clock onto Kiosk mode using this activity - Comes up with an error saying we do not have permsision to start this activity. The moment we make it visible again, you can clock on to the kiosk as per normal.
The Kimai system does absoluteley everything else we require, its just this one little pain point we are trying to get past. If there is any advice we are welcome to it and of course, your support is much appreciated.
Describe the solution you'd like
The ability to hide that timeclock (kiosk) entry from staff so they cannot stop it either intensionally or by accident during the day from their workstations logged into their Kimai portal. The only way staff can stop that particular entry is by swiping their barcode etc at the Kiosk upon exiting the building.
Describe alternatives you've considered
We have considered setting up x 2 user accounts for each staff member as a workaround for this issue
One for Clocking On and Clocking off each day at the Kiosk and one seperate account for timesheet entries.
Example: 1.Adam_KioskClock 2. Adam_Timesheet
By Doing this, the Timesheet user cannot accidently or intensionally stop their Clock On Timesheet Entry.
Screenshots
Kiosk Mode Settings
User Mapped to Non Global Time Clock Activity
Sign in at the kiosk when activity is set to visible
We can see this entry in his timesheet –
This is where the problem lay for us:
We do not want staff to be able to stop this entry from their portal – We think they nay do this by accident by hitting the stop button highlighted below inadvertently from their desks while logged into their Kimai portals.
Timesheet Entry for Kiosk Clock On Activity we want to hide -
If we try to make this TimeClock Acitity (Not Visible) – We get the below error signing in at the kiosk
The text was updated successfully, but these errors were encountered: