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.

Come on Figma team, you can do it !

+1, I would love to have this feature.

This would be so useful!

+1 to this! Would be a very helpful feature so we can show clients a mockup without giving them access to our entire project.

+1 I concur completely

Hey!


A good option would be to make the entire list of pages visible on the left, but some pages would be in a disabled state (for example, gray and with a lock icon) for everyone except the editors of the file and so that it would be configurable in the menu by right-clicking on the page where there is functionality: copy link to page, rename page, duplicate page, delete page.


Thanks!

I would love that feature for clients. I want to give clients access to a specific page with the deliverables, I don’t want them to see all the work in progress, experiments, and assets which can be a lot and quite messy so it would be confusing to them and may also make an impression of being unprofessional/unorganized because not every client understands that it is a necessary part of design work.

Mind blowing that simple features like these not already exist…

There has to be a feature for Devs to see only the ready screens and nothing else…in large organizations the risk of a Dev using a different, not ready screen, is very high.


We need to be able to create shareable collections/folders where we can add different frames/sections/components/etc… and Devs should only be able to see the single items in the folder without being able to move across the whole file.


How is this topic from Jan '21 but not implemented yet…

Still, I am waiting for this option.

Would love this as an option. Often need to hide WIP pages.

I would to be able to hide certain pages within a Figma file as it gets a little messy when I want to brainstorm some ideas in the beginning stages for my clients but I don’t want my client to be able to see this stage. Then I have to create an entire new file and it gets messy with my font and colour styles being in a separate document when I want to edit them.


This hidden page feature would allow everything to stay on a single file and stay organized. In the version history this page would also only be allowed to be viewed by the page owner.

Yes! I feel this! Or I’ll be in the middle of testing different images/making a change and they are adding comments that they don’t like that image but I am not done testing different options I would love this absolute to hide certain pages for this reason!

Currently I started just making a whole new separate file - but this has been pretty irritating.

First, love the new pages within FigJam.


Would be great to have access enabled between pages, vs. at the FigJam file level.


For example, there are some great 1x1 templates that can be used from the library/community. I’m using FigJam for 1x1s, but have to create separate figjams for each team member. Would be awesome to just have ONE FigJam file, and each team member could have access and not be able to view other team members pages, which obviously have feedback specific to them.


This could also come in handy for restricting access to work, flows, retros to stakeholders as well, but selfishly - this could be super handy for internal-only information or manager-only information.


Anyway, just an idea!

Is there any update from the Figma team on when this will be a feature? On large projects I have to strip out sections that I only want people to see in order to protect the other pages. This is time consuming and can sometime break when copying and pasting out.


Thanks

The ability to lock pages within a file would be awesome, would be helpful for when you’re sharing a project with a client, but don’t want them to yet see the WIP work

At every project, every client, every week I need to be able to hide a page for the team until ready. It is so super annoying when you see people already hovering over the page you are working on!

It would be really great to hide pages

Hello there, I just found this webpage, there you can share only selected pages of your project:

monocle.magicul.io


work’s insane good.

But client cant add comments, just view rights.

How is this not a feature yet?


Just found out the file I was working on in drafts will not allow the copy/paste of comments along with the frames over to the file shared with stakeholders, so I will have to re-write them all. 😢

I agree! How is this not a feature yet?

+1 absolutely, we need more control

The lack of this feature is causing us a lot of problems, having duplicates, having to copy everything back and forth, not being able to copy comments, having double the amount of files. People have issues with this for 4 years already.

And instead, we get a floating-looking toolbar on the bottom, and so on… What a progress.

Reply


Terms & ConditionsCookie settings