RELATED IDEAS
Restrict links based on Segment
Who: To support more complex situations where an extensive use of links, where some links only relates to different segments, or when the role does not allow visibility to some links
Impact: Much much cleaner user interface which makes the effort working with relationships between entities easier to use, or limit access to relationships the user is not intended to see.
Similar setup as Restricted Fields, but instead link centric. The feature should allow limitation types for "hidden", "readonly", and as with current RestrictedFields also to be combined with Segment, so a certain restriction only comply if the entity belongs to a certain segment (same logic as Restricted Fields)
Why: To add a governance level to the relationships between the entities as well as reducing the amount of visible linktypes in Includes and Included in in Enrich.
We are experiencing the same challenge. Since multiple divisions/companies are working within the same Inriver solution, users with no ownership of a product can still remove linked resources or manipulate relationships they should not have access to. This creates a governance risk and makes it difficult to maintain control across segments.
A restriction model for links — similar to what already exists for fields — would solve this by ensuring users only see or act on the relationships relevant to their segment. This would both clean up the interface and add an important layer of access control to prevent unintended changes.
This is definitely a feature we need in order to manage our setup securely and efficiently.
Very mush needed to handle situations like
A user in one segment A (Company) have restricted access to another company in another segment B. As it is now the user can DeleteLink in segment B without having the permission in the role on added to Segment B. This means users in Segment A are out of control as users from Segments can delete Links between Entities like Ressourses etc.