Check Out What's New

New Features

Updated "Next Expiration" column

Idle Session Timeout for Users

Updated Compliant Parties Count in Projects

Bug Fixes

Updated "Next Expiration" column

We have updated the "Next Expiration" column on the Parties list page to make it more clear not only when a user has a looming line of coverage expiration, but when they have had one expire already that needs attention.

The clock icon and text will show gray, orange, or red depending on the situation and a popover on hover will clearly show the status of each line of coverage for the party.

Please click here to read the Help Center article to learn more.

Idle Session Timeout for Users

We take security seriously. This is why, starting today, organizations using SSO can request a specific idle session timeout parameter to be set to determine when their users will be automatically logged out and must re-authenticate before using TrustLayer again.

By default, the platform idle session timeout is set at 5 days. This means that if a user is inactive for 5 or more days, they will be automatically logged out of any sessions and must log in again before they can access TrustLayer. 

Updated Compliant Parties Count in Projects

Previously, as shown in the screenshot below, on the Projects page the total count of compliant parties would include inactive parties. This has been updated to be more accurate by only including active parties.

Bug Fixes 

The below bugs have been resolved:

• Fixed a bug where parties with a reviewed document with a future valid from date didn't show as compliant when they should have