Skip to main content
Lishay
January 30, 2021

Give unique access to specific pages

  • January 30, 2021
  • 244 replies
  • 61282 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

james_work
June 20, 2022

It’s shocking Figma doesn’t already allow for this. Design files have so much in them. Lots of noise.

We need the ability to hand off only a dedicated page for dev. Or only a allow a dedicated page inside a document to be viewable via a link.

Magdalena_Geissbauer1
New Member
June 29, 2022

Yes, please. That would be an amazing feature. Especially giving customers access to special areas/screens. They don’t need to see all the component variants and work-in-progress screens.

That would be a life-changer.

Hamza3
July 5, 2022

Can anyone guide in view only option we see padding issues like we see different paddings than edit file i mean like for example an icon in a container but when we select it selects the icon only and shows its padding and its different from the one with edit access

Matylda_Nowacka
July 5, 2022

yeah, would be great to have this feature! Also, because we could have limited access to pages that shouldn´t be edited in within the file, but could be reviewed by other team members!

James_Kelly1
July 11, 2022

Seems like a lot of us would benefit from this amazing new feature

Do we know if it’s on the roadmap yet?

Ben_Ford1
July 28, 2022

Still a problem for us. PM, PO and Dev are struggling to find certain screens/frames within our Pages. Our pages tend have 30-50 frames, and we often need to share a select number of those frames (not always in order on the Page) to other team members. At the moment we’re having to share individual links to individual frames to ensure the team are looking at the right frames.

yahya_shafqat
July 31, 2022

It’s honestly weird for me that a tool like figma, which is based around the concept of sharing and easing team work flows would not include such a basic feature. Its less a feature at this point and more a neccessity. I hate it when clients can just hop in any time to see the progress we’ve made and some of them are salty about the progress for they do not understand that some things take longer than others. Ugh. its super frustrating. I hope it’s something an add on can fix. If it is something that can be fixed with a plugin, I’ll make it and update everyone here

Sam_Burnard
August 3, 2022

Unique links to pages would be a real game changer!

Hope this gets implemented soon, as our current solution is to create a new Figma document just for client review.

Poggs
August 5, 2022

I’m also looking for a way to allow a client to view and comment on artwork in Figma, without being able to see any other pages or content.

I was thinking of creating a simple prototype page within the file - containing either individual frames (so, separate flows which would be selectable via the proto’s left-hand UI panel) or grouping multiple artwork frames within one container to see everything at once.

I figured the ‘original’ artwork could be turned into a component; an instance of which would be placed within the proto page. If you wanted to keep the design synced, leave it as an instance; otherwise, detach it. A protoype link with the “can view prototypes only” setting would be generated and shared as required. This process could be repeated for each design iteration using new pages (and, subsequently, new proto links).

Is this wrong? What am I missing? 🥺
(I love Figma - but even after 2 years of using it daily, I realise how little I actually understand it!! 🤣)

Alice_Curioux
August 17, 2022

+1 - want to share my finalized work with the developers but not work in progress