hi all, I am not sure whether it's the right place to throw my question or whether it's duplicated/ resolved one. May I know if I could restrict the users to view entities (e.g. dataset) while they do the search in the UI? I have already used

View Entity Page

and applied it to specific groups / users, but it only restricts the user to view the detailed content , but fails to restrict the "list" action when the users do the search on the UI. So, It somehow exposes the information to the users even she/he cannot access the details of the assets. Thanks in advances.

It is the current state of things, yes.

hi @better-orange-49102, may i know whether it's a yes for the

could restrict the users to view entities (e.g. dataset) while they do the search in the UI

? thanks

The listings do not hide entities that users do not have rights to view.

oh, i see. thanks for your information. May I know whether the there is related discussion / backlogs that is pertaining to it? Since I would like to see whether I could make a PR or have a look at how it could add that kind of "list" restriction. thanks

https://datahubspace.slack.com/archives/C02QMLWJG12/p1661100440952289?thread_ts=1661100440.952289&cid=C02QMLWJG12 I vaguely recall someone talking about the changes required somewhere but I can't find it

thanks @better-orange-49102! I would like to have a try on implementing it with

Domains

.

Hi @alert-traffic-45034, I think we’d be open to that contribution!

@alert-traffic-45034: We have a similar problem/request, see https://datahubspace.slack.com/archives/CV2KB471C/p1674229275671439 Currently trying to figure out how to solve this best and what needs to be changed where. Our current approach is to filter the results in the GMS backend before forewarding it to the GUI / graphQL API by checking for each search result if the current user has access to the details page. If they are not allowed to view at least parts of the detailed content the result is filtered.