Hey Henry,

Thank you for your feedback. It's not possible to access an employee's drafts—these remain private by default. 

Only the draft file owner and anyone who are explicitly invited into these files will be able to see it. Unless the user moves the Drafts into a Team or Organization project, it won’t be visible to admins.

If greater visibility is important, you might consider encouraging your team to:

• Create new files directly within a team instead of in drafts.
• Or move files from drafts into a shared team or project once the work gets started.

Hope this clarifies!

I suppose I’ll turn this into a feature request then!

In an enterprise setting there’s really no need to have private drafts - everything they make on their work device or work Figma account will belong to the company anyway and in a lot of secure environments it’s a real risk to allow people this kind of private access.

Having to constantly remind people not to create private drafts is a pain and we end up reminding ~40-100 people every single month to move their drafts.

Enterprise admins should have access to all content created.

Thanks for bringing this up! I totally get how draft visibility can be a challenge in Enterprise settings. While drafts are private by default, we can see the need for more admin control. I’ll go ahead and share your feedback internally and mark this as a feature request for our team to consider.

(Just a quick another note: as mentioned earlier, admins can't view drafts created by active members. However -- if you are not already aware of this function--, when someone has been removed from the Organization / Enterprise, you can manage their drafts to get access to them. You can read more about that: ‘Manage drafts of removed users’.)

Thank you again for your feedback!

This really needs to be addressed as it can be a security and intellectual property risk. I’m surprised that Figma didn’t consider this for Enterprise plans. I should be able to have access to any file created within a company account. This should not be put in the classification of a feature request but a security update.