Add button not working - Add a SharePoint list or library as owner

[ks6]

Hi everyone,

I'm facing a strange issue this morning. I have an automation flow running on a SharePoint list that triggers when a new item is added to the list. I'm trying to add the list itself as an owner of the flow such that notifications come from the list and not from me.

The site and list/library fields both auto-populate with the name of the site and the list that the flow concerns respectively which is good, however the 'Add' button simply does not work. I've clicked it a million times and tried waiting to see if anything will happen and it doesn't even suggest it's trying to add the owner on. There is no indication that the button is working in any capacity - no error messages, the browser doesn't suggest it's loading anything, nothing.

I've so far tried:

- Different browsers.

- Signing out and then reauthenticating.

And I'm not sure what to try from here - has anyone else experienced this?

[v-bofeng-msft · Accepted solution]

Hi @ks6 ,

'Add a list as a co-owner' is used to make everyone who has edit access to the list automatically gets edit access to the flow. If you use send an email to send a reminder, who the sender is is only related to which connection the action uses by default. If you need to change the sender, you can set the action's  'Send as':

1\Create an account for this list in your tenant

2\Set the Send as permission for the the account (make sure your account have the send as permission of this account)

3\Set the action's send as

Best Regards,
Bof

[ks6]

Hi @v-bofeng-msft,

Many thanks for your response. I guess this confirms in a way what I suspected though it is a bit annoying for the users as the list does not show up in the 'owners' or 'connections' at all; I had to start this thread to find out that it's just a connection for permissions and nothing more as Automate does not make that clear. Ideally what we would've liked is for the list to be able to send notifications out on behalf of itself, as currently they are all being sent from me. Appreciate you clarifying this though.

We are aware that we can make 'dummy' or bot accounts to fulfil this need but there are extra costs to those as they would need licencing for every application we want to use them with. For instance to make a bot the owner of a Microsoft Forms connection we would have to allocate it a package with a Forms licence in, despite the fact that the bot isn't a real person and won't be building or sending out any Forms, just owning the connection in Automate.

Thanks again for your help.