 The guard says, I have a flow that sends a mail. Trigger is new item in a SharePoint list. The flow works fine, but the mail should come from a coworker in HR. Any suggestion how to give the flow to somebody and delete remove me? Delete slash remove me. Well, if you check the links, we've included one on how to assign basically a service or run as user. This is a common practice in most of the IT world, but I think it's something that's still getting hold in the power platform. Power platform is in that awkward teenage stage where it's not quite old enough to do everything the way IT would want it to do, but it's still young enough that pretty much anybody can grab onto it. The idea of a service account is to make sure none of your users who has been shown many times in the past, a user who sets everything up to run as themselves and then leaves the organization, but doesn't let anybody know, and that account either becomes disabled or, unfortunately in a lot of cases, deleted. You get to play the whack-a-mole game of trying to find all the different services and tools and processes that ran as that user. We have a service account and do it that way. I'd read into that. That's how I interpreted that question. Is that how you guys saw it too? But can you designate from Active Directory which user the email can be sent from? It's part of the parameters when you create that. Even if the email low-hanging fruit, the email used to go from that person, that person shouldn't own the flow either, if it's mission critical, so that you can reassign it and it should be a role that it comes from, like a mailbox depending on the situation, not from Susie, but from HR group, whatever. Well, there's so many different email steps now in flow that you can use. I mean, with different disabilities, I'll call them and the ability to specify different parameters. Yeah, I agree. Anything you can do to send that from a role or a designated mailbox or something like that, to get a level of abstraction between the user who does the authoring and editing and the process itself, abstraction is the name of the game. If you use a connector in there, so here's the key thing to this. When you send it on behalf of somebody because I've actually to deal with this, you have to use a connector in there and the person who is actually the account that it's coming from, has to log in and has to approve that connector, and here's why a role or a group or something is way better, because if that connector for whatever reason logs out, times out, has an issue, whatever, then it'll stop the entire flow and the whole thing will fail, until that person, not you, not you as the owner, not you as the creator, not you as a service account, but that person has to log back in and click on it to refresh the connector as the logged in user. So you can always change that in there, but it's definitely good to use service accounts groups, dedicated accounts of some sort of possible, but yes, yes you can, you have to use a connector and that person has to log in and approve it, and anytime the connector is disabled, they have to be the one to refresh it. Well, the fact it's a SharePoint list tells me it's in some kind of collaborative space that is more than one person involved anyway. So there's gotta be a group account in there that could be usable for that. But I just point out that here's another example of why you need to have a governance strategy around Power Platform. Yep, yep. So you can remind people of little rules and little issues like this and why you might wanna agree upon service accounts and how people author their flows. Yep, yeah, in fact, we just ran into one of my clients where they're actually doing a really nice job. They're maturing and they're bringing in a Power Platform governance and sending up a center of excellence and doing a real good job of that. And they've been working through that and I went to help them with a ticket that came in about some flow had died or whatever. And they're like, okay, can you help us with this? And I was like, yeah, I'll just reach out to the person. I know who built the flow. So I'm like, I'll reach out to them. Their email didn't work. I'm like, did that person leave? And they're like, oh yeah, by the way. And I'm like, oh no. Cause I knew that this person had been a power user and we had been kind of chasing this person for a while trying to collect all their stuff, getting it shared, getting it put in. And I'm like, oh no, I know this is gonna be kind of pain. So we had to go in and get anything that I could at the top level to your point, Sean. And there's certain things like we can't see certain things. We can't see certain things. I'm like, well, here's the things I can see. Here's the things I can help with. Here's the things that you're just kind of gonna be stuck with having to fix yourself. And so, I mean, at least they're down the path where they're maturing enough to be able to put some of the governance around that. Once they're done, I think that'll help a lot. But while I was in there, I'm like, hey, while I'm in here, I'm just gonna go ahead and share this with our admin team in case we need to help you in the future. Yeah. And you can't tell them with any certainty how far down the iceberg goes below the level. So yeah. All they knew was that things weren't working. Things that they had depended on for quite a while just weren't working and they couldn't figure out why. And I'm like, oh, ouch, it's a hard lesson to learn. It, yes.