Use of Multiple widget on Portal.

[srvalw92]

Suppose there is a page on portal which is used by two different teams (IT & HR). How we can avoid any impact for another team if we make some changes while cloning standard widget and put it on an instance?

Getting an error for another team : Read operation on Table '<table_name>' from scope 'Service Portal - Standard Ticket' was denied. The application 'Service Portal - Standard Ticket' must declare a cross scope access privilege. Please contact the application admin to update their access requests.

[Its_Azar]

Hi there @srvalw92 

When you clone a standard widget and place it on an instance, make sure to isolate the customizations to avoid cross-scope issues. The error  "Read operation on Table '<table_name>' from scope 'Service Portal - Standard Ticket' was denied," indicates that there is a cross-scope access issue.

Create separate clones of the standard widget for each team. 

make sure,  that each widget clone is correctly configured with the necessary cross-scope access privileges. 

 Place each team's widget in its own scoped application. 

Before deploying changes to production, test them in a sandbox environment. 

If this helps kindly accept the answer thanks much,.