We've updated the ServiceNow Community Code of Conduct, adding guidelines around AI usage, professionalism, and content violations. Read more

Adding SIR workspace to the Unified Navigation search context menu

Stev Williams1
Tera Guru

Hi,

 

Has anyone added the SIR Workspace to the Unified Search who can help me out?

I followed the guide  here - https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/search-administ... and it all seems to work fine for Admins,  however none admins who use the SIR workspace do not get the option to select "Security Incident Workspace"

 

I thought it may well be related to ACL's specifically sys_search_source & m2m_search_context_config_search_source 

But adding the read for the role sn_si.analyst for both "Security Incident Response" and "Security Incident Response Workspace" scopes didn't seem to change much. 

1 ACCEPTED SOLUTION

Stev Williams1
Tera Guru

If anyone else finds this.

 

Fix is to add a read acl (sn_si.read role) for the sys_search_context_config table in the security incident response scope.

View solution in original post

9 REPLIES 9

Hi @Stev Williams1 

sorry again, I shouldn't answer questions on Sunday😔

I'm still checking the document and try to add another Workspace in my PDI, but have you checked the system property "glide.ui.can_search". In my recent customer project, I had to add a basic role from the FSM module to make the global search visible for all users.

Maik

Haha no problem @Maik Skoddow happy for any assistance I can get.  That property is fine and global search is ok. 

Hi @Stev Williams1 

in the meantime I found a video regarding that topic. Maybe it helps: https://www.youtube.com/watch?v=3XFU6AkiAMU 

Unfortunately, I had not the time yet to replicate the use case in my PDI.

Maik

Search Applications sys_search_context_config Search Sources sys_search_source Workspace Global Search Configurations sys_aw_global_search_config Documentation on text_search view: ...

Stev Williams1
Tera Guru

If anyone else finds this.

 

Fix is to add a read acl (sn_si.read role) for the sys_search_context_config table in the security incident response scope.

Great!