They can be used for such a wide variety of purposes (folders, workflow emails, report emails, queue membership, data sharing, content workspace permissions, etc....) that it really does make sense to have some sort of governance over managing them. I'm currently working on documenting every where each one is currently used in our Org, so I can determine the best naming convention, and use for them. I also don't like assigning any piece of configuration to a specific person if I don't have to, so using Public Groups where possible would make employee turnover much easier to manage. Maybe I'm the first person trying to do this....but I would think/hope not.
3 Antworten
Adding my Dev Org to this question. My user was my current organization user. Thanks!
