Settings Dashboard Deep Dive
ποΈ Complete Settings Control: Comprehensive guide to the sophisticated Pastoral Care settings dashboard with 8 management sections, active settings coordination, and universal SMS configuration for any Salesforce object.
βοΈ Configuration Excellence: Master every aspect of the centralized settings system including Custom Settings for SMS, active record management, team coordination, and multi-organizational deployment strategies.
π― Quick Startβ
β
Step 1: Understand the active settings record system and priority management
β
Step 2: Configure Custom Settings for universal SMS across any Salesforce object
β
Step 3: Master the 8 dashboard sections for complete system control
β
Step 4: Set up team-specific email templates and campaign integration
β
Step 5: Implement organizational validation and conflict resolution
π Table of Contentsβ
- ποΈ Settings Dashboard Architecture
- βοΈ Active Settings Management
- π± Universal SMS Configuration
- π§ Email Template Management
- π₯ Team Configuration
- π Campaign Integration
- π Settings Validation
- π Multi-Organizational Setup
ποΈ Settings Dashboard Architectureβ
ποΈ Dashboard Overviewβ
The Pastoral Care settings dashboard provides centralized control over 8 critical management sections, each designed for specific aspects of organizational care coordination.
- ποΈ System Architecture
- πΊοΈ Dashboard Navigation
- π Access Control
Core Settings Objects:
- Pastoral_Care_Setting__c - Main configuration record with active/inactive control
- Pastoral_Care_Custom_Settings__c - List Custom Setting for universal SMS field mapping
- Email Templates - Team-specific communication templates
- Campaigns - Member engagement and tracking integration
Dashboard Sections:
- Active Settings - Current configuration record management
- Email Alerts - Clergy and non-confidential template configuration
- Pastoral Care Team - General team settings and campaign integration
- Bereavement Team - Specialized bereavement coordination
- Congregational Settings - Community-wide communication
- Engagement Plan Templates - NPSP integration by record type
- Pastoral Care Flows - Automation monitoring and management
- Phone Configuration - SMS field mapping and merge field setup
Accessing the Dashboard:
- Pastoral Care App β Pastoral Care Settings tab
- App Launcher β Search "Pastoral Care Settings"
- Setup Menu β Custom Settings β Pastoral Care Custom Settings
- Quick Actions β Settings shortcuts from case records
Navigation Flow:
- Main Dashboard β Select active settings record
- Section Tabs β Navigate between 8 configuration areas
- Field-Level Config β Detailed parameter setup
- Validation Panel β Real-time configuration verification
- Help Integration β Context-sensitive guidance and tips
Required Permissions:
- Pastoral Care Admin permission set for full dashboard access
- Custom Settings read/write for SMS configuration
- Email Template access for communication setup
- Campaign access for member engagement tracking
- Flow visibility for automation management
Role-Based Access:
- System Administrator - Full configuration control
- Care Coordinator - Team-specific settings access
- Team Lead - Limited configuration for assigned teams
- End User - Read-only access to relevant settings
- Mobile User - Essential settings for field operations
βοΈ Active Settings Managementβ
π― Configuration Record Systemβ
Only ONE Pastoral Care Settings record can be active at any time. The system uses the active record to control all automation, email templates, and team assignments across the organization.
- β‘ Active Record Control
- π Configuration Management
- π Environment Management
Active Settings Mechanism:
- Single Active Record - System enforces one active configuration
- Automatic Deactivation - Previous active record deactivated when new one is activated
- Validation Logic - Built-in flow prevents multiple active records
- Rollback Capability - Ability to reactivate previous configurations
- Audit Trail - Complete history of configuration changes
Creating Active Settings:
π Step-by-Step Active Settings Creation
New Settings Record Processβ
- Navigate to Settings - Pastoral Care app β Pastoral Care Settings tab
- Create New Record - Click "New" to start configuration
- Essential Fields:
- Settings Name: Descriptive name (e.g., "Production Settings 2025")
- Active: βοΈ Check to make this the active configuration
- Description: Purpose and scope of this configuration
- Effective Date: When this configuration takes effect
Required Configuration Stepsβ
- Basic Information - Name, description, and activation status
- Email Template Assignment - Configure templates for each team type
- Campaign Integration - Link campaigns for member engagement tracking
- Phone Field Configuration - Set up SMS field mappings
- Team Assignments - Configure notification recipients
- Validation Check - System verifies configuration completeness
- Activation - Set as active configuration with automatic validation
Best Practicesβ
- Test Configuration - Validate settings with test data before activation
- Backup Previous - Keep previous configuration available for rollback
- Documentation - Document changes and rationale for future reference
- Team Communication - Notify teams of configuration changes
- Monitoring - Monitor system behavior after activation
Settings Record Structure:
| Field Category | Fields | Purpose |
|---|---|---|
| Basic Info | Name, Description, Active, Effective Date | Core record identification |
| Email Config | Clergy Template, Non-Confidential Template | Team-specific notifications |
| Team Setup | PC Team Template, Bereavement Template | Specialized team coordination |
| Campaigns | PC Campaign, Bereavement Campaign | Member engagement tracking |
| Phone Fields | Contact Phone Fields, Case Phone Fields | SMS merge field configuration |
| Assignments | Birthday Assignee, Default Teams | Automated task and notification routing |
Configuration Strategies by Organization:
- βͺ Religious Organizations
- π Educational Institutions
- π₯ Healthcare Organizations
- π’ Corporate Organizations
Settings Configuration:
- Settings Name: "Congregation Care Settings 2025"
- Clergy Template: "Rabbi_Pastoral_Alert" or "Pastor_Care_Notification"
- PC Team Template: "Pastoral_Care_Team_Alert"
- Bereavement Template: "Bereavement_Committee_Notification"
- Congregational Template: "Community_Bereavement_Notice"
Campaign Integration:
- PC Campaign: "Member_Care_Tracking_2025"
- Bereavement Campaign: "Bereavement_Support_2025"
- Congregational Campaign: "Community_Engagement_2025"
Settings Configuration:
- Settings Name: "Student Services Configuration 2025"
- Leadership Template: "Principal_Student_Alert"
- Care Team Template: "Student_Services_Notification"
- Crisis Template: "Emergency_Response_Alert"
- Community Template: "School_Community_Notice"
Campaign Integration:
- Student Support Campaign: "Student_Care_Tracking_2025"
- Crisis Response Campaign: "Emergency_Support_2025"
- Community Campaign: "School_Community_Engagement_2025"
Settings Configuration:
- Settings Name: "Patient Advocacy Configuration 2025"
- Medical Template: "Medical_Team_Patient_Alert"
- Advocacy Template: "Patient_Advocate_Notification"
- Social Work Template: "Social_Work_Team_Alert"
- Family Template: "Family_Liaison_Notice"
Campaign Integration:
- Patient Support Campaign: "Patient_Advocacy_Tracking_2025"
- Family Support Campaign: "Family_Support_2025"
- Medical Coordination Campaign: "Medical_Team_Coordination_2025"
Settings Configuration:
- Settings Name: "Employee Assistance Configuration 2025"
- Management Template: "Manager_Employee_Alert"
- HR Template: "HR_Team_Notification"
- Wellness Template: "Wellness_Coordinator_Alert"
- Emergency Template: "Emergency_Response_Notice"
Campaign Integration:
- Employee Support Campaign: "Employee_Assistance_Tracking_2025"
- Wellness Campaign: "Wellness_Program_2025"
- Emergency Campaign: "Emergency_Response_2025"
Multi-Environment Strategy:
- Development Settings - Configuration for testing and development
- Staging Settings - Pre-production validation environment
- Production Settings - Live organizational configuration
- Training Settings - User training and demonstration environment
- Backup Settings - Emergency rollback configurations
Change Management Process:
- Development - Create and test new configuration in dev environment
- Documentation - Document changes and validation procedures
- Staging - Deploy to staging for user acceptance testing
- Training - Train teams on configuration changes
- Production - Deploy to production with monitoring
- Validation - Confirm proper operation and performance
- Rollback Plan - Maintain ability to revert if issues arise
π± Universal SMS Configurationβ
π§ Custom Settings for Any Objectβ
SMS functionality requires proper Custom Settings configuration for each Salesforce object. The Pastoral_Care_Custom_Settings__c List Custom Setting maps Object API Names to Phone Field API Names for universal merge field support.
- βοΈ Custom Settings Setup
- π Phone Field Mapping
- π± LWC Integration
Custom Settings Configuration Process:
π± Universal SMS Setup Guide
Access Custom Settingsβ
- Navigate β Setup β Custom Settings
- Find β "Pastoral Care Custom Settings"
- Click β "Manage" to access configuration
- Create β "New" to add object configuration
Required Configuration Fieldsβ
- Name - Unique identifier for this configuration (e.g., "Contact_SMS_Config")
- Object API Names - Salesforce object API name (e.g., "Contact", "Caring_Case__c")
- Phone Field API Names - Comma-separated list of phone fields for merge field access
Standard Object Configurationsβ
Contact Object:
- Name:
Contact_SMS_Config - Object API Names:
Contact - Phone Field API Names:
Phone,MobilePhone,HomePhone,OtherPhone
Caring Case Object:
- Name:
CaringCase_SMS_Config - Object API Names:
Caring_Case__c - Phone Field API Names:
Contact__r.Phone,Contact__r.MobilePhone,POC_Cell_Phone__c,Phone_Call__c
Account Object (if needed):
- Name:
Account_SMS_Config - Object API Names:
Account - Phone Field API Names:
Phone,Fax
Custom Object Configuration:
- π Student Object
- π₯ Patient Object
- π’ Employee Object
Educational Institution Custom Object:
Name: Student_SMS_Config
Object API Names: Student__c
Phone Field API Names: Personal_Phone__c,Emergency_Contact_Phone__c,Parent_Phone__c
Usage Example:
- Student support cases can send SMS to student, parent, or emergency contact
- Merge fields automatically available:
{!Student__c.Personal_Phone__c},{!Student__c.Parent_Phone__c} - textMerge LWC displays all configured phone options
Healthcare Custom Object:
Name: Patient_SMS_Config
Object API Names: Patient__c
Phone Field API Names: Patient_Phone__c,Emergency_Contact__c,Family_Contact_Phone__c
Usage Example:
- Patient advocacy cases can send SMS to patient or family members
- HIPAA-compliant phone field mapping
- Emergency contact coordination through SMS
Corporate Custom Object:
Name: Employee_SMS_Config
Object API Names: Employee__c
Phone Field API Names: Work_Phone__c,Personal_Phone__c,Emergency_Contact__c
Usage Example:
- Employee assistance cases can reach employees through work or personal phone
- Emergency contact notification capability
- Wellness program engagement through SMS
Phone Field Syntax Rules:
- Direct Fields -
Phone,MobilePhone(fields on the current object) - Related Object Fields -
Contact__r.Phone(fields on related objects through lookup) - Custom Fields -
POC_Cell_Phone__c(custom phone fields) - Comma Separation - Multiple fields separated by commas, no spaces
Field Access Patterns:
| Field Pattern | Description | Example |
|---|---|---|
Phone | Standard phone field on current object | Contact.Phone |
Custom_Phone__c | Custom phone field on current object | Caring_Case__c.POC_Cell_Phone__c |
Contact__r.Phone | Related object standard field | Caring_Case__c.Contact__r.Phone |
Contact__r.Custom_Phone__c | Related object custom field | Caring_Case__c.Contact__r.Emergency_Phone__c |
Validation and Testing:
π Phone Field Validation Process
Field Accessibility Checkβ
- Object Manager β Select target object
- Fields & Relationships β Verify phone fields exist
- Field-Level Security β Confirm user access to phone fields
- Page Layouts β Ensure phone fields are visible (optional)
Custom Settings Validationβ
- Test SMS Creation β Create text template for object
- Merge Field Test β Verify phone fields appear in merge field list
- Mobile Test β Test SMS sending from mobile device
- Error Checking β Review any error messages for field access issues
Common Validation Issuesβ
- Field API Name Typos - Ensure exact field API name matches
- Permission Issues - User lacks access to phone fields
- Related Object Access - User cannot access related object fields
- Custom Field Namespace - Managed package fields may have namespace prefixes
textMerge LWC Configuration:
- Page Layout Addition - Add textMerge LWC to object record pages
- Automatic Field Detection - LWC automatically reads Custom Settings configuration
- Dynamic Phone List - Displays all configured phone fields for object
- Merge Field Integration - Connects to Text Template merge field system
- Mobile Optimization - Touch-friendly interface for mobile SMS sending
LWC Placement Strategy:
π± Adding textMerge LWC to Any Object
Lightning App Builder Processβ
- Object Manager β Select target object β Lightning Record Pages
- Edit Page β Select appropriate record page template
- Components β Drag "textMerge" LWC to desired location
- Configure Component β Set visibility and size properties
- Save and Activate β Deploy to users
Recommended Placementβ
- Contact Pages - Communication section or related list area
- Case Pages - Action panel or top of page for quick access
- Custom Object Pages - Primary tab or communication section
- Mobile Layout - Prominent placement for field team access
User Experience Considerationsβ
- Mobile Priority - Ensure component is easily accessible on mobile
- Workflow Integration - Place near related case management tools
- Permission Sensitivity - Only visible to users with SMS permissions
- Training Support - Include component in user training materials
π§ Email Template Managementβ
π¨ Team-Specific Communication Setupβ
- π§ Template Assignment
- π Merge Field Configuration
- π Template Testing
Email Template Structure:
- Clergy/Leadership Templates - High confidentiality case notifications
- Team Templates - Standard care team coordination
- Specialized Templates - Bereavement, crisis, or specific care type alerts
- Community Templates - Public notifications and announcements
Template Assignment Process:
π Email Template Configuration Guide
Template Selection Criteriaβ
- Confidentiality Level - Match template to case privacy requirements
- Team Responsibility - Route to appropriate team members
- Response Urgency - Different templates for urgent vs. routine cases
- Communication Style - Organizational tone and messaging approach
Settings Dashboard Configurationβ
- Navigate β Pastoral Care Settings β Active Settings Record
- Email Configuration Section β Select templates for each category:
- Clergy Email Template - Leadership notifications
- Non-Confidential Email Template - General team alerts
- Pastoral Care Team Template - Primary care team notifications
- Bereavement Team Template - Specialized bereavement alerts
Template Content Guidelinesβ
- Subject Line - Clear, actionable, privacy-appropriate
- Body Content - Relevant case information based on confidentiality
- Action Items - Specific next steps and responsibilities
- Contact Information - Appropriate escalation and coordination contacts
- Branding - Organizational styling and messaging standards
Template Examples by Organization:
- βͺ Religious Templates
- π Education Templates
- π₯ Healthcare Templates
- π’ Corporate Templates
Clergy Template Example:
Subject: Pastoral Care Attention Required - {!Caring_Case__c.Record_Type}
Dear {!Caring_Case__c.Owner.FirstName},
A caring case requiring clergy attention has been created:
Case Type: {!Caring_Case__c.RecordType.Name}
Contact: [Limited details for privacy]
Please review and coordinate appropriate care response.
Blessings, Pastoral Care System
Bereavement Template Example:
Subject: Bereavement Coordination - {!Caring_Case__c.Contact__r.Name}
Dear Bereavement Committee,
A bereavement case requires immediate coordination:
Family: {!Caring_Case__c.Contact__r.Name}
Date of Loss: {!Caring_Case__c.Death_Date__c}
Funeral Arrangements: [See case details]
Please coordinate appropriate community support.
With sympathy, Pastoral Care System
Administration Template Example:
Subject: Student Support Case - {!Caring_Case__c.RecordType.Name}
Dear {!Caring_Case__c.Owner.FirstName},
A student support case requires attention:
Student: {!Caring_Case__c.Contact__r.Name}
Support Type: {!Caring_Case__c.RecordType.Name}
Priority: {!Caring_Case__c.Priority__c}
Please review and coordinate appropriate intervention.
Student Services Team
Crisis Response Template Example:
Subject: URGENT - Emergency Student Support Required
Dear Crisis Response Team,
An emergency student support case has been created:
Student: [Confidential - See case record]
Situation Type: {!Caring_Case__c.RecordType.Name}
Immediate Action Required - Please respond within 1 hour.
Emergency Response Coordinator
Medical Team Template Example:
Subject: Patient Advocacy Case - {!Caring_Case__c.RecordType.Name}
Dear Medical Team,
A patient advocacy case requires coordination:
Patient: [HIPAA Protected - See secure case record]
Advocacy Type: {!Caring_Case__c.RecordType.Name}
Assigned Advocate: {!Caring_Case__c.Owner.Name}
Please coordinate appropriate medical team support.
Patient Advocacy Department
HR Template Example:
Subject: Employee Assistance Case - {!Caring_Case__c.RecordType.Name}
Dear HR Team,
An employee assistance case requires attention:
Employee: [Confidential - See case record]
Assistance Type: {!Caring_Case__c.RecordType.Name}
Assigned Coordinator: {!Caring_Case__c.Owner.Name}
Please coordinate appropriate support resources.
Employee Assistance Program
Available Merge Fields:
| Category | Merge Field | Usage |
|---|---|---|
| Case Info | {!Caring_Case__c.Name} | Case number and identifier |
| Record Type | {!Caring_Case__c.RecordType.Name} | Type of care situation |
| Contact | {!Caring_Case__c.Contact__r.Name} | Primary person receiving care |
| Owner | {!Caring_Case__c.Owner.Name} | Assigned care coordinator |
| Priority | {!Caring_Case__c.Priority__c} | Case urgency level |
| Status | {!Caring_Case__c.Status__c} | Current case status |
| Dates | {!Caring_Case__c.Date_Opened__c} | Case creation date |
| Custom | {!Caring_Case__c.Custom_Field__c} | Organization-specific fields |
Privacy-Conscious Merge Fields:
- High Confidentiality - Use generic fields like
{!Caring_Case__c.RecordType.Name}only - Standard Confidentiality - Include contact name and case details
- Non-Confidential - Full case information appropriate for community sharing
Email Template Validation:
π§ Template Testing Process
Pre-Deployment Testingβ
- Create Test Cases - Generate sample caring cases for each record type
- Test Email Generation - Trigger email alerts and review content
- Merge Field Validation - Ensure all merge fields populate correctly
- Recipient Verification - Confirm emails reach appropriate team members
- Content Review - Validate messaging tone and information completeness
A/B Testing Strategyβ
- Template Variations - Test different subject lines and content approaches
- Response Rate Analysis - Measure team engagement with different templates
- Feedback Collection - Gather team input on template effectiveness
- Continuous Improvement - Regular template optimization based on usage
Common Testing Issuesβ
- Merge Field Errors - Fields not populating or showing error messages
- Permission Problems - Team members not receiving expected emails
- Content Issues - Inappropriate information for confidentiality level
- Delivery Failures - Email system connectivity or configuration problems
π₯ Team Configurationβ
π― Organizational Team Setupβ
π₯ Team Structure Configuration
Team Categories by Organization Typeβ
Religious Organizations:
- Clergy Team - Senior leadership for high-sensitivity cases
- Pastoral Care Team - Primary care coordinators and volunteers
- Bereavement Committee - Specialized grief support and funeral coordination
- Life Cycle Team - Celebrations, milestones, and community events
Educational Institutions:
- Administration Team - Principal, vice-principals, and senior staff
- Student Services Team - Counselors, social workers, and support staff
- Crisis Response Team - Emergency intervention and family coordination
- Academic Support Team - Tutors, advisors, and intervention specialists
Healthcare Organizations:
- Medical Team - Doctors, nurses, and clinical staff
- Patient Advocacy Team - Patient advocates and family liaisons
- Social Work Team - Social workers and discharge planners
- Administration Team - Administrative coordinators and managers
Corporate Organizations:
- Management Team - Supervisors and department heads
- HR Team - Human resources and employee relations staff
- Wellness Team - Wellness coordinators and employee assistance specialists
- Emergency Response Team - Crisis management and emergency coordinators
π Campaign Integrationβ
π Member Engagement Trackingβ
- π Campaign Configuration
- π Campaign Linking
Campaign Purpose and Structure:
- Member Engagement Tracking - Monitor participation and response to care initiatives
- Care Outcome Measurement - Track effectiveness of different care approaches
- Resource Allocation - Understand which programs deliver the best results
- Community Impact - Measure broader organizational influence through care
Campaign Types by Organization:
| Organization | Campaign Type | Purpose |
|---|---|---|
| Religious | Member Care Tracking | Track pastoral care engagement and outcomes |
| Education | Student Support Programs | Monitor student services effectiveness |
| Healthcare | Patient Advocacy Impact | Measure patient satisfaction and outcomes |
| Corporate | Employee Assistance ROI | Track employee program participation and results |
Settings Dashboard Campaign Integration:
- PC Campaign - Primary campaign for general care coordination
- Bereavement Campaign - Specialized tracking for loss-related care
- Congregational Campaign - Community-wide engagement measurement
- Special Events Campaign - Milestone and celebration tracking
Automatic Campaign Member Addition:
- Case Creation - Contacts automatically added to relevant campaigns when cases are created
- Record Type Routing - Different campaign assignment based on care type
- Engagement Tracking - Member responses and participation automatically logged
- Outcome Measurement - Success metrics tracked through campaign analytics
π Settings Validationβ
β Configuration Integrityβ
π Automated Validation System
Validation Flow Componentsβ
- Active Settings Check - Ensures only one active settings record exists
- Template Validation - Confirms all assigned email templates exist and are accessible
- Campaign Integration - Verifies campaign lookups are properly configured
- Custom Settings Validation - Confirms SMS field mappings are correct
- Permission Verification - Ensures users have access to configured resources
Error Resolution Processβ
- Issue Detection - Automated validation identifies configuration problems
- Alert Generation - System administrators notified of validation failures
- Guided Resolution - Step-by-step guidance for fixing configuration issues
- Re-validation - Automatic re-check after corrections are made
- Success Confirmation - Validation success notification and audit trail
Common Validation Issuesβ
- Multiple Active Settings - More than one settings record marked as active
- Missing Email Templates - Referenced templates that don't exist or are inaccessible
- Invalid Phone Field Mappings - Custom Settings pointing to non-existent fields
- Campaign Access Issues - Campaign lookups pointing to inaccessible campaigns
- Permission Mismatches - Users lacking access to configured resources
π Multi-Organizational Setupβ
π’ Enterprise Configuration Strategiesβ
- π Multi-Org Strategy
- π Deployment Strategy
Organization Structure Approaches:
- Single Org, Multiple Settings - Different settings records for different departments/locations
- Separate Orgs - Distinct Salesforce orgs for each organizational unit
- Hybrid Approach - Mix of shared and separate configurations based on needs
Configuration Isolation:
- Department-Specific Settings - Separate active settings for different organizational units
- Geographic Separation - Location-based configuration for multi-site organizations
- Program-Specific Setup - Different settings for different care programs
- Tenant Isolation - Complete separation for multi-tenant implementations
Change Management Process:
- Development Environment - Test all configuration changes in sandbox
- User Acceptance Testing - Validate changes with key stakeholders
- Staged Rollout - Deploy to pilot groups before organization-wide implementation
- Training and Communication - Ensure teams understand configuration changes
- Monitoring and Support - Track performance and provide ongoing assistance
Best Practices:
- Configuration Documentation - Maintain comprehensive documentation of all settings
- Change Control - Formal approval process for configuration modifications
- Backup Strategy - Maintain backup configurations for emergency rollback
- Performance Monitoring - Track system performance impact of configuration changes
- User Feedback - Regular collection and incorporation of user feedback
ποΈ Remember: The settings dashboard is the control center for your entire care management system. Take time to understand each section thoroughly and test all configurations before deploying to production. Regular review and optimization ensure your system continues to meet organizational needs as you grow.
π Related Documentation:
- βοΈ Settings & Configuration - Basic settings overview and quick setup
- βοΈ Workflows & Automation - Automation integration with settings
- π± Text Messaging System - SMS configuration and Custom Settings
- π¨ Templates & Customization - Organizational adaptation strategies