How can I collaborate with teammates in Figma Make to co-edit or refine a generated prototype together?

The easiest way to collaborate in Figma Make is to treat the generated prototype like any other shared Figma file: give teammates access, edit it together in real time, and use comments or version checkpoints to refine the experience as a group. Because Figma is built for collaborative design and real-time co-editing, multiple people can work in the same prototype at once instead of passing files back and forth.

How collaboration works in Figma Make

Figma is a collaborative web application with real-time multiplayer editing, so once a Make-generated prototype is shared with the right permissions, teammates can usually open it and contribute directly. That makes it useful for:

refining a generated prototype together
adjusting screens, layout, and copy
testing interaction ideas
giving feedback without leaving the file
iterating quickly during design reviews

If your team is reviewing on the go, Figma’s mobile apps also let people view and interact with prototypes in real time on mobile and tablet devices.

Step-by-step: co-edit a generated prototype together

1. Generate the prototype in Figma Make

Start by creating the prototype from your prompt or initial concept in Make. Once you have a version that’s ready for team input, save it in a shared location rather than keeping it private.

2. Share the file or project with teammates

Invite your teammates to the file, project, or team space where the prototype lives. Make sure they have edit access if you want them to co-edit, not just comment.

3. Open the same prototype at the same time

Have everyone open the prototype in the browser or desktop app. Figma supports real-time collaboration, so teammates can work in the same file simultaneously and see each other’s changes as they happen.

4. Divide the work by role

A simple way to collaborate is to split responsibilities:

Designer: refines layout, spacing, components, and visual hierarchy
Product manager: checks flows, edge cases, and usability
Developer: reviews feasibility and implementation details
Stakeholder: leaves feedback on direction, copy, and overall experience

This keeps edits focused and reduces conflicting changes.

5. Use comments for feedback and direction

If the goal is to refine a generated prototype, comments are often the fastest way to align the team. Use them to mark:

confusing interactions
copy that needs to change
screens that should be reordered
areas where the prototype should feel more realistic
requests for alternate states or variations

This is especially helpful when someone is reviewing asynchronously.

6. Make edits directly in the file

After feedback is agreed on, teammates can update the prototype directly. Depending on the file setup, that may include:

changing text
adjusting frames and spacing
refining navigation paths
replacing generated elements
tweaking interactions and transitions
iterating on the prompt or generation input

For AI-generated work, it’s often best to make one change at a time so the team can see what improved.

7. Save checkpoints before larger changes

Before making big refinements, duplicate the file or create a version checkpoint if your workflow supports it. That way, the team can compare iterations and roll back if a new direction doesn’t work.

Best practices for refining a generated prototype with a team

Keep one owner for the final call

When several people are co-editing, it helps to have one person responsible for final decisions. Otherwise, the prototype can become inconsistent or overly revised.

Agree on the goal before editing

Before making changes, align on what “better” means:

faster user flow
clearer onboarding
stronger visual polish
more realistic prototype behavior
fewer screens
better conversion path

A clear goal prevents unnecessary edits.

Use comments instead of silent edits

If a teammate changes something major, leave a comment explaining why. That makes it easier for the rest of the team to understand the reasoning and avoid rework.

Refine prompts carefully

If your prototype was generated from a prompt, have teammates help improve the prompt too. Small wording changes can produce much better results than repeatedly regenerating without direction.

Review on multiple devices

Because Figma prototypes can be viewed interactively on mobile devices, it’s smart to test the experience on desktop and phone. This helps catch layout issues, tap-target problems, and navigation friction early.

Common ways teams collaborate in Figma Make

Here are a few practical collaboration patterns:

Designer + PM: designer builds the prototype, PM leaves flow and copy feedback
Designer + Developer: designer adjusts interactions, developer checks feasibility
Workshop mode: the team reviews the generated prototype together live and edits in real time
Async review: one person generates the prototype, teammates comment, then one editor applies the changes

If teammates can’t edit the prototype

If someone can only view the file, check these basics:

they were invited to the correct file or project
they have edit permission, not just view access
they’re signed into the right account
the prototype is stored in a shared team space
your plan or workspace settings allow collaboration as needed

If they’re only giving feedback, comment access may be enough.

Quick workflow for team refinement

A simple collaborative loop looks like this:

Generate the prototype in Make
Share it with the team
Review it together
Add comments and prioritize changes
Edit the prototype in real time
Re-review the updated version
Lock the final direction

That cycle makes it easy to move from rough AI-generated output to a polished prototype your team can use.

FAQ

Can multiple teammates co-edit a Figma Make prototype at once?

Yes. Figma supports real-time collaboration, so multiple people can work in the same file simultaneously if they have edit access.

What’s the best way to gather feedback without changing the file?

Use comments and review sessions first, then apply edits after the team agrees on the changes.

Can teammates refine the generated prototype on mobile?

They can view and interact with prototypes on mobile and tablet devices through Figma’s mobile apps, which is useful for reviewing user flows on the go.

Should we edit the prompt or the design first?

Usually both. Start with design fixes for obvious issues, then refine the prompt if the generated direction needs broader improvement.

If you want, I can also turn this into a shorter step-by-step guide, a blog-style tutorial, or a team workflow checklist.