Behind the feature: building multi-account

Today, we’re launching account switcher, streamlining the experience of navigating across different accounts and workspaces in Figma, while still unifying your work under one single profile in the Figma Community. Product Manager Ben Stern shares how delivering on a seemingly simple user request required navigating a surprising amount of complexity: the technical foundation, design explorations, and building towards a new north star, while solving for short-term needs.

While Figma is most often used for designing and prototyping, we’ve long used it internally for everything from brainstorming creative concepts to building slide decks. Increasingly, we observed users relying on Figma for so much outside of product design, like creating digital maps, developing vector artwork, planning a wedding, and even making fan art. Figma has become a home for projects at work, and a space to create outside company walls.

Art from Figma Community member Dinara Nikolaeva

So, when Director of Product Sho Kuwamoto asked users on Twitter what they’d like us to add or change in Figma, it was no surprise that support for multiple Figma accounts was top of the list.

A new paradigm

As we scoped this feature, we knew that user feedback would be a driving force. More than anything, we heard that users have many roles—employee, freelancer, hobbyist—but no simple way to move between these different identities. Instead of resorting to complex workarounds, they needed to easily switch between workspaces, depending on whether they were creating designs at work or during off hours. 

And creating work has different requirements than sharing work. While users need to move freely between accounts as they’re designing, they also need to have choices around how that work is packaged and attributed. Many Figma users maintain a public profile in the Figma Community, sharing their work, managing comments, and connecting with others under one handle. Keeping personal files separate from work projects is important, and equally critical is allowing users to maintain one public brand as they change jobs or roles.

Rethinking the 1:1 model

Among the many things that the enterprise team is tasked with, authentication—the concept of recognizing and verifying a user’s credentials—is top of the list. Authentication is usually synonymous with security, but it also ties to identity. Most product assume a 1:1 model, that one user equates to one account. Companies like Slack, Google, and Instagram ultimately supported multiple accounts as user needs evolved, but they started with one account at launch.

Since the Figma editor is the hub for creation, and the Figma Community is the home for publishing work, we needed to consider both spaces. While we’d want to allow toggling between separate accounts in the Figma editor, in the Figma Community, it would be important to unify all accounts under one profile. What complicates this even more is ensuring that work projects respect the walls of a company, while still allowing for easy access and switching between personal projects. 

Our goal was to help people work in Figma in a way that reflects all the facets of their work—both inside a company and outside of it. It was time to move away from the paradigm of one person per Figma account and make switching between contexts easier and intuitive. 

Some early explorations on how to indicate where a new file would be created and what this experience would look like in our desktop app

Designing towards a north star

With this in mind, we started designing. But once we actually mapped out what this new paradigm might look like, we quickly realized that the “one user, one account” model was baked into the file browser UI, not just the technical infrastructure. If we were to add on support for multiple accounts based on the previous version of the file browser, the UI would be clunky, at best—not to mention the broader under-the-hood technical challenges. To accommodate a new account switching feature, we’d have to re-examine the whole information architecture (IA) of the file browser.

So, we needed to arrive on a long-term direction of the file browser, while also making changes to address user feedback in the short-term. Our new north star? A hybrid model, allowing users to access multiple workspaces in the Figma editor, while maintaining one single Figma Community profile.

As we thought about how to build this, we needed to be conscious of what it looks and feels like to go from one single identity (the Figma Community) to multiple identities (the Figma editor). We would have to make the Figma Community feel separate enough from the Figma editor, while still being cohesive from a design perspective.

UX considerations were top of mind:

  • Managing tabs: We didn’t want users to have to close and reopen their tabs each time they switched between accounts. Instead, we made it possible to keep tabs from different accounts open at the same time, in the same window. To make it clear which account is open in a given tab, we added an icon in the center of the editor that shows which account the file belongs to.
  • Installing plugins: We heard from users that they want to access all installed plugins, even when signed into multiple accounts. Now, if a user has multiple Figma accounts connected to one profile in the Figma Community, clicking “install” adds the plugin to all connected accounts.
  • Naming workspaces: Previously, accounts outside of an org account were called “Personal” spaces. After hearing user feedback via our support team, we realized that this was a misnomer since work in this space was still tied to a work email address. We renamed the space “External teams.”
Early explorations of the menu with feedback and notes from the team

Embracing hard problems

Whenever we see a commonly requested feature, our instinct is to ship it as soon as possible. In this case, we initially thought that building support for multiple accounts would be a straightforward ship. But as we scoped the project, we realized just how interwoven the work would be. Changes that one team made had the potential to disrupt ongoing workstreams across product, design, and engineering.

Throughout the process, we considered various approaches to building an account switcher that would’ve been more straightforward, and thus faster to launch. In many ways, the easy answer would be to ship an MVP in response to user feedback. But knowing that our ideal state would disrupt the file browser IA, it was important to get it right. While getting it right took longer, it also allowed us to think more holistically about the user experience—landing on a solution that solves immediate needs, while leaving room to scale with Figma as our products evolve. 

Check out the new account switcher feature in Figma and get more tips in this help center article. If this type of cross-functional project sounds like an interesting challenge, learn more about Figma and check our open roles—we’re hiring! And keep submitting feature requests—whether it’s through support, our forum, or on social media, we’re always listening.