Skip to main content
Question

Why do some files become ownerless even though the original owners are still active team members?

  • September 4, 2026
  • 1 reply
  • 9 views
Reina00

Hi Figma Support,

We are investigating several ownerless files in our team and found the following documentation:

  • Remove access to teams
  • Files are missing after remove the member from the team
  • Ownerless File – Can't Claim Ownership as Team Owner

Based on the documentation, we understand that files can become ownerless when the file owner is removed from the team.

However, we noticed a different situation in our workspace:

  • Some files are showing as Ownerless Files.
  • The original creators of those files are still active members of the team.
  • These users have not been removed from the workspace or the team.
  • In some cases, the files were created directly within team projects.

Could you help clarify:

  1. Besides removing a user from a team, what other situations can cause a file to become ownerless?
  2. Can moving files between Projects, Drafts, Teams, or Workspaces cause ownership to be lost?
  3. Is there a way to identify the original owner of an ownerless file?
  4. Is there any supported method for restoring ownership to an ownerless file?

Any guidance would be appreciated, as we are trying to understand the root cause and prevent this from happening in the future.

Thank you.

1 reply

djv
Figmate
  • djv
  • Community Support
  • September 4, 2026

Hi ​@Reina00, thanks for reaching out! 

I understand the confusion here, so I’d be happy to help clarify. To answer your questions:

  1. There are a few situations can cause a file to become ownerless, even when the creator is still active:
  • They were removed from that specific team, but are still active elsewhere in your workspace. Team-level removal strips their roles on that team's content.
  • Their seat was downgraded from Full to View. The owner record still exists, but they can no longer act on the file, which often looks like ownerless in the share modal.
  • The team or files were migrated between plans or organizations at some point, and the original owner was removed after the move.

There's also a common look-alike worth ruling out: folder owners inherit ownership-level permissions over the files inside them. So a file can appear to have "an owner" via the folder while the file's own owner record is separate. If your folder structure changed recently, some of what you're seeing may be this rather than lost ownership.

  1. Does moving files cause it?
  • Moving a file between folders, teams, or workspaces does not change its owner. Ownership and location are independent (Transfer ownership of files or folders). The one exception is moving between accounts by exporting a .fig, which drops permissions, comments, and version history entirely.
  1. Identifying the original owner
  • There's no self-serve way to surface this from the file itself today. On Enterprise, your Admin → Activity log is the best starting point — filter by the file and look for role or membership changes around when it went ownerless. If the log doesn't show it, our Support team can look it up directly.
  1. Restoring ownership
  • Only the current owner can transfer ownership, so there's no admin-side reassignment today. Two practical paths:
    • Best case: if the original owner is still active, have them open the file and transfer ownership to a long-term owner. Since they're still on your team, this is fully self-serve and the cleanest fix.
    • Interim: an ownerless file is still fully usable — existing editors keep full access, and links and library connections are unaffected. Assigning a stable owner to the parent folder also gives that person ownership-level control over the files inside.

Hope this helps, but if you have any specific files that you’d like to investigate further, please let me know. I can help get you connected with our support team to take a look at your account. 

Terms & ConditionsAccessibility statement