Enable Assets search only for enabled libraries

Shocked that Figma hasn’t spotted this “All libraries by default” issue themselves - please, please prioritise this!! (seriously) Our UX/Design team wasted hours trying to figure out this misperceived “bug” in our Design System, it directly undermines the architecture of any multiple-design-systems setup. I’m a big Figma fan/advocate, but if another tool arrived that could match Figma and solved for this issue then I’d bounce the org over to that tool. It’s not the expected behaviour (from a user lens) and usually Figma never drop the ball like that.

Adding myself to the discussion that this feature is needed and I hope they don’t hide this feature behind some plans. It’s already frustrating enough you can’t do a library analytics unless you use Organization Plan (the most expensive).

Both features should be given and not blocked by some paywall. Keeping tracking of changes in the library is hard enough.

If developers can keep track of files changed, deleted, and added for free using Git, why shouldn’t designers be able to for free?

Same from our perspective. We are working in an agency model where we’re handling multiple libraries for multiple clients at once. Not being able to filter out the results ofter results in placing components that should simply not go into a specific file.

We have the same problem and just found out that there are a lot of assets from different libraries because our colleagues didn’t know that they were using other assets than the ones from our own library. This is a major problem, especially for bigger teams like ours!!

Same here, it’s super annoying to find out people use the wrong components ! you have to waste time cleaning everything up later

This is a major functionality issue that needs to be addressed.

I thought I was doing something wrong, and am shocked that this is just how it works. A major major flaw, we basically cannot use the search bar at all.

Echoing this issue for prosperity in the hopes that Figma will address this. Upgraded to a new library and advising users to turn off the old library (during a transition phase) and causing major issues of duplicated components and user issues around knowing which instance of a component to actually use.

This is a major productivity problem for us. We’re using a hierarchy of libraries where the same component name is used in multiple libraries.
Seeing the library name in the search results would really help designer productivity and prevent the use of incorrect components.

Same here in our organization. Designers often use old unpublished and deleted components because they appear in “assets”. So we are painting it red to indicate that it is an old component. Horrible.