James, if you are using an identity provider (such as Microsoft Azure Active Directory) then you will likely be able to extend the ND session timeout period by linking the IDP with NetDocuments using federated identity. For example, one of my clients extended it to 10 hours to ensure no one is logged out during work hours. I'd be happy to connect directly with you if you need assistance with it.
ndWeb - Adjustable Timeout Value
So many of our users complain about being constantly logged out of ndWeb within Edge because of the timeout feature. We get that it's there for security, but would really appreciate the ability to set the value ourselves at the repository level. If the vast majority of our work is being done on firm devices that already have multiple layers of authentication then it makes no sense to have this setting set to a value that interrupts workflow multiple times throughout the day.
Please sign in to leave a comment.
Adding to this great suggestion: If implemented, create a distinction on the source IP address. For example, extend the time out to match a specific IP range but time out anywhere else. Maybe match the echoing IP addresses?