Skip to main content
mcram
March 11, 2021

Lock pages

  • March 11, 2021
  • 28 replies
  • 7078 views

Of course it is easy enough to lock layers but I think that it would be helpful to be able to lock pages in a fashion similar to the layers.

I often place root (master, main, og?) components on a separate page and it would be nice to be able to lock these pages to keep items from moving around without intention.

28 replies

Bart_Oosterveer
March 18, 2024

We use Figma and also share full boards with clients, support and or teams. Not everyone needs acces to every page but keeping everything in one file with the ability to lock is a must have. +1

April 18, 2024

It would be great if you could add a feature that allows users to lock pages.
Exactly or similar as it exists for locking layers.

Here’s the use case/reasons why this would be super useful:

During a design process we usually split tasks over separate pages for example:
Page 1 - “Round 1 - Design Explore”
Page 2 - “Round 2 - Refinement”
Page 3 - “Round 3 - Delivery”
At each stage we ask the client to comment on the work.

At large organizations/with many approvers and projects that span longer timelines, it often happens that comments are left in what we consider an “OLD design” (=an outdated page). In the above example, we would have already addressed the comments from Page 1 and 2 as we are working on Page 3.

So the only place where new comments should be placed are in the most current Page 3.
Yet it happens often what people catch-up on progress shares via their Figma email notifications, where they click on an outdated Page link (i.e. Page 1 or 2) and they land in these pages where they start to add comments. Essentially in the wrong place, where they don’t realize that things have already moved on to Page 3 - “Round 3 - Delivery”.
This especially happens with less Figma savvy folks.

If we had the feature to “lock a page”, the approver could still land on that outdated page, see the content/design but the page lock would prevent accidental comments in the wrong stage of the project.

If the page was locked for commenting, the approver would likely reach out to ask where to leave comments, which would allow us to remind them that work has progressed and we could share the actual page link with the most current work where they can still leave comments.

It goes without saying the “lock” feature should of course allow a simple “unlock”.

Alternatively, if a full page lock seems unpractical, perhaps a “comment lock” for discrete pages could be an approach. I.e. if a user wants to leave a comment on a page that is considered out of date, a prompt would appear that states “The commenting feature on this page has been disabled - please check with the seat holder or perhaps …” Something along these lines.

Many thanks.

July 19, 2024

Locking should also keep it from taking component updates. This would allow it to stay in sync on the page that represent the live on site design, while we update component for the new design version page.

Marcus_Bakke
July 23, 2024

Hi,

I’m not sure if this idea has been discussed yet, but I really miss the ability to lock specific pages in a Figma file while sharing, especially for larger files. I know it’s possible to share individual pages, but often I have many pages in one file and only want the client or partner to see selected ones. Sharing one page at a time can be quite time-consuming.

As far as I know, this isn’t currently possible. If anyone has developed a plugin for this, please let me know.

I appreciate your help and keep up the great work!

Kind regards,
Marcus

James_Walsh
New Participant
February 27, 2025

Being able to hide in progress work from stakeholders would greatly improve our client delivery process. +1 for this.

Salvador1
New Member
May 6, 2025

I love this idea! Currently how I structure some projects I have pages set up for concepts, the stages for each proof (proof 1, proof 2 and so on), and releases. If I ask leadership to review and comment on Proof 2, and I’m starting proof 3 they’ll start noting or making changes on proof 3, why? I don’t know I’m sure curiosity kicks in and they feel it’s best to comment there. I also see the need for this when I have a page for components that I would prefer others to not have access too. 

 

To try and combat this at the moment I have a file I named playground in my drafts and I do everything there and then have to copy and paste it into the project. It would be nice if I didn’t have to do this.

James_Walsh
New Participant
February 26, 2026

Locking should also keep it from taking component updates. This would allow it to stay in sync on the page that represent the live on site design, while we update component for the new design version page.

Being able to “Publish” a client visible version would be amazing. 

Grace Banks
New Member
May 13, 2026

^^ same. Even the most basic of functionality would be AWESOME and super appreciated.