The central issue I keep coming up against is this: How can I separate the permissions of the user who triggered a flow and the flow itself?
In a PowerAutomate approval workflow, after a document is fully approved, a copy of it is moved to a separate library, 'Final'. This library's permissions are set to read-only, so that no one can upload anything to it that hasn't gone through the approval flow. However, this step fails every time because the flow initiator does not have adequate permissions to create a document in the 'Final' folder.
The flow is triggered via a button in PowerApps. Both the PowerAutomate workflow and PowerApp were created using a service account with all privileges.
Is there a way to 'bake-in' the permissions of the admin service account?
As @Willman has noted, the connections are associated with the account that created the flow. Despite this, it seems as though this does not give the triggering user the same privileges to lists/libraries as the service account has. I have confirmed this by attempting to run my flow as the test user both without write-access to the library and with write-access. In the former case, it fails every time, indicating that the service account permission levels are definitely not being applied through the flow.