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

Jess_Veitch
March 31, 2023

I often want to set up my file at the start of the project, with all pages that will be needed through all the design phases, however feel that it can confuse clients to have empty pages. Would be amazing if you could hide/show pages to people outside of your team.

Celine_
Figmate
Community Support
March 31, 2023

Hi @Jess_Veitch ,
Others in the community have requested something similar here : Giving unique access to specific pages .
I am merging these two topics, do not hesitate to vote up top, so we can gather all the feedback and interest from the community.
Thank you!

April 4, 2023

As of today this has 732 votes. If this hasn’t been actioned @Figma_Support please communicate to the community as to why so we can understand the challenges faced 🙂

djv
Figmate
Community Support
April 4, 2023

Hey @Jacques2,

As I mentioned 6 days ago, our team is fully aware of this feature request. We’re already working on it - we just don’t have an exact timeline.

Geeta_Jeevaratnam
New Member
April 5, 2023

Yes please - would be handy to give engineers access to the handover page only.

Lishay
LishayAuthor
April 16, 2023

Good to know. Thanks for updating us

Catalin.D
May 8, 2023

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.

Jordan_Kersey1
May 26, 2023

@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

Prabhakaran
New Member
June 5, 2023

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.

June 20, 2023

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.