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.
Page 6 / 9
Good to know. Thanks for updating us
Please make this happen… Not sure how it wasn’t included by now. The initial request was made back in 2017… That’s crazy.
Right now because I have a huge library premade I don’t want to grant access to my clients to those types of files. It’s pretty annoying that I have to have a duplicate file, one for me and one for the client.
@Catalin.D -I just found this thread for the exact same reason as you, with hopes I would also find a solve scrolling to the bottom here. For me I have an old system we’re updating to a newly rebranded one, theres some systemic disconnect in the company, and I’m new, so I wasn’t given a lot of time, and didn’t know about the rebrand until 2 weeks into working here after I had started to develop a design system. So a lot of my components and pages aren’t ready yet. The way I have currently solved for this is by putting a big red circle emoji at the front of the pages that arent ready, and green for those that are, so people coming to the system as its a WIP updating to the new brand, users at least know which of these is up to date and which aren’t, but being able to hide them from other users would be SO clutch, just like hiding components, only page based.
HOWEVER … I did just think of something you could do - you could use the rename it plugin to select all the components within a page and add the . in front of the layer name for everything, thus hiding it at a system level
In our team, we use Figma full-time. However, when content writers review designs, they review separately and provide the content to the designers again. This results in the designers having to add the content to the design file again, causing unnecessary repetition. Therefore, having edit access for content writers would be very useful for us. However, we cannot give them the same edit mode as our designers. Instead, we suggest adding a box to the properties area that will allow content writers to make changes and save . This way, it will be clear who added the content and it will notify the original file owners.
Could someone from the Figma team share some workarounds or ideas to help in the meantime? I need to be able to manage our road map and link to specific sets of screens for developers, and I need to be able to send specific sets of screens to stakeholders without dropping them into the entire Figma file. What is the ideal way to do this? Our team wants to switch but we’re sticking with Sketch + inVision until this is worked out.
Congratulations! This is now available through dev mode
I saw the new dev mode, but not sure how this solves the issue. Can you please explain?
So it doesn’t give unique access to pages but by adding sections to dev mode, you can make it easy for your developers to find what is ready for handoff by marking it ready for dev.
I guess in the future they can add the option to hide everything that is not marked as ready for dev as an additional feature
There’s this topic as well and has 400+ votes on it. Maybe merge those two as both threads essentially ask for the same thing?
+1 unique access to specific pages
I need this now! I literally just had to explain to the PO not to comment on old pages on the left of my design because the a11y annotations may bet updated there instead of a later page (where the devs will see the change). LAME. Please give us page by page permissions.
🙏 🌝
Been following this thread for a while now, we just release a tool that allows you to create shareable links for Figma design and hide specific pages, check it out here:
I would love to hear your feedback and what features we should add.
this is great! is there a way to do this with Presentation view?
Great initiative and It works super well, the only thing missing for me is access to Figma Toolbars (layers / inspector etc.)
+1 for unique access to specific pages
It could be really beneficial in particular for small projects in which the freelancer is in direct contact with their customers and to co-design the project together. Thumbs up for this idea.
C’mon Figma, the people have spoken!
Is there a way to share a link with a client that only gives them viewing access to a specific page as supposed to being able to view the entire project?
Yes please!!! It´s an issue since two and a half years!
Not at this moment but we will pass along to our team for consideration! Others in the community have requested something similar. Feel free to vote up so we can gauge the overall interest in the community here: Give unique access to specific pages
(Tips: The best workaround right now will be to separate out the information you want to share to a separate file and only share that.)
This would be so helpful. It’s really frustrating to have clients peeking at work that isn’t ready for them.
I have to say I had hopes that Figma would take steps to improve this long time ago 😑
YES, this would make getting feedback from clients so much easier! Especially given there is no real workaround right now.
If you could at least copy comments from one file to another, then you could duplicate your file, remove all the pages you want to hide, receive feedback on the duplicated file, copy the client’s comments over to the original Figma file and work on from there.
But not even this seems to possible, so giving unique access to specific pages would make a huge difference! 🥹
I needed this today so badly! Had no idea that when I share page with ‘view only’ it shares all pages .
This would be a very helpful feature. I would prevent making extra project files just to share a specific part of the project with the client.
