I want to present a read-only version of Dependency Views

ewilks
Giga Expert

I have a group of users (auditors) that I want to allow to see (read-only)   the maps in the Dependency Views application and a couple of the modules.   I granted them the access to these modules, when they click on the   module, they get an error, reading "You don't have permissions to view this page!"  

even after adding their role to the ACLs, I still can't see any records in these tables (see below).   If I add them to the role "dependency_views"   they are able to update, which we don't want.   What do I need to do to allow them to view the relationships in dependencies whether   it's from Dependency Views application or from clicking the map on a configuration item?

I have attempted to add their role to the read ACLs for the following:

BSM Saved View [bsm_chart]

BSM Menu Action [bsm_context_menu]

Map Indicator [bsm_indicator]

BSM Map Filter [bsm_map_filter]

BSM Related Item [bsm_related_item]

and some more...

Thanks for any help

1 ACCEPTED SOLUTION

Thanks Laurent,


I did set them up with the snc_read_only role, but that didn't give them any read access to the dependency views.  



What I ended up doing was, in addition to the snc_read_only role, I gave the group dependency_views role.   That gave the users read and write access to the dependency views, so I opened the acl NG-BSM Menu Action [ngbsm_context_menu] (with write operation) and, in the condition script, I added the following code.   Which worked to prevent the snc_read_only users from updating, while still allowing them to view the mapping:


//script code below--


if(gs.hasRole('snc_read_only')){


  answer=false;


}


View solution in original post

3 REPLIES 3

LaurentChicoine
Tera Guru

Hi Eric,



Did you try to give them the snc_read_only role?



It gives every access of the roles the user has but puts everything read-only.


Thanks Laurent,


I did set them up with the snc_read_only role, but that didn't give them any read access to the dependency views.  



What I ended up doing was, in addition to the snc_read_only role, I gave the group dependency_views role.   That gave the users read and write access to the dependency views, so I opened the acl NG-BSM Menu Action [ngbsm_context_menu] (with write operation) and, in the condition script, I added the following code.   Which worked to prevent the snc_read_only users from updating, while still allowing them to view the mapping:


//script code below--


if(gs.hasRole('snc_read_only')){


  answer=false;


}


Hi Eric,



You should not have to modify the ACL as the snc_read_only role puts the whole platform to read-only without having to modify any ACL. However the read-role applied are the ones from the other roles given to that user.