Skip to main content
Lishay
January 30, 2021

Give unique access to specific pages

  • January 30, 2021
  • 244 replies
  • 61291 views

Hello 👋

First, I’m happy about the opportunity where I can make an impact on this amazing product.

My idea is pretty simple but can make a huge difference in the way we share files with stakeholders and colleagues. I suggest adding the ability to give different access (viewer/editor) for pages within a Figma file.

Because in most cases, we’re trying to include a whole project, feature, or function, whether small or big, in one Figma file - it becomes a real pain-point if the lowest level of grant permissions it’s the file itself instead of the pages within the file.

I’m sure a lot in this community can agree with me that many times you gave people access - it was relevant to certain areas of the file, and less to other areas.

  • I want to give content writers access to a specific page where they can edit and review content.
  • I want to give developers access to a specific page where they can play with responsive layers and explore edge-cases.
  • I want to leave experiments (Some would call it a playground, sandbox 😃) and previous versions to myself, to avoid background noises from the rest

The current situation is that I give everyone viewers access, each one of them looking for his relevant place among the information load and I avoid giving an editor access to prevent touching what they should not touch by mistake 🙄

What do you think about it?
Of course, feel free to vote if you agree with the idea.

244 replies

SeanMakesApps
New Member
July 20, 2025

The Problem

The sales and management teams create client quotes and pitch decks for private and public listed companies which contain budgets and confidential or sensitive information. All staff - from managers to designers to developers - can access this material, which increases privacy and “leak” risks, as well as increases the risk of in-office bickering regarding budgets, potential clients and proposed timelines, all of which can damage internal and external opportunities and workplace culture. 


There needs to be a better solution than creating new teams and effectively paying multiple times for the same tool simply to limit who has access to what while also needing to copy design systems across multiple teams which inherently leads to introducing changes that are not replicated across the design system elsewhere.

 

Proposed Solution

  1. Role based users in teams - owner, admin, manager, general, read owner
  2. Lock files based on role with default as general
  3. Lock entire projects based on role with default as general

Roles based users have existed across products for over 20 years, how is a multi-billion company like Figma unable to facilitate this feature? It’s been 4 years and there are 10 pages of comments and hundreds of thumbs up. For every person who’ve thumbs up or commented on this issue, there’s likely 10+ more who have the same problem and are silent. Please make an effort to address this issue. 

 

 

New Member
February 18, 2026

+1 | Please implement this feature now Figma. I've been waiting for it for years.

Hannah_Glasscoe
New Member
April 14, 2026

+1 here too, I can’t believe this isn’t available 😮

Norix
New Member
June 20, 2026

Still hoping Figma ships this natively, but in the meantime I put together a workaround that's helped me stop duplicating files.

I built a small Figma plugin called Framely. The idea: you "stamp" whatever frames you want to share, and it auto-generates a separate "Client View" page in the same file with live component instances of those frames. You share a prototype link from that page — clients see only what you've stamped, nothing else in the file. When you update a frame, the client view updates automatically because it's component-based.

It's not the same as real page-level permissions. Clients can't log in and browse pages freely — they just get a clean prototype URL with no Figma account required. It also doesn't help with the editor-access side of this request. But if your specific headache is "I don't want clients stumbling into my WIP frames via a share link," it does cover that case.

I'm still building it out — it's a side project from Hamburg — but the plugin works. please check framelyforme.com if you want to look.

Curious whether this kind of prototype-based approach would actually solve the problem for most people in this thread, or if the real need is truly granular per-page editor permissions.