Collaboration

Process improvement is not a solo activity. Flow Myna is built so that a finding can be handed to someone else as a link, a cohort can be agreed on once, and outsiders can be given exactly one project and nothing else.

Who can see what

Access works at two levels, and the difference is the useful part.

Workspace roles

Invite colleagues from the People page in the workspace.

• Owner — the workspace creator. Full control, including deleting the workspace.
• Admin — full access to the workspace and its settings; can invite and remove people.
• Member — upload data, create projects, run analysis, see everything in the workspace.
• Guest — access to specific projects only, not to the workspace as a whole.

Invitations are sent as Admin or Member. A Guest membership is what someone ends up with when they are added to a project without being given the workspace.

Project roles

Projects have their own membership, managed on the project's Collaborators page.

• Admin — full control of that project, including inviting and removing people
• Member — explore, filter, save filters and use the copilot

This is what makes projects the right unit to share with people outside your team. A consultant added to one project sees that project's data and nothing else in the workspace, however many other processes it holds.

Sharing a view

Filters live in the URL, so an analysis is a link.

1. Build the filter — by hand, from the map, or by asking the copilot
2. Copy the address bar
3. Send it

Whoever opens it, if they have access to the project, sees the same cohort with the same lens. No screenshots, and no "which filters did you have on?"

Say what it shows when you send it. "Here are the slow high-value orders from Q1" and a link is a conversation; a bare link is a puzzle.

Agreeing on things once

Links are good for a finding. For anything you will discuss more than once, there are three durable options.

Saved filters belong to the project, not to the person who made them. Save "high-value" once, with a description saying what counts as high-value, and everyone means the same thing by it. See Saved Filters.

A pinned filter sets the project's baseline: applied to everything, for everyone, until unpinned. Only a project admin can pin one, because it changes what every member sees.

Metrics go further. When someone asks the copilot about a named business metric, it proposes a definition to confirm, and an admin can promote that definition to be the project's official reading. From then on, the same question gets the same number no matter who asks it. That is usually the end of a particular kind of meeting.

Working together in a project

Several people can work in the same project at once. Filters are per person, so nobody's exploration disturbs anyone else's; what is shared is the data, the saved filters, the Board and the conversation history.

Conversations are visible across the project, so a colleague's investigation is something you can read rather than something you have to repeat.

Working well together

Name what you share. Project names, dataset names and filter descriptions are read by people who were not in the room when you made them.

Put the baseline in a pinned filter, not in everyone's head. If the team has agreed to analyse completed cases only, pin it. Otherwise half the team will be looking at a different population and nobody will notice for a month.

Share the cohort, not the conclusion. A link lets someone check your reasoning; a number in a message does not.

Next steps

• Creating Your Workspace — invite people, set roles
• Creating a Project — project membership and scope
• Filters & Exploration — build the views worth sharing
• Saved Filters — make a cohort reusable
• Co-Pilot — where metric definitions get agreed