Skip to main content

Hi all 🙂


Can you please guide me. This particular case is new for me, I need your advice.


The thing is: I need to share Figma file to the client so he can play around with color variables to build new Mode that will suite his brand colors. It should be separated from the main file. Also I need to avoid him pushing changes to the master library.


In my imagination it works this way:



  • I send a link to a file to the client, file is wired to master library so he can create Modes;

  • After he done - my dev team goes into this separate file and grab all Modes into development.


Will it work only inside my team project? I should invite client inside team project with Edit rights? Will variables remains working if he copy the project into his drafts?

Hi @Timofey_Malkov – from my current understanding of libraries, there’s not really a way to accomplish this in the way you want.


You could share edit access to the file they’d need to work on, but adding them as an editor to the file will also mean you are adding them to your team – this means you will be charged for an additional seat for them to edit files within your team. You may be aware and okay with this, but I always like to make sure that’s understood before anything else.


If the end goal is for them to be able to create their own variables and modes within a copy of the main file you have in one of your projects, and then be able to take those to implement in the main file, there shouldn’t be a problem as long as they have access edit access to the copy of the main file in question.


re: library publishing – I think that if they’re working in a copy, there shouldn’t be too big of a worry of them overwriting any libraries you have, but I’d recommend telling them to avoid publishing anything and just work in the file.


I may be misunderstanding your asks, though. so let me know if I have.

Reply


Terms & ConditionsCookie settings