This release is driven by customer feedback, with updates across responsibility management, filtering, asset access rights, and contract archiving. Each change addresses specific requests from users looking for more precision and control in their day-to-day work in the .legal platform.
When transferring a user's responsibilities, you can now choose exactly which entities to transfer rather than transferring everything in bulk. From the user overview, you can drill into each area (such as contracts, assets and processing activities) to see every individual field and record the user is connected to. Select only the specific entities you want to reassign, choose the receiving user, and confirm. This also now works for custom fields, which weren't included in previous versions of this feature.
You can now filter on text fields using "contains" and "does not contain" logic, and list-based filters support both "any of" and "none of" matching - making it straightforward to include or exclude specific values. These filtering options are available across contracts, assets, and tasks, with more areas of the platform to follow.
Filters are saved per record within your session, so they'll persist if you navigate away and come back — until you close the browser.
When archiving a contract, you can now optionally set an end date at the same time and choose which obligations to update with that date. Any planned obligation tasks that fall outside the new end date are automatically removed, while tasks that are in progress or already completed are kept. This keeps your obligation overview clean without losing historical data.
Assets now support a more granular permission model. In addition to overall asset access, you can control which input fields a user can read or edit within an asset. This means a user may have read access to the asset overview but no edit rights on specific fields, for example business area. If a user has no edit access to any fields on a given step, the step icon in the navigation is hidden. This replaces the previous locked-field approach and gives administrators precise control over what each role can see and change.
You can also now restrict which asset templates a user is allowed to create assets from. If a user tries to create an asset from a template that includes required fields they don't have access to, they'll see a clear warning and won't be able to proceed until an administrator adjusts their permissions.
We'd love to hear from you! Your input helps us keep improving the platform. Please don't hesitate to reach out to our support team with your thoughts, questions, or suggestions. 🚀