Suggest a Feature

Hi Figma Team,  I would like to propose a new feature that allows users to lock specific sections within a Figma file to restrict visibility or editing access. This would be particularly useful for teams with multiple departments working on the same project, where certain sections may contain sensitive or confidential information.  The proposed functionality would include:  1. Section Locking: The ability to lock a specific section, preventing unauthorized users from viewing or editing its contents.  2. Access Control: Permissions settings to allow only designated team members or roles to access the locked section.  3. Toggle Visibility: An option to enable or disable the visibility of the locked section once the project is completed, ensuring flexibility for final reviews or presentations.  This feature would greatly enhance collaboration security and streamline workflows, especially in cross-departmental projects.  Thank you for consid

make it possible for the text layer to be selected not as a square, but in the form of text (enveloping the text)

Currently I can only define a variable with some absolute value or referencing it to another variable but I would also like to define it using operations on other variables. for example Total Fee Amount = 100000 Paid Amount = 20000 then Unpaid Amount = Total Fee Amount - Paid Amount

Since Figma has all of information regarding design and layouts. I like to reference @ Figma pages or components (in addition to  multiple references) so that I simply build it accordingly to the specifications within my Cursor. That way, the Claude LLM can produce the necessary code while adhering to the organization of my codebase.

I have a big icon library where every icon is its own component set with 9 variants. I need to add the same properties on all component sets. Bulk editing multiple component sets at the same time would be a huge time saver.

Because Figma only supports pixels, and we often have to translate pixels into other units for Fonts, etc., it would be great to document these conversions in the style’s description and have it show in the inspect panel. The description field is already available for editing in the style settings, so adding its value to the inspect panel would make it much more useful.

I spent a good amount of time searching for mockups that match the ones I’m presenting my work in. The device frames presented by Figma are exactly what I’m looking for. There should be an option to “Export with Device Frame”. The prototyping feature does already has a lot of device mockups with pretty good quality to showcase designs. Does anyone else feel that this would save them a lot of time?

It’d help to add “Scroll Behavior” option for the items in auto layout, which gives the option for Position Sticky either for Top or Left (with offset values) depending on the direction of auto layout (vertical or horizontal). This will make creating tabular / grid layouts with row and column freezes possible… especially when creating feature comparison layouts.

I’d like to request a new feature that provides more control over sharing permissions for viewers and Dev Mode users. Current Challenge:In our organization, we have internal employees and external agencies set as viewers, and we also use Dev Mode on an organization plan, where developers are automatically set as viewers as well. However, the sharing permissions for both viewers and Dev Mode users are currently bundled under the same settings. This causes issues because we need different levels of access control: Some viewers should be able to export files.Some viewers should be able to copy and share screen designs.Some viewers should only be able to view without any additional permissions.Feature Request:Could you introduce more refined sharing permissions that allow us to control these settings separately? Specifically, having distinct options for:😎 Viewers who can export files.😎 Viewers who

I’d like to request a new feature that provides more control over sharing permissions for viewers and Dev Mode users.Current Challenge:In our organization, we have internal employees and external agencies set as viewers, and we also use Dev Mode on an organization plan, where developers are automatically set as viewers as well. However, the sharing permissions for both viewers and Dev Mode users are currently bundled under the same settings.This causes issues because we need different levels of access control:Some viewers should be able to export files. Some viewers should be able to copy and share screen designs. Some viewers should only be able to view without any additional permissions.Feature Request:Could you introduce more refined sharing permissions that allow us to control these settings separately? Specifically

Can Figma create a feature when we click a link in Figma that navigate to the design page, then will appear "Return to Link" like "Return to Instance" in component feature? 

 The User Enter Page Manual helps us navigate any page.  

I like shortcuts, but… Some Figma shortcuts override my keyboard layout shortcuts. For example:“OPT+<” or “OPT+>” to insert quotes like this « ». But in Figma its letter spacing controls. “SHIFT+OPT+<” or “SHIFT+OPT+>” to insert quotes like this „ “. But its line-height.Those shortcuts frustrate me, so I want to disable it. Other ones are quite nice.

