Skip to main content

Please let me know if such a feature exists. If not, it would be helpful if it were implemented for teams using libraries.


Group A: Artist with limited or no editing of components

Group B: Artist with governance over components


I need any component created by Group B to be available in a library for Group A. However, Group A can not break, unlink, or edit the component in any way, this ensures Group A comes to Group B for edits to the components if needed.


Please share if there is such a feature, plugin, or hack. I want to ensure our team communicates their needs appropriately while keeping our branding and components working correctly throughout all the projects created by our artists. If a rouge Group A artist unlinks and then creates their version of a component, when Group B rolls out an update for all components, the unliked component will not update, making it difficult for our team to keep track of all customized components by Group A.


Thank you.

Hey @Christine_Deer, thanks for reaching out!


For Group A, as long as they don’t have edit access to the library file itself, they shouldn’t be able to make any unintended changes. If the library is enabled for them, they can still use those components in another file that they do have edit access to.


But keep in mind that if the library is completely private, i.e. in a private/invite-only team or project they do not belong to, then they won’t be able to use or modify the components at all.


For Group B, ensure they have edit access to the library file and that the library is enabled to be used in other files, so that they can both edit and use the components.


Hope this helps!

@dvaliao Denise, thank you for your response. 🙏 I would like Group A to use the component on their projects but not be able to break the link to the component they are using. I do not want them to edit the “unlinked component” in their projects or files. Is it possible to have a component that can not be unlinked or detached from its parent?


Thank you again.

Thanks for clarifying, @Christine_Deer!


Sadly, there isn’t a way to specifically prevent a group of users from unlinking components. I’ve updated your topic into a feature request, and I’ll pass this feedback onto our Design Systems team for future consideration.

@dvaliao Denise, thank you so much for your quick response and for adding this feature for a vote.


Have a great rest of your week and best regards,

Christine

Reply


Terms & ConditionsCookie settings