so it may not be ideal.
Understatement of the century. Yes it’s not ideal because then it’s not a shared library!
We work on a design system for an organization. We were using Sketch and Invision and have put a lot of effort into migrating to Figma and, while we love using it and amazing things like properties, solid autolayout etc. etc., this is the issue that is close to pushing us away.
The reason being is the organization (funnily enough) needs an organization plan to structure teams and projects for their business units.
But for this use case it’s absolutely essential that the core design system components can be still shared with outside agencies in a straightforward way where they can be kept updated, because the organization doesn’t have in-house designers.
Their projects can run long term and agencies (we know from experience) can’t be trusted to pull in a new unlinked file, identify the components that have changed and swap in the latest versions. And they shouldn’t have to because we know it’s possible!
That ability was an "accidental feature that was disabled – Global live library sharing - #13 by Antoine – but why couldn’t it be re-enabled for an organization who is paying more for their plan?
I wish you could be more transparent about it. If it’s a technical issue fine, it must be a complex beast under the hood. If it’s a business decision to sell editor seats or whatever, then ok that’s your call but then at least we know what the deal is.
But radio silence (or unfit for purpose workarounds) leave us annoyed / confused / disillusioned / angry / wondering what we did in a previous life to deserve this / etc.
