Our team is very enthusiastic about the Figma Buzz concept, we decided to try it out. I created templates, locked the layers that don't need editing, published them, shared them with my colleague and gave him editing permission.
My colleague logged in but was able to edit every layer of the template, also the locked ones. And also if he uses that template in a new file.
Could you help me find out what's wrong? Why Figma Buzz doesn't meet our expectations?
In the first screenshot below, we see the layers are locked in design mode. And in image 2 and 3, we see the user the template is shared with able to edit the same layers, while in Buzz mode.
I cannot find similar questions in the Forum. Are we the only team having this problem?
For now we've concluded that Figma Buzz's beta version is not sufficiently developed for our current collaboration needs. Because we did not experience the anticipated 'simplified editing experience.'
Thanks a lot in advance! Marinske
Page 1 / 1
Hey, Marinske!
I’m Mike, a researcher on the Buzz team.
Thanks for sharing this with us. When you have a chance, could you email me (mblight@figma.com) with the file? We’d love to give it a look to see what’s happening.
-mike
Hi Mike,
Thanks for your help.
Shall I share the two files with you in Figma (I just did)? Or do you want me to send you the downloaded .fig file?
Thanks! Marinske.
Hi! OK, I think we (the Buzz product team) figured it out!
In the second two screenshots, the assets being edited aren't actually locked templates—they're editable files. It looks like you created templates, locked certain layers, and published them, which is the right flow.
BUT!
Instead of having your teammate open a new file based on that published template, you likely shared shared the original file itself. Your teammate needs to open up Buzz and create a new file from the template you published instead of editing from the link you shared (e.g., the source file).
Your teammate (assuming they’re in the same org) should see “From <org name> in the entry modal” (see the attached picture). From that tab, they should see the template you published. After clicking that, they should not be able to edit the fields that you’ve hidden because they’ll be working with a publishing template rather than the file you used to create a template in the first place.
Let me know if that helps!
Hello Mike,
Thanks a lot for this potential solution. It might take a while before I try it because my colleagues are on summer holiday.
I will get back to you with the outcome as soon as I can.
Meanwhile I have one question: Does it make a difference if the team member has an ‘edit’ or 'view’ seat type?
Thanks in advance,
Marinske.
Hi Mike,
I logged in with another email address and I tried to find the “From <org name> in the entry modal” shown on the image you attached. I do not see it. While I am attached to
Now I'm confused with the terms seats, teams or org's… Not knowing what you exactly mean by “(assuming they’re in the same org)'’. (Do I need an organisation plan?)
And like I mentioned earlier, I wonder what kind of seat is needed. View seat should be enough because Buzz is free for everyone?