
On October 5, 2026, Figma added a line to its changelog that could easily go unnoticed if you do not work between design and code on a daily basis. It is now possible to connect multiple GitHub organizations to a single Figma plan. Behind this slightly technical sentence lies real relief for product teams juggling multiple repositories, multiple clients, or multiple subsidiaries within the same company.
Before this update, a Figma plan could only talk to one GitHub organization at a time. The problem: as soon as a team worked on several projects hosted in separate GitHub organizations, they had to multiply accounts, multiply connections, or accept losing consistency across their shared design system.
With this new feature, you can now:
This feature is available on Organization and Enterprise plans. To learn more about the technical mechanics, Figma offers a dedicated guide to connecting a GitHub repository directly from the interface.
Reserving this feature for Organization and Enterprise plans is no accident. These are precisely the structures most likely to work with several GitHub organizations in parallel: multi-client agencies, large groups with multiple business units, distributed product teams. The need is real at this scale, much less so for a small team managing a single product on a single repository.
| Before the update | After the update |
|---|---|
| Only one GitHub organization connected per Figma plan | Multiple GitHub organizations connected on a single plan |
| Design system duplicated or fragmented across projects | Centralized design system, with code spread transparently |
| Multiple accounts or manual workarounds | A single source of truth for design and dev teams |
{{webdesign}}
At Mazette.co, Figma sits at the heart of our method, and not just for the design phase. It is the tool that bridges creativity and production, especially on our Webflow projects where fidelity between mockup and delivered site is non-negotiable.
This update speaks to us directly. An agency like ours works with multiple clients, often each with their own GitHub organization for custom development or technical integrations. Until now, that meant workarounds: secondary accounts, manual exports, or simply giving up on deeper integration between Figma and code.
Being able to connect multiple GitHub organizations to a single plan means gaining fluidity without sacrificing the consistency of our internal design systems. For an agency, this is exactly the kind of improvement that does not make headlines but changes teams' daily work.
Our only reservation: this feature remains limited to Organization and Enterprise plans. We would have liked to see it trickle down faster to intermediate plans, so growing teams could benefit without waiting for a costly upgrade. But in principle, it is good news, the kind that proves Figma listens to the real needs of scaling organizations.
If you are looking for an agency that makes the most of Figma for your Webflow projects, head over to our Figma web agency page or our Webflow expertise page to see how we orchestrate design and development without friction.
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.
