Okay, I think I have a better idea. This is on a Mac?
It sounds like the WD drive is just a NAS that is presenting its drives over a network interface (CIFS/SMB probably). If that is the case you should be able to mount that drive to your computer persistently, including providing the credentials for access. At that point any software that you have running, including odrive, will have access to the drive without requiring additional authentication.
Now, there may be a couple of options at this point:
It sounds like you may have odrive auto-downloading files from the #Returns slack channel (after linking Slack). Is that correct? If so, how are you planning on pushing the files into the other location? Will you be using an automated script, or something similar? If that is the case then odrive wouldn’t actually need access to that network drive, only the script would.
Alternatively I could see something like this being setup:
- Map the WD drive persistently (This could be a bit tricky, so we’ll need to understand the environment more, but it is a requirement in almost all scenarios anyway)
- Set the odrive auto-download limit to always
- Create a Pro Sync folder on the mounted WD drive and map that to the #Returns slack channel
- Let odrive do its thing