Restrict "Edit" button in Post Incident Report (Major Incident Workbench) to Incident Assignment Gro

[macharlaven]

Hi Team,

I am working on the Australia release of ServiceNow ITSM.

I have the following flow:

Open an Incident.
Promote it to a Major Incident.
Click View Workbench.
Resolve the Major Incident.
Open the Post Incident Report tab.

In the Post Incident Report, there are two sections:

Overview
Findings

Each section has an Edit button.

Requirement:

I want only users who belong to the Assignment Group on the Incident record to be able to see and use these Edit buttons.

For all other users, the Post Incident Report should remain visible, but the Edit buttons should be hidden or disabled.

I have already checked:

UI Pages (workbench, mim_workbench_promote, mim_workbench_resolve)
UI Scripts related to the Major Incident Workbench

However, I could not find where the Overview/Findings Edit buttons are rendered or where the edit permission is controlled.

Could someone please help me with:

Which OOB component controls the Edit buttons?
UI Page
UI Script
Script Include
Scripted REST API
Other
Is there an OOB extension point or recommended customization to restrict editing based on the Incident Assignment Group?
Has anyone implemented this requirement without modifying OOB code?

Any guidance would be greatly appreciated.

Thank you!

[Ankur Bawiskar]

@macharlaven 

the page which opens up is coming from platform level i.e. "$major_incident_workbench.do"

We as admins or developers don't have access to edit anything there

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Ankur Bawiskar]

@macharlaven 

Just following up to see whether my suggested solution worked for you.

If you're still facing any issues, I'd be happy to help further.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[MacharlaV]

Yes this solution is worked 

[Ankur Bawiskar]

@macharlaven @MacharlaV 

Glad to know

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