Hi Vinoth,
It is strongly recommended to always try and set the permissions through the metadata security configuration. This will ensure that the user does not have access to the data neither through the UI or APIs.
The one use case for using the "*.ui.json" permission configuration is when you need to show/hide attributes based on the value of another attribute.
Example: Hide the entire attribute "ActiveSince" if the attribute "Status" ov value is = "Inactive".
The above behavior cannot currently be accomplished within the metadata security permissions as filters are only applicable at the entity/relation level and can't be applied at the attribute levels.
Again keep in mind... even though you can hide the attribute within the UI, the user can still see the "ActiveSince" data if they were to fetch the profile data through the API.
------------------------------
Bryant Barrenechea
Solution Architect | Professional Services
------------------------------
Original Message:
Sent: 10-25-2023 00:33
From: Vinoth Kumar Chittibabu
Subject: Where does the source/entity level permissions set for user roles are maintained
Hi Bryant & Ashish, Thanks for the details and I was following the same APIs for setting permissions.
I also saw the below documentation to show/hide profiles details based on role,
https://docs.reltio.com/en/model/manage-profiles/profiles/hideshow-profile-information-based-on-user-roles#hub-configuration-example-0
Could you share some inputs on the above documentation and when to use the "*.ui.json" config file and when to use the APIs to set role based permissions.
Thanks,
Vinoth
------------------------------
Vinoth Kumar Chittibabu
Mastech Infotrellis Inc
------------------------------
Original Message:
Sent: 10-23-2023 11:40
From: Ashish Rawat
Subject: Where does the source/entity level permissions set for user roles are maintained
Here is the API to get the Metadata security:
Get {{applicationURL}}/permissions/{{tenant}}
------------------------------
Ashish Rawat
Sr. Manager
Fresh Gravity
Bangalore