#CutTheClutter0 debatiendo

We've just added a set of free training content for topics not in Trailhead; business analysis, Org clean up, Org Impact Assessment & Documentation, and  User Adoption .   train.elements.cloud

I haven't explored it too much yet, but Config Workbook in the AppExchange has a lot of great tools for reviewing profiles and permissions

#cuttheclutter starts with understanding your Org, and then a simple achievable approach to documenting it.  Here is a video of Southeast Dreamin #SED18 presentation minus the laughter, heckling & free t-shirts 

video: https://app.box.com/s/jh4zlnncpstjb3mljrjwsbdoumq9x6d8

deck: https://app.box.com/s/6wemoscts1y7mv42iewpf79kdeg4a3fk

@Jon McDermott 

Even schema builder isn't helpful because there are so many relationship lines, they are on top of each other, despite zoom level. Other ideas?

I recommend charting this out. I referenced Lucid Charts in the webinar, but you can do this in Word or Powerpoint. I mainly use it for integrations and use closed arrows for one-way sync and open arrows for two-way data flows. You could use the same for charting out your relationships. It really depends on what you're after though - you can see what objects are tied by viewing the lookup fields on the object itself. Are you trying to document this from a process perspective or are you hiding related lists or renaming objects and it's causing confusion for teams? #CutTheClutter 

@Toya Tate 

What's Kelly's recommendations for orgs that can't afford a separate license for each of their integrations? What if they have to dedicate one license to all of their integrations?

Great question! For me, security always comes first. You need to know what is touching your data, when it's making updates and also have the ability to disable access if something goes wrong (API Limits are hit, Integration credentials are compromised and you didn't have enable API Only checked - what would you do in that case?)

If I absolutely had to make a decision under a budget constraint, I would actually say to remove users that are not active in the Org from a pure license count and have each integration on their own license. If the Org is really lean and everyone needs to have their license (and adding isn't an option) then I would pursue getting creative with your options. Review the functionality your users have and determine if you can purchase a different license type that may give them what they need but not have all the bells and whistles of a full license. Can you discuss contract terms and bulk buys with your AE? Analyze the tools that are running in the business and look for overlap, see if you can free up available dollars for those licenses in other areas. It's a really tough challenge, but it's even worse if something goes wrong with your integrations, you can't tell where the issue is coming from and you can't turn it off because everything is hinging on that one license. #CutTheClutter 

How would I setup my Org such that, before every deployment the earlier component version will be backed up automatically?

i loved the cut that clutter webinar! looking forward the next one! is it possible to have more of these?

I couldn't find a phone number to call in.  I watched the presentation without sound.  I too, would like more information on  Field Footprint?  Is it free for companies with premier support?

What would be an easy and awesome way to do a mass compare of Profiles?