Skip to main content

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.

@anon21722796 Can you please add this feature to your New-Year’s resolutions? Since Zeplin is changing there pricing plan, we’ll need to find an other developer-hand-off tool. Figma would do this perfectly if only we had the option hide some pages for those with only viewing access.


+1

For me, I have a master file that contains a lot of my “pages” which are irrelevant to designers that are assisting with the project. If I hire a remote designer to help with ‘xyz’ then I want to give that designer access to ONLY that page, and nothing else. Privacy content and other stuff that I’m not too eager for this contractor to get access to. This feature will be great for agency or startups too, not just internal teams with stakeholders.


Please @anon21722796 is this something you’ll be working on?


Thank you!


@anon21722796 Can you please add this feature this year?


As a designer I regularly run into a situation where I discussed designs with the team and start working on iterations on a new page in the same document. I want to be able to hide that page from team members until I am ready to discuss it again.


Often after I discussed designs team members start watching new iterations. That to me feels intrusive. My work around is copy everything to a new document. And copy paste it back into the original document when I am ready to discuss it with the team.


So being able to hide/unhide a page would be a perfect solution for me.


Cheers,

Martin


I’m quite surprised that this isn’t a feature already.


Is it in the backlog or on the roadmap @anon21722796?


@anon21722796 this would be very, very helpful!!!


After many years I’m about to switch from Sketch+inVision to Figma. I was able to determine exactly what to publish on inVision (version/handoff for implementation or just a presentation for a marketing department).

I consciously want to show decision-makers (management, marketing) only what is necessary to save their time and not create confusion. Decision-makers also do not need any insight into components and other assets.


I was very surprised that there is still no function in Figma to simply mark a page as hidden for others.


Hey all! I have an option for this workflow, and would love to hear what you all think.


As many of you pointed out, you can copy a Figma link that points to a specific area:



  • The entire Figma file

  • A page in a file

    copy-link-to-page

  • A prototype in the file

  • A specific frame in the file (this include frames within frames)


Once you have the link, you can embed that link into any browser-based tool as a live preview. I walk through this exact workflow in this video (timestamped at 28:20). Some key callouts:



  • If you paste the link to the page inside a doc, while it will the land on the page, the viewer will still be able to view other pages. I’m not sure if this was intended, and I will look into this more.

  • However if you link just the frame, the embed will only give the viewer access to the single frame. They will not be able to see anything else in the embed except the frame. Let’s say you have a flow of screens, you can embed each screen as a single frame in the doc and lay it out in the doc for your audience. I favor this flow because it doesn’t force a stakeholder to enter a Figma file to view the screens. Perhaps they are more comfortable in their own tool of choice. Meanwhile, any updates you make to the screen will update live in the embed as well.


A workflow I didn’t cover in the video is to embed into a FigJam file. Taking that same example, I might embed a single Figma frame into a FigJam, where I’ll string together a series of screens to represent a flow. This workflow can be nice if you want to invite feedback in the form of stickies, stickers, etc.


If you have a ton of screens you have to share, I understand this isn’t ideal to get a link for every frame. In the same video, Kelly shared a shortcut that can make it a bit faster to grab those links if you’re using the desktop app (timestamped 12:26).


I know the team is thinking heavily on this problem, but I hope this workflow can help in the interim. Thanks for chiming in everyone!


Love the collaboration level here on Figma. But when working with Clients / Developers I like to reveal my designs piece by piece as it’s ready. Otherwise it causes confusion and unnecessary explanation of “why this design doesnt work” even if I wasn’t planning to share it with client.


I wish there was a way you can “reveal” a page once you’re ready or make an artboard “public” when it’s ready to be reviewed.




  1. There are lots of times where there are multiple pages in the file but when there is a review not all the pages need to be seen. Sometimes it’s research pages, inside information pages or work that are still in the process and do not want to reveal them yet.




  2. Has anyone else experienced the need for this? Do you think adding an option to hide pages is relevant?




+1 I would really like to see this feature


+1 also from my side!


Yes, yes, yes!


We need this feature. I know that Figma it’s amazing for inside product design, but for outsourcing, we need this extra feature.



Hell yeah!


As a new user of Figma, coming from a combination of Sketch + Overflow, the ability to have unique pages just being shared out of all the pages on Figma file is a must.


A lot of times you just want to have someone, that is not proficient into a design tool, to just see and evaluate something in a simpler away without the clutter of other pages or Interface elements.


It would be the same ability that Overflow allows to generate a simplified, “clickable” and “navigational” wire flows for example. This would be a great addition to the platform.


+1 to this. Would be great!


I need this. A lot of clients want access to Figma, maintaining two files is more work and can be messy, and giving them access to the file where I do all my work feels really invasive.


My current workaround this is to keep your work in a separate page in the file, select all and hide everything you want to keep private. I also name the page with a comma or dot so it looks like a blank page. Obviously this isn’t the best solution because when you do want to work on it, people will be able to see what you’re doing if they’re in the file at the same time, but it still sort of works


Nice but it’s hack, we want (need) a built-in solution here 😋


Let’s make this happen @figma 😩 I’m still downloading copies of files to ideate in a space without a scrutiny ……!?


Still such an inconvenience right 😦


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.


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.


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


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!


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


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


Reply