When an entity undergoes partial data deletion, the data for an offboarded jurisdiction is deleted, having reached the end of it's retention period. With this deletion, related products may also be selected to delete. When using Dynamic Access Layers, if the deleted data was an input to the Entity's Access Layers, they will now be re-evaluated based on the remaining data.
Product Access Layers (PALs) and Product Field Access Layers (PFALs) introduce a dedicated security model for product data. These controls allow clients to restrict which products a user can see, and which product fields they can view, based on Business Related and Geographic access layer entitlements.
This ensures product visibility is governed independently of the owning Entity, providing stronger information barriers and more precise access control across all product-related features.
The capability to define which page users in teams will be directed to upon user login.
A toggle has been added to the Dynamic Assignment Configuration page, enabling clients to trigger Dynamic Access Layer calculations when Entity Drafts are updated. This feature is particularly useful for calculating access layers for Related Parties.
There is now an option to enforce the usage of SSO for a tenant. If this option is enabled, the users won't be able to log in without SSO (via user and password) even if those have been created beforehand. Please reach out to your contact at Fenergo if you require this to be enabled.
Users can be suspended, this will prevent them from logging in until they are reactivated.
The extension of Teams Limits to 80 Teams; the extension of Access Layers Limits to 900 Access Layers & the extension of Dynamic Access Layer Rule Limits to 380 Rules.