Skip to main content

I, like many designers, have my own workflow and work style. This includes the way I tag up my designs with annotations, make notes about design decisions, and prep screens for use in other formats (like presentations).


I would love to have my own personal library of “things”, including my own annotation styles, type, colours, components etc. that is only “published” for me - so that I don’t have to make and publish a library that will be available to my entire team.


The reason I want some sort of “publishing” ability is so that I don’t have to go and get the things I want to use, or recreated things every time I work on a new project in a new file. And so that I can push my own updates that only affect my stuff.


Our team has a File Management library with a bunch of stuff for everyone, but like I mentioned above, there are things specific to my workflow and style of presenting work that I’d like all-over-access to (and wouldn’t fit in the team File management library).


Would I be able to achieve the same thing with a private team that only has me in it? Seems a bit clunky 😅

That is something our team has implemented and it works really well! Each designer created a custom (private) team within the org so we can create our own libraries and organize our own files for random stuff that may not fit in the org folders but we don’t want hanging around in our drafts. I use mine for things you mentioned like annotation kits, styles, and presenting components and I can publish changes to use throughout my org files!


Reply