Prefer English?
Prefer English? Switch the website language for a better experience.
Since November 3, 2026, Figma clones a GitHub repository’s code by default as soon as a team connects that repo to its organization. In practice, this means an admin no longer needs to manually approve each connection before the code gets imported. The extra approval step is gone, and cloning is now the native behavior for any new connection.
That said, admins haven’t lost control. They can disable cloning for a specific repository at any time from the admin settings. And for connections that were already in place before this update, nothing changes: their settings remain exactly as they were configured.
The rollout covers all Figma plans. For the exact details on eligibility and configuration, head over to Figma’s official documentation.
Until now, connecting a GitHub repo to Figma came with real friction: a designer or developer would initiate the connection, then wait for an admin to approve access before actually being able to work with the imported code. On a small team, this step might go unnoticed. On a larger organization, with multiple product teams and several repos to connect, it could slow down entire workflows, sometimes by days.
By switching cloning to a default behavior, Figma removes a layer of administrative friction without removing control. That’s an important nuance: this isn’t a step back from governance, it’s a shift in posture, from systematic opt-in to targeted opt-out.
| Before this update | Since November 3, 2026 |
|---|---|
| Admin approval required for every new connection | Cloning enabled by default, no approval needed |
| Control applied upfront only (approval) | Control applied downstream, repo by repo |
| Existing connections locked to their original setting | Existing settings unchanged by the update |
For teams working in dev mode, with frequent back and forth between design and code, this kind of detail genuinely changes the pace of work. Less waiting means more iterations possible within the same day.
At Mazette.co, we use Figma every day, on both product design and custom web design projects. This kind of update, quiet as it may seem, speaks directly to us: it’s exactly the sort of friction we encounter in the field, with fast-growing clients where every repo, every integration, every admin approval adds a delay that doesn’t bring any real value on its own.
We think the balance here is quite well thought out. Figma isn’t removing control, it’s relocating it. An admin still has full authority over sensitive repositories, but no longer has to make upfront decisions on connections that, in the vast majority of cases, pose no issue at all. It’s a logic we see in plenty of good tools: reasonable security by default, with the exception still possible without the bureaucracy.
{{webdesign}}
The real benefit, in our view, mostly plays out for organizations scaling fast, with multiple product teams and just as many repos to connect. That’s precisely the profile of clients we work with most often: tech start-ups and scale-ups where execution speed matters just as much as rigor. One less piece of friction in the Figma GitHub integration means a bit less time lost between a design idea and its coded version, visible right in dev mode.
We keep one caveat in mind: default doesn’t mean no vigilance required. Any organization connecting repositories with sensitive code should check its admin settings as soon as this rolls out, rather than discovering after the fact that automatic cloning happened without oversight. A good habit to add to your Figma onboarding checklist, plain and simple.
If your team already uses GitHub alongside Figma to keep design and code in sync, here’s what deserves your attention in the coming weeks:
This kind of evolution clearly illustrates the direction Figma is heading: smoothing the path from design to code, while never losing sight of the governance needs of larger organizations. A trend we’re watching with interest, project after project.
Code
Over 180 companies have already stepped out of the shadows with us.
Since November 3, 2026, every new GitHub repository connection automatically clones the code into Figma, with no admin approval step required. Existing connections keep their current settings, unaffected by this update.
Yes. An admin can disable cloning for a specific repository at any time, directly from the organization’s admin settings. This setting applies repo by repo, without affecting other active connections.
Figma says the rollout will reach all plans progressively. The exact details by plan are still worth checking on Figma’s official page for this feature, and Mazette.co always recommends confirming exact quotas and settings with the official source before rolling it out in production.
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.
