Be able to adjust when NetDocuments times out (logs out) in Chrome

NetDocuments in Chrome times out (logs out) in 90 minutes, it would be nice to be able to adjust the amount of time ND times out.  We use Email Link a lot and we are running into issues when we click "Open" to an emailed linked through Outlook, and ND has timed out.  Which ndClick stops running and therefore the document doesn't check in properly and the changes don't save.

1

Comments

4 comments
  • If you're using federated ID you can pass a claim to extend the timeout.  Up to 8 hours, I believe. 

    0
    Comment actions Permalink
  • Hi Jessica.

    If your repository is connected to Microsoft Azure Active Directory (highly recommended), a NetDocuments partner should be able to assist and add a claim called 'sessiontimeout' with a setting of 480.

    480 is minutes (8 hours) and is the maximum before auto logout happens.

    Good luck,
    Paul

    0
    Comment actions Permalink
  • It would be nice not have to use federated identity.  When we used Internet Explorer, it didn't time out all day.

    0
    Comment actions Permalink
  • I understand, Jessica. As I recall, in the Internet Explorer days, the timeout was because the PC was connected to an on-premise Active Directory server and the users had selected the option to link their NetDocuments settings to link to Active Directory as well.

    These days, who needs on-premise servers when Azure Active Directory is available as part of a Microsoft 365 account??!! This gives even very small firms the ability to secure themselves just like the larger firm with IT departments at no extra cost.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post