Service Operations Workspace Landing page Issue.

[Premnath M]

Hi all,
I have faced an issue while installing the Service Operations Workspace ITOM in the instance. I am unable to view or access the landing page of the Service Operation Workspace ITOM.
Please find the Screenshot.

Thanks,
Prem

[C598Hash]

---

@Premnath M wrote: My Health At Vanderbilt

Hi all,
I have faced an issue while installing the Service Operations Workspace ITOM in the instance. I am unable to view or access the landing page of the Service Operation Workspace ITOM.
Please find the Screenshot.

Thanks,
Prem

---

Hello, @Premnath M 

A user should have the itil role to access the landing page. A tier-1 agent is an itil user who belongs to a service desk group. A tier-2 agent is an itil user who does not belong to a service desk group. For more information about the redirection of tier-1 and tier-2 agents to the respective landing page, see Redirect an agent to the Service Operations Workspace landing page. More information is here: https://docs.servicenow.com/en-US/bundle/tokyo-it-service-management/page/product/service-operations...

[Premnath M]

Hi @C598Hash ,

I have tried the process you gave. but still, it is not working, the same issue continues in the Service Operations Workspace ITOM. Please find the below Screenshot.

if you know any other methods to solve this issue. please comment on this reply.

Thanks,
Prem

[Omkar Kumbhar · Accepted solution]

Hello @Premnath M ,

USer should have the below role to access the landing page.

Thanks,

Omkar

[Premnath M]

Hi @Omkar Kumbhar ,
Thanks for your help in accessing the landing page of the Service Operation Workspace ITOM.
Now I have another Query. how we can edit the Service Operations Workspace UI Builder?
it shows the widgets of the alert table, but we need to replace it with the Incident table widget view. how to achieve this action.

The UI Builder page it showing a Protection policy, how to override that policy and to edit the SOW.

please refer to the below image and help me with this issue.

Thanks,
Premnath