Make it possible to download comments in the same way as local versions of files are downloaded, with the ability to also import comments along with a local file, now I transfer all comments from one file to another manually, also between pages in files, this is very inconvenient, and does not simplify the task

While I can link width and height to variables, it can be hard to get complex components to scale correctly using them. Having a scale variable that behaves just like using the K key would make things a lot easier. Unlike using the K key it would need to remember the ‘base’ 1.0 scale of an object.

Would be extremely helpful to have the option to always show min-w and max-w in the sizing panel! Selecting the dropdown takes forever. Thanks!

If you copy anything as a PNG, it defaults to 2X size. The problem I’m running into is that I’m copy screenshots from Figma into other tools like Axure all day long. Since “Copy as PNG” only copies at 2X, I’m constantly needing to group objects and create export settings unnecessarily over and over.I’m hoping for one of these solutions somewhere. Ability to “Copy as PNG 1x” with the existing “Copy as PNG 2x” Ability to choose a preference for “Copy” options Ability to respect the export settings of the parent frame when copying children (so I don’t have to recreate export settings repeatedly)Does anyone know if any of these are on the product roadmap to address? Or if something exists that I just haven’t found. I’ve seen this issue come up in forums a few times. Thanks for any help or tips anyone might have.

Hi, Updating components slows down the inability to browse other components from the open review detail of a component. I would also expect the possibility of browsing components in the detail.     Furthermore, if I update all instances, a button to move to the next component appears. However, it does not behave in such a way that it moves to the next component, but to the first, which is strange. An example of use is if, for example, I have the first component in the change list, where there are 300 occurrences, but I want to skip it at the moment, I go to the detail of the second component, update it, but then I have to go back and deal with the second component again.  

It would be great to be able to add a note when declining someone of Figma access, so I wouldn’t have to write separate email with explanation of decline decision. 

It would be convenient if we could inherit the code syntax from a referenced variable. It makes sense that the variable codeSyntax is interpreted out of the box, but it would be very convenient to inherit referenced variables in some scenarios. We have a variable collections for designers to control color from a matrix using variable mode. When inspecting the variables in use it would only output --background, --text because this is the name of the variable, but in reality these variables reference variables with other names and codeSyntax. These variables would look something like this:--ds-color-accent-background, --ds-color-neutral-background. This would also be the variable used in code. Whats your thoughts on this? 

Is there a way to create variables for axes like width, grade, and slant? Or is the new typography variable support currently limited to the following: → Font family → Font weight and style → Font size → Line height → Letter spacing → Paragraph spacing and indent

Currently, if you would like to bold part a text using a certain style, you have to create an extra style with a different font-weight, then jump into text styles and pick a bolded one. Things get crazier if we would like italic, underline, strikethrough as well… 🤯 Fine. But this is not how coding works (something you’re trying to align to). Usually*, we can just mark part of a text in styled with only font-weight property. Something similar is required in Figma with the ability to assign shortcuts so we can easily use i.e. ctrl+B / cmd+B to assign bolded sub-style. Just like all your users work with text in any other software. Optionally, these could be just pre-made options to pick (bold, italic, underline, strikethrough). *I’m a designer not engineer though

I have noticed that it is not possible to assign specific variables from a component to the internal components that make it up. For example, in a component composed of multiple internal components, you cannot assign a text variable from the main component to its subcomponents. This creates an issue when a property, such as a text variable, needs to be changed in multiple places simultaneously, as it must be manually updated in each internal component.It would be ideal if the system allowed assigning specific variables from a component to its internal components to streamline the management and editing of shared properties.

Record Prototype | A feature I wish existed in Figma 🎥. Adobe XD released this many years ago and had the time to die before it even existed in Figma. 🤷‍♂️. So, what’s stopping Figma from doing it?

I couldn’t find a similar thread, so I’ll just post it here. Here’s what’s InVision Studio does great: The idea is to be able to define when each layer is to be triggered when using smart animated. Currently there is only a global switch and all layers will animated in a given time. If this idea is a duplicated of one I