# Power Automate run-only users missing: where it is and what to check > For the full documentation index, see https://250highstreet.com/llms.txt > Run only users missing in Power Automate? It applies to instant flows with a manual trigger, set by an owner. Check the flow type, your role and the page. Short answer: the Run only users section is on the flow details page of an instant flow, meaning a flow with a manual trigger such as a button or an item being selected, and an owner uses it. Microsoft lists run-only sharing for instant flows only, so a flow that starts on a schedule or when something changes has nothing to share that way. If your flow is an instant flow, check that you are an owner and that you are on the flow details page, not the edit screen. ## What run-only users are When you share a cloud flow, Microsoft lists three ways to do it: add an owner, share with run-only privileges, or share a copy. Run-only is the one for people who only need to press the button. Microsoft describes it this way: "Any user you add as a run-only user doesn't have access to edit or modify the flow in any way. They have permissions only to trigger the flow." A run-only user also cannot see the inside of the flow. In Microsoft's sharing guide, a run-only user "can't open the flow in edit mode, see its internal logic, or view past run history." ## Where the option is Microsoft's page says to use the flow details page. One way to get there: 1. Sign in at [https://make.powerautomate.com](https://make.powerautomate.com) and open My flows. 2. Select the name of the flow to open its details page. 3. Find the section called Run only users and select Edit. 4. In the Manage run-only permissions panel, pick the people or groups. Exact names may differ. Microsoft's own steps say: "On the flow details page, in the Run only users section, select Edit." ## Why the option may be missing Work down this list. Each item is a reason the section may not be where you expect. 1. The flow is not an instant flow. Microsoft says: "Instant flows (that is, flows that use a manual trigger such as a button or an item being selected) can be shared by using run-only permissions." A flow that runs on a schedule, or when a row is added or changed, does not fit that description. For those, the options Microsoft lists are adding an owner or sending a copy. Our advice, not a Microsoft rule: if you want people to start it on demand, build an instant flow with a manual trigger. 1. You are not an owner. Microsoft says: "You must be the creator or owner to add or remove owners from a cloud flow." Someone who was only given run-only access cannot share the flow with anyone else. Ask an owner to open the flow, or see "[The person who built your flows left: what happens and what to do](/guides/power-automate-flow-owner-left-company/)". 1. You are looking in the wrong place. The section is on the flow details page. It is not a step inside the flow editor. If you are in Edit mode, go back to the details page. 1. You are looking at the list of flows people shared with you. A run-only user does not own the flow. Microsoft's guide says run-only users get the flow only in contexts where they can run it, such as a button or an app, and that it is "not listed under their owned or team flows". So the person you shared with may not see the flow in their My flows list. That is expected. 1. Your license may not allow sharing. Microsoft's page says you must have a Power Automate license, except the free license, or a seeded license, to share a cloud flow. Check with your admin which license you have. ## Run-only is shared, but the person says it does not work You added someone and they still cannot run the flow. Check these. 1. Where do they run it from? Run-only users run the flow from the place its trigger lives, such as a button, a Teams message or an app. Microsoft's sharing guide describes it as running through "a button in Teams or a shared link". Send them that link or tell them where the button is. 1. Which connection setting did you choose? Microsoft says an owner can specify "whether run-only users need to provide their own connections or you can use a connection already defined in the flow." When a connection is set to Provided by run-only user, Microsoft says "the user that runs (or "invokes") the flow provides that connection." The flow then acts as that person and can only reach data that person can reach. If they lack access to the SharePoint site, list or mailbox the flow touches, the run can fail for them even though it works for you. 1. Is the person in the right group? Microsoft says you can enter a group name instead of single users. If you shared with a group, check that the person is in it. Microsoft also notes that if the environment is limited to a security group, the group you share with "should either be the same or a subset". 1. Does the environment need a role for them? Microsoft says that when you share a solution-aware flow with someone who is not yet in Dataverse, that person "might only be able to run the flow until an administrator assigns them a role." If they see an error message about a role, send it to your admin. ## Share with a group Microsoft's guide says: "When sharing a flow, owners can enter a group name instead of individual users for either co-owner or run-only access." It adds that to revoke access for a person you remove them from the group, and that a group helps to manage run-only permissions at scale. Microsoft's guide recommends Microsoft Entra security groups for this. Share with a group that holds the people you want. If the environment is tied to a security group, share with that group or a subset of it. Otherwise people outside the environment's allowed users might not be able to run the flow. ## A SharePoint selected-item flow A flow that appears on a SharePoint item through a selected-item trigger is an instant flow, so the section is where described above. Microsoft's sharing page says: "SharePoint users must have Edit permission or be a member of the Members or Owners group to run flows in SharePoint." A person with only read access to the list can fail even when they are in the run-only list. Microsoft's page also lets you add a SharePoint list as a co-owner, and says to "Use a list when the flow is connected to SharePoint, and use a group in all other cases." That option gives edit rights to the flow, not run-only. ## What to avoid - Do not add people as owners just to get around a missing run-only option. Microsoft's guide says: "Only add co-owners for flow collaboration as needed." It tells you to use run-only permissions when a flow needs to be shared and no one needs to edit it. - Do not share a flow that uses your own connection to people who should not reach what that connection reaches. Run-only users trigger the flow, and a flow that uses the owner's connection acts with the owner's access. - Do not list dozens of single users on a flow. Our advice, not a Microsoft rule: share to one group and manage the group. - Do not leave a flow with a single owner. If that person leaves, Microsoft says actions that use their connections might fail. ## A short check before you ask for help 1. Open [https://make.powerautomate.com](https://make.powerautomate.com) and open the flow details page. 2. Confirm the trigger is manual (a button or a selected item). 3. Confirm your name is in the Owners list. 4. Open Run only users and confirm the person or group is listed. 5. Check the connection setting for each connector. 6. Ask the person to run it from the button or link, not from My flows. 7. If it still fails, ask your admin about environment roles. ## When to get help You can build all of this yourself in Microsoft 365. If you would rather have it built and tested for your team, I do that. A tracker like this is a fixed price: \$5,000 for one, built in 2 weeks. See "[What a SharePoint tracker costs to build](/guides/what-a-sharepoint-tracker-costs/)". Bring one example of the problem to a free call. I am Al Davies. I run 250 High Street LLC and build SharePoint trackers and Power Automate flows for operations teams. I work remotely. The first call is free, and I will not try to sell you anything. See trackers I built: [Tools I built](/portfolio/) ## FAQ ### Why are run-only users not visible on my flow? Check three things: the flow is an instant flow, you are an owner, and you are on the flow details page, not the editor. Microsoft says run-only sharing is for flows that use a manual trigger such as a button or an item being selected. ### Can I share a flow run-only with a group? Yes. Microsoft's guide says owners can enter a group name instead of individual users for run-only access, and it recommends security groups for managing it. ### How do run-only users work for a SharePoint selected-item flow? Add them in the Run only users section of the flow details page. Microsoft also says SharePoint users must have Edit permission or be a member of the Members or Owners group to run flows in SharePoint. ### Can a run-only user see the run history? No. Microsoft's sharing guide says a run-only user cannot "view past run history". Owners and co-owners can view it. ### What does Provided by run-only user mean? It means the person who runs the flow supplies the connection. Microsoft's sharing guide says that with this option "the flow executes in the context of the run-only user's credentials." ## Sources - [Microsoft Learn, Share a cloud flow](https://learn.microsoft.com/en-us/power-automate/create-team-flows) - [Microsoft Learn, Guide to cloud flow sharing and permissions](https://learn.microsoft.com/en-us/power-automate/guide-to-cloud-flow-sharing-permissions) ## Related guides - [Run a flow only when one column changes](/guides/power-automate-trigger-when-specific-column-changes/) - [Power Automate run history only shows 28 days: how to keep a longer record](/guides/power-automate-run-history-28-days/) - [Run a scheduled flow on weekdays only](/guides/power-automate-recurrence-weekdays-only/) Source: https://250highstreet.com/guides/power-automate-run-only-users-missing/