Skip to main content
Question

Setting enablePrivatePluginApi to true on a community published plugin


Maksim_Petriv

I have a plugin that is approved and published to the community and I need to set enablePrivatePluginApi to true. I need this setting turned on it seems in order to get the fileKey value from within the plugin. According to this doc Plugin Manifest · Figma Developers

What are the implications of turning this value on in the manifests file on an already approved and published “publicly accessible” plugin. Would I need to go through the approval process again? Will my plugin now become only a team plugin and become unpublished from the community.

6 replies

Adam_Ginsburg

@Maksim_Petriv FYI I posted related question here Slack


Michael_Gubik

If there’s an answer in the Slack can you please share it? It’s not publicly accessible


Gleb
  • Power Member
  • 4708 replies
  • June 2, 2022

You can’t set enablePrivatePluginApi to true on a public plugin — that was the whole reason this option was needed in the first place. File key is not accessible to public plugins by any means as it would be a security consern.

Here are the answers from slack:


Michael_Gubik

Thanks, the reason Jonas gives is what I had feared. This is quite limiting though. Without changing the current API, Figma could just display an alert saying: “Sharing the file key with this plugin will give the developer perpetual access to this file. [ Share ] [ Deny ]”

How can I get a rendering of a frame without the file key?

Also there should be some explanation in the docs for fileKey.


Adam_Ginsburg

@Michael_Gubik we had to do a “dance” and get the user to enter the filekey to have a published plugin - you can see it working in our plugin Buzzy - No Code App Builder | Figma Community


Gleb
  • Power Member
  • 4708 replies
  • June 9, 2022

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings