Slice library per-user vs per-repo?


When creating a slice and adding it inside the slice library, only the user who created the slice can see it showing up in the “Use existing slice” section when modeling a custom type’s slice zone. Other users can’t use the work already done which kinda defeats the whole point of having a library. Is this intended?


Hello Simon,

Thanks for posting to us.

Yes, It's made like that it becomes available in any custom type and any repo (only for that user, though – the slice library's scope is per-user, not per-team or per-repo).

I understand your point about having a library per repo. I will pass this on to my dedicated developer team.



1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.