Things to keep in mind when changing the default service portal

jigyasaarora23
Tera Contributor

Need you view on few question such as : What do we need to keep in mind when we are  changing the default service portal for our instance. What else uses the record of default portal. What could get impacted?

What are the implications/Risks in doing this? 

2 REPLIES 2

Dan O Connor
ServiceNow Employee
ServiceNow Employee

Hey @jigyasaarora23 , it will depend specifically on what you want to change.

 

If you simply want to create your own Service portal or Employee Center (not edit the provided OOTB one) you can absolutely create another one to use instead. Our OOTB assets can be applied to multiple portals. When you add widgets etc, an instance of that widget is created meaning the instance is unique to that portal.

 

So you can safely create your own ESC or SP without any risks or impacts.

 

Obviously there is considerations to make in terms of user experience. Ideally you should have only one Employee Center or Service Portal.

 

However if you want to change the existing one, there is a ton of configuration options which you can use to personalize the look, feel and experience to be unique to you, while not being customization. 

 

If you have more details what you plan to do, can probably advise better. But for example of what you can do that would be configuration, and therefore no risk. 

 

- Apply your own branding and colors to a portal.

- Create your own taxonomy or topics.

- Amend or edit the layout and position of widgets and alignment.

- Add or remove widgets, and change widget options. 

Hello Dan.

 

Nice answer. I have a doubt, We have built a custom employee center portal to not move the OOTB, how can I make this the default portal?

 

Best Regards.