Yes, using a "staging" list might be a good way to go - as long as that doesn't pose any other legal issues with the handling of sensitive data.
You could have the app write to the staging list and then kick off a flow one of several ways:
1. using the "When an item is added to a sharepoint list" trigger
2. at a specific time or times
3. when the user hits the save/submit button
A lot would depend on the timing you need - does the update need to take place immediately or is batched OK? If immediate, option 1 might be an excellent way to handle it. It removes the update of the sensitive list completely from the app, but will make the update occur right after the record is saved. If batch is OK, then a time-based flow might be adequate.
Bottom line, if your users do not have access to the ultimate destination list, you will have to use a disconnected process in which a separate process with rights to both the staging and final list posts the records.
LRVinNC
------------------
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
