
Figma keeps building out its admin toolkit. Its latest update lets organization or workspace admins choose exactly which resources they want to push to their teams: skills, templates, component libraries, or even Make kits. The goal is simple: make sure every user works with the right tools from the start, without having to dig through a mountain of available resources.
In practice, an admin can now mark certain resources as "recommended" for their organization or workspace. These recommended resources display a checkmark and an explicit tooltip along the lines of "Recommended by [organization or workspace admin]." The result: users immediately spot the right resources to use, without having to guess or ask on Slack which library is the reference one.
This feature fits into a broader trend at Figma: giving admins more and more curation and governance power, as organizations pile up dozens, even hundreds, of files, kits and templates. Without this kind of mechanism, finding the "real" official component library among ten outdated variants quickly becomes a nightmare.
In a growing agency or product team, Figma resource sprawl is a classic problem. A junior designer joining the team ends up facing a "v2" component library, another one called "v2-final," and a third one called "v2-final-actually-final." Without a clear signal, they pick one at random, or worse, they recreate their own components. This recommendation feature fills exactly that gap.
| Before this update | With recommended resources |
|---|---|
| Users pick at random among published resources | Users immediately see the admin-validated resource |
| No visual signal of trust | Checkmark and explicit "Recommended by..." tooltip |
| Risk of duplicated components or skills | Natural convergence toward the right tools |
| Slower onboarding for new hires | Clear bearings from day one |
At Mazette.co, we use Figma every day, on Webflow projects where several designers and sometimes several clients work on the same files. So yes, we know the "ghost resource" problem well: the one nobody dares delete "just in case," but that nobody actually uses anymore.
This feature strikes us as a good idea, even a slightly overdue no-brainer. Figma had already laid the groundwork with team libraries and Design Systems Analytics, but it was missing this small visual trust signal that says "use this one, not the others." That is exactly the kind of detail that, at the scale of a fifty-designer organization, saves cumulative hours of searching and avoids brand inconsistencies.
The only catch: this feature remains limited to plans with advanced admin capabilities, meaning structures already mature enough to have a dedicated admin. For a small team or a freelancer, the impact will be zero. But for our clients with structured product teams or brand teams, it is a real plus for maintaining design system consistency over time, especially when moving from a Figma file to a Webflow site, where every component inconsistency directly turns into technical debt.
If you work with Figma every day and are looking to bring more structure to your internal resources, also take a look at our article on the latest Figma updates under the microscope, or discover how we actually use Figma in our Webflow projects.
Code
Impactful titles, polished meta descriptions, sitemaps, Schema.org, Hn structure, and audits: these are the SEO foundations that make your content readable by both Google AND generative AI. We cover both simultaneously.

With over 180 clients, our agency is one of the few in France to hold the Webflow Premium Partner label, supporting you in every area, including custom web design, sophisticated automation, conversion optimization, and SEO and GEO visibility.
We create bespoke web designs focused on performance, user journeys, and conversion. Join over 180 clients who have trusted us to elevate their brand.
