Thank you for the message.
We have some exciting changes coming over the next few months. We have a new release coming out in the next couple weeks. This release has not changed the Google Drive login requirements. However, the program is planning a future release to add a single sign on feature. This may address the login concerns.
There is a way to set up scanning to a network folder that could then sync to Google Drive. This can be accomplished using the Scan to Shared Folder template app. Create the folder to sync with Google Drive, then create and install the corresponding Scan to Shared folder app at the device.
There aren't any current plans to add phone support for badge-in via NFC for the devices, but this will certainly be added as a feature request for the team.
The only workaround for logging in is using a Scan to Shared Folder set up to sync with Google Drive, as you mentioned.
Please let us know if there are any additional questions.
Is there an update to the Google Drive autheification requirements?
Is there any way to setup scanning to a folder that can be shared to Google Drive?
Can the enduser use their phone's nfc to save the credentials for when they 'badge-in' to the device?
Is there any work around for this issue?
Thank you so much for the suggestion.
I have added your recommendation to our open feature enhancement request.
We appreciate the feedback!
Perhaps too, we could use Properties to set a default domain?
Example: email@example.com could be signed-in with just "john.smith" and the domain would be already set.
Thank you for your reply.
There have been similar requests for this functionality. We have a feature request in the system to cover this capability and will be considering this addition in a future release. Unfortunately, there isn't an outlook for how soon this might be added. If you watch this forum periodically, we will post information when new releases are launched and what those releases contain. If I find additional information regarding this specific topic, I will reply here as well.
Thanks again for your valuable feedback.
That is a really disappointing user experience. We set up a "copiers" Google account in order to allow the copier to authenticate to SMTP in order to send scanned docs to email addresses. I'd like to use the same account to allow end users to scan to the same shared folder on Google Drive without having to enter a password everytime.
Thank you for your message.
The apps do allow designers to save partial user credentials when creating the apps. When the Google Drive apps are being designed in App Studio, there is an option to provide a default login name on the first screen of the wizard. Saving full credentials (password) is not offered at this time. A screen capture of the designer screen is attached.
When the app is being used at the device, users are able to modify the default login, if necessary and then simply provide the password.
I would like to set up both of our copiers so the end user does not need to unter the google drive username and password everytime they want to scan something. Is there a way to make the username and password persistent in the settings of the device?