Skip to main content
Natalie Braun
Natalie Braun
New Member
May 14, 2026
Question

Removing a figma user resulting in files with no ownership

  • May 14, 2026
  • 1 reply
  • 247 views

Hi! We’re seeing an odd issue and have blurred the user and organization for what is being removed. When removing a user, Figma shows a message saying 43 files will have no owner and 33 drafts will be moved to Unassigned. However, this user was not the owner of any files.

Do you know why Figma is reporting this? Is it simply aggregating all unowned files and drafts or is this a bug?

 

    1 reply

    ksn
    Figmate
    ksn
    Community Support
    May 14, 2026

    Hey Natalie! Thank you for checking in on this one. This one is a bit interesting, and I think there are a couple of things that could explain what you’re seeing.

    Even if this user didn't explicitly own any files, ownership can sometimes be transferred behind the scenes — for example:

    •  If a previous owner was removed from the org at some point, this current user you are removing may have inherited those files without them realizing it.

    Another possibility is that those files were already ‘orphaned’ within the org before this removal, and they are bringing it to your attention now, even though they aren't directly connected to this user.

    When a member is removed, their files will not automatically be given a new owner, which may also be contributing to the message you're seeing. This page on removing org members has more context on that behavior: Remove people from an org

    These are just my initial stream of thoughts, and it can be something completely different.

    My recommendation at this time is to contact our support team so they can take a look at the list of files that are being counted in this toast -- I don’t have the ability to deep-dive into this directly, but I can make sure you get help.

    PM me your email address and I’ll get a ticket set up for you.

      Terms & ConditionsAccessibility statement