Flow Designer Cross Scope Access Error Scope does not have write access to sn_hr_le in Else Rejected

[Pavankumarkp]

Hi Team,

I am currently working on an Employee Offboarding Flow in Flow Designer (HRSD module). The flow is triggered when an offboarding request is submitted and follows an approval process.

The Approved branch is working as expected, including record creation and updates. However, in the Else (Rejected) branch, I am trying to update a record in the table sn_hr_le_case, and I consistently receive the following error:

“Scope does not have write access to table sn_hr_le_case”

Some details:

• Application scope: Custom scoped application

• Table being updated: sn_hr_le_case

• Action used: Update Record (Flow Designer)

• Error occurs only in the Rejected (Else) branch

• Other flows like Onboarding and Leave Automation are working with current roles

I would like to understand:

1. Why is write access restricted specifically in this scenario?

2. Is this due to cross-scope privileges between my custom app and the HR Core scope?

3. Should I create a Cross Scope Access (Application Access) privilege explicitly?

4. Is there a recommended best practice to handle updates to HR tables from a custom scoped Flow?

Any guidance on the correct and secure way to resolve this would be greatly appreciated.

[Ankur Bawiskar]

@Pavankumarkp 

the error clearly says it's cross scope issue.

Seems you can't write that record of "sn_hr_le_case" from your custom scoped app

Define RCA for that table and they try

Restricted caller access privilege settings 

Also try to see if READ & WRITE access is allowed on that table from Table -> Application Access -> Accessible from All Scopes

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

[Pavankumarkp]

Since I am already working inside HR Core and my flow is ALSO in HR Core, now I am afraid that neither RCA is the issue nor the cross-scope between custom app and HR Core.  More than that i have given READ & WRITE access too..  so i think HR Lifecycle Event Case tables are protected because they contain sensitive employee data and that's why Direct “Update Record” is triggering restriction.. may be  a dead lock now...