Local File Sync - why the time limit?
Our team was initially using Workiva for SOX, however we've recently added the Audit Module. When using Local File Sync, the 60-minute limit is causing some issues now, as the Audit team frequently has files open longer than 60 minutes. Why is this limited? Can it be extended? Also, does the time start 60 minutes for each file opened, or if you open a file, then 40 minutes later, open a 2nd file, do you only have 20 minutes now?
I'm just trying to understand the reasoning behind the time limit, and if it can be expanded.
-
Hello Anthony!
Thank you for your feedback. Currently time extensions are not possible but we have had similar requests in the past. I have created a ticket for you to receive updates on this potential feature and let our team know we have another vote for this issue.
3Hello Sheila,
This time limit is still in place. However, I have added you to the request for an extension so our Support team is aware of the impact. You will be updated on any progress/updates moving forward!
1Hi Bill!
Thanks for your question. Sorry for the delay here. After talking with our experts, I did get some info for you. Here goes!
The 60-minute limit exists today for security purposes. Workiva limits the “checkout” time of the file to prevent unintended, or otherwise malicious updates to the file that could flow back into our system. Our engineers are open to the discussion of extending this time, so I'm happy to get you connected with them if interested. And to answer your question, yes, each file gets 60 minutes from the time it was originally downloaded onto the user’s machine.As a workaround for Audit folks is to download the Original attachment, work on it for as long as they'd like, then use the Replace function to re-upload it when they're done.Hopefully that helps some. Do let me know what questions you have and if you need anything else. Thanks again for the questions and happy Friday!0Thanks Mike. If possible, I'd like to work with them to see about an extension of the 60 minutes. Thanks!
0Sounds like a plan! I'll reach out to the folks on our side and we'll be in touch.
0Hi.
Is the 60-minute limit still in place? Currently, we are having issues saving the changes to a file opened in local file sync.
0Could you provide the link to download the latest version (1.17) of Local File Sync?
0Jehanzeb Khan here ya go!
Windows: https://w-audit-app.app.wdesk.com/Workiva+Local+File+Sync+1.17.0.msi
Mac: https://w-audit-app.app.wdesk.com/Workiva+Local+File+Sync+1.17.0.dmg
0thank you Mike!
0You're welcome 🤜 🤛
0Hi Mike, many users on my team would like extensions beyond the 60 minute time limit for file sync. Is it possible to extend the time-limit for 114 users?
If that is too many, near 50 of our users would for sure benefit from a time limit extension as they're more active in Workiva than the remaining.
Thanks,
Anthony0Not sure if this post is still being monitored, but please add my organization as additional stakeholders who would like to see extensions beyond the 60 minute limit for local file sync (or at least some sort of option to extend the sync session by manually clicking on a pop-up to keep it open). Thank you.
0You betcha, Russel. I'm all up on it. And thanks for chiming in :)
0+1 to the request that Wdesk extend the local file sync checkout limit. Our team has experienced instances where data has been lost due to the file becoming desynchronized when the 60-minute limit is reached.
While I understand the warning popup is intended as a security measure, many of the risk professionals at our organization are well-versed in the other compensating controls in our environment (e.g., authentication, screen locking, MFA). In our experience and in our environment, the 60-minute limit is not seen as a helpful or necessary control.
I would be happy to discuss this further with the product team, as it looks like this has been a concern for over 2 years. Extending the checkout limit or making it user-configurable would be greatly appreciated by our organization and would help us avoid potential data loss incidents.
I look forward to hearing your thoughts.
0Please sign in to leave a comment.
Comments
14 comments