I've noticed that when you enable Web Clock, it is then selected as the default option for new employees. When you enable Mobile, however, you always need to switch it on manually. I understand that making mobile punching the default option could create issues, however all of our clients are configured to use Mobile for Time Card Approvals and time off requests. We could avoid calls from our clients if the system would give all employees mobile access by default, versus needing to switch on access for new hires
Guest
Hi Bill,
I think it makes a ton of sense to have the mobile application turned on for all employees by default, with no punching capability. We have already taken that approach internally, as we include the mobile application access in our standard pricing to our clients and we want to encourage all employees to use the mobile application for Time Off Requests, and Timecard Review and approval. I can think of almost no reason why a client would not want an employee to have access to the mobile application, assuming the employee cannot punch on it unless they are given access.
That said, I agree with Premier Payroll in that a Processing Rule that sets the Default Mobile Settings for all new employees would be a big improvement for the clients that use the Mobile Application for punching across the majority of their employees. It seems like a (relatively) simple addition that would make a significant impact to those clients.
If I can provide any other information or feedback about this idea, please let me know.
Thank you,
Greg Nasso
Complete Payroll
Attachments Open full size
Thanks for the feedback! We are considering turning on mobile access at the client level and at the enabled at the employee level with punches and gps off. We will review internally.
Attachments Open full size
This is an issue for our clients that use the Mobile features as well. Generally, if the mobile option is enabled, they want it enabled for employees by default. It seems more prudent to let the client choose which employees to restrict.
I find the situation further compounded by Resellers that employ an API developed by their payroll provider to streamline export of employee data / import into TW/TWP. If all other employee data can be transferred through the API, only having to go into Employee Setup to enable mobile features reduces the value and scope of the API's usefulness.
To keep all users, those who are happy with the current process and those like us who see it as an impede, perhaps this can be a Processing Rule, "MobileDefaults," that lets you set Yes/No values for each mobile permission. Yes = box checked, No = box unchecked in Employee Setup for future new-hires.
GREAT IDEA, Greg!
Attachments Open full size