Skip to content
Tutorials Center
My learning

Topics

Lesson 31 of 36 ยท Collaboration and Handoff

Comments, Sharing and Permissions

Work with others in Figma: multiplayer editing, comments and mentions, sharing links, roles and permissions, version history and FigJam for workshops.

Figma was built around real-time collaboration. Several people can edit the same file at once, and everyone sees each other's cursors. Reviewing, discussing and sharing happen in the same place as the design, so there are fewer exported PDFs and outdated screenshots. This lesson covers the social side: comments, sharing, permissions and the habits that keep a shared file healthy.

Figma cannot run on this site. Plan names and menu labels can change over time. The code examples are labelled JavaScript stand-ins that model permissions and comment threads.

Multiplayer editing

Open a file with a colleague and you see their colored cursor and name. Click a cursor's name to follow that person's view (spotlight), which is excellent for walkthroughs. Press Alt (Windows) or Option (macOS) and click an avatar in the toolbar to follow as well. Everyone's changes sync immediately; Figma merges edits at the property level, so two people can edit different layers without conflict.

Guidelines for busy files:

  • Work on your own page or section, and name frames with your initials during exploration.
  • Use sections (Shift+S) to group frames visually and mark status ("Ready for dev").
  • Avoid renaming shared components while others are working with them.

Comments

Press C to enter comment mode and click anywhere on the canvas (or on a specific layer) to leave a comment. Type @ plus a name to mention someone; they get a notification and an email. Comments are threaded: reply, add emoji reactions, and resolve a thread when it is done. Resolved comments stay available in the panel under the resolved filter.

Writing useful feedback:

  • Be specific: "The helper text fails 4.5:1 contrast" beats "colors off".
  • One issue per comment so each can be resolved separately.
  • Attach the point to the relevant layer.
  • Ask a question or suggest an action, and mention an owner.

Comments are visible to anyone with access to the file. View-only users with comment access can leave feedback without being able to change the design.

Sharing

Click Share at the top right. You can:

  • Invite people by email with a role.
  • Create a link with a permission level: can view or can edit (and, in some plans, can view in Dev Mode).
  • Set whether the link works for anyone, for people in your organization, or only for invited people.
  • Share a prototype link separately, which offers the Present experience without exposing the file's layers.

Always choose the least permission that does the job. A stakeholder who only needs to look should have can view, and a developer who needs specs should use Dev Mode access.

Roles and permissions

Common roles on a team (names vary by plan):

Role Can do
Viewer Open, comment, play prototypes; no editing
Editor Edit files in projects they can access
Admin / Owner Manage members, billing, libraries

Permissions apply at several levels: organization, team, project and file. A person's effective access is generally the most permissive of the levels that include them, but a file link's access can be tightened by org settings. The stand-in models a simple, safe check.

JS Stand-in: who can do what?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Version history and restoring

Figma autosaves and keeps version history. Open the file menu, choose Show version history, and you can see checkpoints, restore an earlier version or make a copy of it. Add named versions at milestones ("Sent to client, 12 May") so you can find them later. Restoring creates a new version, so you do not lose later work.

Organizing teamwork: pages, sections, status

A readable file makes collaboration easier:

  • Cover page with project name, owner and status.
  • Pages by purpose: Cover, Explorations, Ready for Dev, Components, Archive.
  • Use sections with status markers (a colored fill and a label) and the built-in status badges, if available on your plan ("Ready for dev", "Completed").
  • Keep a Changelog or notes area for decisions.

Comment threads in practice

Treat comments like a task list. A thread has an author, an assignee (the person mentioned) and a state. The stand-in turns a thread list into a review summary.

JS Stand-in: review open comment threads

Press Run (or Ctrl + Enter) to see the console output here.

No output.

FigJam and workshops

FigJam is Figma's whiteboard for brainstorming, flowcharts and workshops: sticky notes, stamps, voting, a timer and shared cursors. Use it for journey maps and sitemaps before you open design files; link FigJam boards into design files to keep decisions connected. You can also paste design frames into FigJam to discuss flows.

Healthy habits

  1. Name your files and pages clearly; avoid "Untitled".
  2. Keep one source of truth per feature; do not scatter copies across projects.
  3. Resolve comments you addressed, so open threads are real work.
  4. Share prototype links, not file links, with people who just need to test.
  5. Review access periodically; remove people who left the project.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which key enters comment mode?

    Pressing C starts comment mode.
  2. 2. What should you give a stakeholder who only needs to look and give feedback?

    Give the least permission that does the job.
  3. 3. Restoring an old version of a file does what?

    Restoring makes a new version, so history is preserved.
  4. 4. What is FigJam mainly for?

    FigJam is the collaborative whiteboard in the Figma family.

Summary

  • Figma is multiplayer: follow cursors, use sections and own pages to avoid collisions.
  • Comments (press C) support mentions, threads and resolving; write specific, actionable feedback.
  • Share with least privilege using roles, link settings and prototype links.
  • Version history and named versions protect your work.
  • FigJam supports early-stage collaboration.

Next: Dev Mode and Handoff