Executive summary
- What: Flow now uses the staff permissions managed in your Shopify admin instead of a single blanket app permission, and checks each workflow against the permissions its steps require.
- Why: Staff could previously automate actions they were not allowed to perform manually. That gap is closed, and Flow becomes auditable through the same roles as the rest of the admin.
- Who: Any store where more than a handful of people touch Flow, especially merchants with separated marketing and support roles.
What changed
Access to Flow is now set by two permissions in the Flow automations category, under Settings, Users, Roles. View, create, and delete automations controls whether a staff member can open Flow at all, along with editing, duplicating, importing, exporting and deleting workflows. Manage connections and secrets controls the Flow settings page, where accounts such as Google Sheets or Slack are connected, and is required to turn on any workflow that uses a secret.
Flow also evaluates each workflow against the staff member's other admin permissions. To test or activate a workflow, they need permission for every step it contains. A workflow with an Add customer tags action requires the Edit customers permission. A staff member missing one can still open Flow, build and edit workflows, and save drafts. They cannot test, turn on, turn off, apply changes, run manually, or cancel and retry runs for that workflow, and they will not see sample data, test results or run details they lack permission to view. Flow explains what is missing when they attempt the action.
The migration is deliberately gentle. Workflows that are already on keep running. Staff who have Flow access today keep it, because they are granted the Flow automations permissions automatically.
Why it matters
This is governance catching up with capability. Flow is one of the most powerful tools in the admin: a workflow can tag customers, adjust inventory, call external services and move order state. Granting Flow access previously granted all of that implicitly, which made least-privilege design impossible to enforce.
The practical consequence is that role design now determines what automation each team can ship. If your merchandising role lacks Edit customers, a merchandiser can draft a loyalty tagging workflow but cannot turn it on. That is correct, but it surfaces as a support ticket rather than a policy discussion unless you get ahead of it. Stores running substantial inventory automation through Flow templates should map which roles own which workflows before anyone hits the wall.
There is also an audit benefit: Flow activity is now explainable in the same terms as admin access.
Role-specific impact
- Marketers: Campaign and segmentation workflows that write to customers now require customer edit permissions. Expect to request access rather than assume it.
- Developers: Workflows using the Send HTTP request action or stored secrets require Manage connections and secrets. Confirm the role used for deployment and testing carries it.
- Store admins: Review roles now rather than reactively. Automatic grants cover current Flow users, but new hires inherit only what their role grants.
Use-case example
Real-world scenario
A 140 person apparel merchant gave 22 staff the old blanket Flow permission, including six support agents who only needed to read run history. Under the new model the team rebuilt three roles: a Flow owner role with both automations permissions plus customer and order edit rights, a builder role without secrets access, and a read-only support role. The result was 16 of 22 accounts dropping to reduced privilege, and two workflows that had been quietly tagging customers from a support account surfaced for review.
Implementation checklist
- Open Settings, Users, Roles and list which roles now carry the Flow automations permissions after the automatic grant.
- Inventory active workflows and note the admin permissions each step requires, especially customer, order, product and inventory writes.
- Identify the owner for each workflow, then confirm that person's role carries every permission their workflows need.
- Move staff who only review run history onto a role without create and delete rights.
- Restrict Manage connections and secrets to the group that administers external connections.
- Brief support on the new failure mode, so a staff member who cannot activate a workflow treats it as a permissions question, not a bug.
FAQ
Q: Will any of our running workflows stop?
A: No. Workflows already on continue to run, and staff with Flow access today keep it through an automatic grant of the Flow automations permissions. The change affects new activations, tests and edits rather than existing execution.
Q: Can we grant Flow access to specific workflows only?
A: No. Flow automations permissions apply to every workflow in the store. Granularity comes from the underlying admin permissions, which determine which workflows a staff member can test and turn on.
Resources
Staff permissions for Shopify Flow
Need guidance? Talk to Makro.