Flows - giving a teammate access to a flow
Last updated: October 29, 2026
Why they can't see it
Flows access is two-tier. Being in the organization isn't enough on its own — access is granted per project, and a new user with no project membership sees nothing.
Organization admins see everything.
Adding someone
Step 1 — organization membership.
Avatar bottom-left → Organization → Users → + Invite Users → enter their email.
Step 2 — project access. Go to the project → Membership in the left panel → + Add members → select the user and assign a role → confirm.
Which role
Role | Can |
|---|---|
Consumer | Use flow HTTP endpoints, MCP servers and forms, typically via the Service Catalog. Cannot view a flow's configuration. |
Viewer | View flows in the project. |
Editor | Edit flows and manage app installations. |
Admin | Manage users in the project and create custom apps. |
Organization Admin | Manage the whole organization, including projects, registry subscriptions and agent pools. |
Consumer is worth knowing about — it lets someone trigger a flow without seeing how it's built, which is what you usually want for self-service.
Doing it for a group
Once people are in the organization you can put them in teams: avatar → Organization → Teams → + New team, name it and assign users. A team can then be added to a project the same way an individual is.