#CommunityImpact0 debatiendo

➡️ Join Sprinty's Community Resources at the LAST community sprint of the year in person in Chicago on November 13-14. This is a great team to join if you are a first-time Sprinter or new to the Commons! Can’t make it to Chicago, or sprinting with another team? You can still help by submitting a resource! Be part of building a resource hub that truly meets the needs of non-profit and education organizations. 

#Nonprofit #Education #CommunityImpact @Nonprofit and Education MindShare @Salesforce.org Commons & Sprint Events

🌟 Join Sprinty's Community Resources at the upcoming Commons Virtual Community Sprint September 26-27! This is a great team to join if you are a first time Sprinter or new to the project! Already part of another group? No problem! You can still help by submitting a resource! Let’s build a resource hub that truly meets the needs of non-profit and education organizations.  #Nonprofit #Education #CommunityImpact @Nonprofit and Education MindShare @Salesforce Commons & Sprint Events

Success Stories and Impact

🎉 Have a success story from using Sprinty’s Community Resource Collection? Share it with us! Your experiences can inspire and guide others. Let’s celebrate our wins and learn from each other. 

#SuccessStories #CommunityImpact

#Nonprofit @Nonprofit and Education MindShare #Education @Commons: Sprinty's Community Resources 

We have a client who we're helping implement HEDA in a brand new instance for an advancement use case. However, they'd like the ability to scale in future phases to include current student data. 

I'm used to using the standard Administrative Account approach, but the Household model makes sense for advancement. Can anyone name some obvious downsides when scaling to include things like current/prospective students? Is mixing Household and Administrative Accounts in the system of any real consequence, as long as the default account model doesn't change? Or are there any consequences to switching the default account model later on?