Salesforce ArchitectureAdvancedlicensingpersonacost
Design enterprise persona-based licensing architecture reducing shelfware
Real World Scenario
Enterprise agreement true-up finds 2000 Sales Cloud licenses but only 1200 monthly active users; 800 read-only users on full license.
Expected Answer
• Persona map: seller service agent executive partner read-only integration
• Permission set license and Einstein GPT add-ons right-sized
• Identity license for read-only dashboard users where applicable
• Automated inactive 90 day deprovision reclaim license
• Community license separate count portal not full CRM
• Quarterly true-up forecast with active usage metrics
• Chargeback BU pays for allocated personas
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Persona map: seller service agent executive partner read-only integration. Permission set license and Einstein GPT add-ons right-sized. Pick based on your integration pattern and team capability. Persona licensing architecture saves millions—map job function to SKU not default full license. Optimize for scale and operational observability.
Architect Perspective
Persona licensing architecture saves millions—map job function to SKU not default full license.