Skip to main content
Question

Bug Report: Issues with Multi-Account Switching and Session Management

  • May 15, 2026
  • 3 replies
  • 125 views
Sushi

Dear Figma Support Team,

I am writing to report several issues I’ve encountered while working with multiple Figma accounts simultaneously. These problems started recently (possibly after a recent update) and are significantly impacting my workflow. My colleagues are also experiencing the same issues, suggesting this is not an isolated case.

Issue 1: Authentication Failure via App-to-Web Redirect

When I click on an account in the Figma desktop app to log in, it redirects me to the web browser as usual. However, even after completing the login process in the browser, the app often fails to register the login. I have to repeat this process 2–3 times before the account successfully logs in.

Issue 2: Loss of Seamless Session Recovery for Multiple Accounts

Previously, if I had multiple files open from both Account A and Account B and my computer went into standby, I could simply re-log into both accounts upon waking the device to continue working. Now, even after logging into both accounts, the open files do not refresh correctly. The system forces me to close the files and manually reopen them under the correct account context to view or edit them.

Issue 3: Failure to Automatically Detect Corresponding Accounts

The system no longer seems to automatically recognize which account should be associated with a specific file. For instance, if I open a file belonging to Account B, the system mistakenly attempts to view it using Account A's credentials. This cross-account confusion was not an issue in previous versions.

These bugs make it extremely difficult to manage complex projects across different accounts. Given that this is happening to multiple people on my team, could you please investigate if these are known bugs or if there is a planned fix for session management?

I look forward to your assistance.

Best regards

3 replies

ksn
Figmate
  • ksn
  • Community Support
  • May 15, 2026

Hey ​@Sushi -- thank you for checking in. A recent update could definitely be a factor, but there are a few other things worth checking on.

You mentioned that your colleagues are experiencing similar issues, so want to check on some things:

1. Are you all logging in through an SSO provider (Okta, Google Workspace, Azure AD, etc.) or standard Figma credentials?
2. Did anything else change around the same time — new device, OS update, or any IT/admin changes to login policies?
3. Does this happen on the Figma web app too, or just the desktop app?
4. Does the issue occur when using a personal (non-org) Figma account on the same machine?
5. How many accounts are typically open at once when this happens?

If you also have time, can you (or your IT team) review our section on login and authentication? There may be some hint as to what may have happened there as well: https://help.figma.com/hc/en-us/sections/4403936348311

Sushi
  • Sushi
  • Author
  • New Member
  • June 12, 2026

Thank you for getting back to me. Here are the answers to your questions:

  1. We all log in using our Google accounts.

  2. No, there haven't been any changes to our devices, OS, or IT/login policies.

  3. We typically use the desktop app, and that is where we are experiencing this issue.

  4. The issue happens whenever we try to switch between accounts.

  5. We usually have two accounts open at the same time.

Since we have been using Figma for several years without any changes to our login methods or settings, and this problem only started occurring recently, we suspect it might be related to a recent update or a backend issue. Could your team please help investigate further on your end to see if you can identify the root cause?

Thank you very much for your help!

adamsmasher
Figmate
  • adamsmasher
  • Figmate
  • June 12, 2026

Thanks so much for the detailed breakdown, @Sushi - stepping in for @ksn. Thank you for reporting all three issues together like this. It’s really helpful, and I can totally see why this is disrupting your workflow, especially when it's happening across your team.

I have some extra steps that you might want to try which have helped resolve the authentication issue (Issue 1) for others in similar situations. Even if the root cause turns out to be something else, it’s good to try these first if you haven’t yet:

  1. Try logging in through a different browser first — in some cases the browser itself is the culprit.
  2. If the issue persists across browsers: relaunch your browser to clear any pending updates, then log out of Figma on the browser, clear the browser cache, and disable browser extensions.
  3. Fully uninstall both the desktop app, then reinstall
  4. Log into Figma on the browser first, then open the desktop app and attempt login

If those steps don't help, I’m going to help make a ticket for you with our Technical Quality team so they can get debug logs from the desktop app and help you further. 

For Issues 2 and 3 (session recovery after standby and files loading under the wrong account), I’d like to understand the pattern a bit better. A couple of questions that would really help:

  • Are Issues 2 and 3 happening consistently, or intermittently?
  • When Issue 3 occurs (wrong account loading a file), does manually switching to the correct account and reopening the file resolve it?
Terms & ConditionsAccessibility statement