You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In UI, I would like to be able to differentiate between a user who has access to an entity through domain level permissions or entity level permissions. This is because I am not able to remove a user from an entity if they have domain level permissions.
for example in the scenario above, those two users have domain level access, hence the delete button shouldn't be present. But I don't have a way of determining whether their access is domain level or entity level
Describe the feature you are requesting, as well as the possible use case(s) for it.
We should be able to determine whether a user's access is domain or entity level. Or we should have better way of managing entity and domain permissions/relations
Indicate the importance of this feature to you.
Must-have
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In UI, I would like to be able to differentiate between a user who has access to an entity through domain level permissions or entity level permissions. This is because I am not able to remove a user from an entity if they have domain level permissions.
for example in the scenario above, those two users have domain level access, hence the delete button shouldn't be present. But I don't have a way of determining whether their access is domain level or entity level
Describe the feature you are requesting, as well as the possible use case(s) for it.
We should be able to determine whether a user's access is domain or entity level. Or we should have better way of managing entity and domain permissions/relations
Indicate the importance of this feature to you.
Must-have
Anything else?
No response
The text was updated successfully, but these errors were encountered: