5 posts tagged with "Security"

Product Access Layers are calculated on 'Save' in the Manage Products task. If users lack the resulting access layers, they will lose access to that product and be unable to edit it further.

We're introducing a warning toast that monitors product field changes and alerts the user when current inputs will result in an access layer they lack, recommending to finalise all required inputs for the product before saving. This mitigates the risk of an inaccessible and incomplete product that may otherwise block task completion.

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.