Skip to main content

We’ve built a large design library in our organization account that many internal teams use.

Sometimes, we also work with external vendors (like agencies or freelancers) who need to use this library and get updates regularly. Because we’re a large corporation, it’s not practical to add them as paid seats just for a short project – the approval and payment process is too complex.

What’s the best way right now to share a library with people outside the organization so they can actually use the components (not just view them)?

Is exporting the library as a .fig file really the only option – even though that means they won’t get any future updates?

Thanks!

We need to support this workflow as well to maintain a single source of truth. Creating duplicate instances that don’t receive future library updates will undermine the value of a shared system we've spent the last six months building.

I've successfully granted view-only access to our library files (with copy/paste/export disabled), allowing external consumers to locate and enable our libraries in their own Figma accounts. This has worked in 3 out of 5 tests, across accounts with Free, Professional, and Organization plans.

Given the inconsistency, I’m starting to wonder if I’ve stumbled onto an unintended behavior, rather than a fully supported feature. Has anyone else been able to get this approach working reliably?

Reply


Terms & ConditionsCookie settings