 Armin asks, I worked in an organization from where I'm leaving this month. I created a PowerApp and Flow associated with it, as the flow runs directly from my email. But when I would leave, my email would be destroyed. So I'm afraid what I can do in such a situation. If I make someone as co-owner after my leaving, will it become the owner? I never saw such a scenario, so it'd be grateful for your input. I saw the Microsoft documentation while clicking on edit section that I'm unable to change the owner as it says, this is a non-solution flow, the owner cannot be changed. How can I fix it? As I have to give access to someone who'd be working in the organization. The flow is associated with my app, which runs every two days. How can I assign it to someone as my email will not longer be valid after I leave my organization? Great question, Armin. It's one that a lot of organizations face when they have employees leaving for whatever reason that they leave the organization, whether it's through these Power Automate Flows or other types of assets that we might have an Office 365 and Power Platform. So the good news is you can take the flow, you can't replace the owner because you always have to have an owner. But what you can do is add another co-owner. You do that by editing the flow. So what you'll do is you'll add another person as an owner, that person will have the right permissions now to take ownership and execute, edit that flow. So that's the first part in adjusting the flow. Norm, does that answer part of his question of, if he has a co-owner and he leaves, then should the other co-owner become the primary owner of that and then can go and add other co-owners? Yes. So it's not really a concept of primary secondary owners, but just in the owner pool and then the flow doesn't go away. So the thing to be certain of now is to drill into the flow and check the connection references in case they are running against your ID. So when I'm talking about connection references, I'm talking about those connections that you would have set up inside of the action. So think of sending an e-mail, maybe it's tied to Armon's account, or doing something in a SharePoint list. Make sure those connection references are updated to the other co-owner or some other user account that's impervious to password changes or leaving the organization. So that's the Power Automates, like Power Apps. You should be able to add your co-worker as a co-owner and that should have the continuity for both the flow and the app, and we'll probably add some links to some Microsoft Docs to help you with that. Great question.