You see, we have this requirement. We have a lot of Android devices out in the field, and most are used by contract employees (they aren’t full-time workers). They need to log in to our app in the field, but we don’t want to constantly create custom logins for these users just to delete them later on. The worst part is having to contact them individually to give them their credentials, it’s a hassle and takes too much manpower.
A workaround we found was using the Deploy file action. What we do is create a set number of available logins, put everything into a file, and deploy that file across the device group. When the workers get their devices, they can open the file on their phone and look up their Worker ID (each worker gets a reusable ID when they register) to get their credentials. These credentials are only valid for that specific day and for specific hours, so after that, access is denied.
We have been doing this manually, but now we are expanding to two shifts. Even though we have workers for both shifts, I am the only IT admin handling this. The first shift isn’t an issue, but after it ends and the new workers come in to get their devices, I need to push these credential files again during my off-hours. Is there a workaround for this that can help me out? I know it’s a lot to ask!
14 Views
