Lock Down Figma Make and Sites Publishing at the Workspace Level

Figma has added workspace-level web publishing controls for Figma Make and Figma Sites. Confidence level: confirmed. Organization admins can now set a default publishing policy across the org, then override that policy for specific workspaces when a team needs different access.

What changed

Figma says org admins can manage web publishing permissions for Make and Sites files at the workspace level. The control has two layers: an organization-level default that applies broadly, and optional workspace-specific overrides for teams that need looser or tighter publishing rights.

That matters because Make and Sites sit close to public output. A prototype, generated app, campaign page, or internal experiment can become shareable quickly. Workspace-level policy gives admins a way to separate exploratory teams from production, client, education, or regulated workspaces.

Key takeaways

• Figma Make and Figma Sites publishing can now be governed by workspace, not only broad org policy.
• The update targets Organization and Enterprise-style administration needs, especially teams mixing AI-generated prototypes with public web output.
• Admins should audit existing workspaces before assuming the org default is enough.
• The control helps reduce accidental publishing, but teams still need approval rules for brand, customer data, and unreleased product work.
• Releasebot independently indexed the update from Figma's release notes, which supports the source trail without turning this into a rumor.

Availability and access

Figma lists the update in its release notes as a June 17, 2026 administration update for Figma Make and Figma Sites. Its Help Center says the broader web publishing controls are available on Organization and Enterprise plans for organization admins, while workspace-level overrides are an Enterprise-plan control.

Teams should also check whether their Sites and Make usage is tied to beta access, seat type, or admin role. The policy can reduce risk only if the people responsible for workspace governance know which projects are allowed to publish.

Why it matters

The practical LinkLoot angle is governance. Figma's newer AI and web-building features make it easier for teams to create publishable work, but faster publishing also creates more chances for a draft, client mockup, or internal test to leak.

For teams already exploring agent-assisted design, pair this setting with a lightweight publishing checklist. Review workspace ownership, external sharing rules, brand approvals, and whether AI-generated content can be published without human review. For broader automation governance, LinkLoot's guide to AI workflow automation is a useful companion.

What to verify before you act

• Confirm the setting exists in your Figma admin console and note which plan, role, or workspace type can use it.
• Check whether the organization default blocks or allows publishing today.
• Review workspaces that contain client work, unreleased product concepts, student projects, or regulated content.
• Assign an owner for each override so exceptions do not become permanent by accident.
• Test the policy with a non-admin user before relying on it for a launch or client handoff.

Source check

Confirmed by:

• Figma Help Center documents organization web publishing controls, password requirements, and Enterprise workspace overrides for Figma Sites and Make files.
• Figma release notes list "Workspace-level Web Publishing for Make and Sites" and describe org defaults plus workspace overrides for publishing permissions.
• Releasebot's Figma feed mirrors the update and summarizes it as workspace-level web publishing controls for Make and Sites.

Context:

• Figma's Help Center gives the admin-console path and plan notes, but teams should still verify rollout in their own tenant.
• This post treats the update as an admin-control change, not as a claim that every Figma workspace already has the feature enabled.