Hello
Interesting use case
The only thing I can think of will not prevent users from accessing restricted 'areas' but will at least help you pointing them to their zones:
Since the mapping of users per system is done on the NWA tool, you may create duplicated destinations for each such destination that you want to give different users to.
For example, say you have a system Sys1 on which UserA has only read permissions and User2 has write permissions
User1 and User2 are the users of the backend system Sys1
Now assume you have 2 VC users, for example VC1 and VC2, who you would like to give the repective permissions, for example, VC1 can have read permissions on Sys1 and VC2 can have write permissions.
Create 2 destinations, named VC1_Sys1 and VC2_Sys1 where the backend user used in each system is the respective one so that for system VC1_Sys1 you would use User1 and for the VC2Sys1 you would use User2
Although VC1 and VC2 may now search on both systems (as I said there is no way to filter the existing systems configured in the NWA), they could be directed to the systems prefix-ing with their names accordingly
Again, not an ideal solution but at least can tackle a portion...
Guy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.