---
title: Community Support Policy
---

**COMMUNITY SUPPORT FRAMEWORK AND GUIDELINES**

## 1. POLICY OVERVIEW AND PURPOSE

### 1.1. Policy Statement

This Community Support Policy establishes the framework for how community members can both seek and provide support within our community ecosystem. This policy is designed to create a safe, inclusive, and mutually supportive environment that honours our values of social justice, accessibility, and community empowerment whilst maintaining appropriate boundaries and safety standards.

### 1.2. Integration with Community Values

**Core Principles:**
- **Mutual Support**: Community members support each other through shared experiences and knowledge
- **Trauma-Informed Approach**: Recognition that many community members may have experienced trauma
- **Inclusive Access**: Support is available to all community members regardless of identity, ability, or circumstances
- **Boundary Respect**: Clear boundaries between peer support and professional services
- **Safety First**: Protection of vulnerable community members and support providers
- **Cultural Responsiveness**: Respect for diverse cultural approaches to support and healing

### 1.3. Scope and Application

This policy applies to all forms of support exchange within our community platforms, including:
- Discord channels and direct messages
- Reddit community spaces
- Social media interactions
- GitHub collaborative spaces
- LinkedIn professional networking
- Any other community-operated platforms

## 2. SEEKING SUPPORT WITHIN THE COMMUNITY

### 2.1. Types of Community Support Available

#### 2.1.1. Peer Support Categories

**Emotional and Social Support:**
- Listening and empathy from community members with shared experiences
- Connection with others who understand similar challenges
- Celebration of achievements and milestones
- Social interaction and friendship building
- Community during difficult times

**Informational and Resource Support:**
- Sharing of knowledge, resources, and information
- Guidance on community platforms and tools
- Technical assistance and troubleshooting
- Educational support and learning opportunities
- Resource referrals and recommendations

**Technical Product Support:**
- Assistance with community-developed software and tools
- Bug reporting and troubleshooting for community applications
- Feature requests and enhancement suggestions
- Documentation clarification and improvement
- API usage guidance and integration support
- Open source contribution guidance and code review

**Practical Support:**
- Assistance with community projects and initiatives
- Collaborative problem-solving on shared challenges
- Skill sharing and mentorship opportunities
- Accessibility assistance and accommodation support (request accommodations via our [Accessibility Accommodation Request Form](https://forms.nhcarrigan.com/o/docs/forms/2FXY87PB6aaMHspcnXYCZX/4))
- Platform-specific guidance and orientation

#### 2.1.2. Specialised Support Areas

**Identity-Based Support:**
- Support groups for specific identities and experiences
- Culturally responsive support for marginalised communities
- LGBTQ+ affirming support and resources
- Neurodiversity-affirming spaces and assistance
- Support for survivors of various forms of trauma

**Professional and Educational Support:**
- Career development guidance and networking
- Educational resource sharing and study groups
- Professional skill development and mentorship
- Open source contribution guidance
- Technical learning and development support

**Technical Product and Development Support:**
- Community software and application troubleshooting
- Development environment setup and configuration
- Code review and programming mentorship
- API documentation and implementation guidance
- Bug triage and feature development collaboration

**Technical Product and Development Support:**
- Community software and application troubleshooting
- Development environment setup and configuration
- Code review and programming mentorship
- API documentation and implementation guidance
- Bug triage and feature development collaboration

### 2.2. How to Seek Support

#### 2.2.1. Identifying Appropriate Support Channels

**Platform-Specific Guidelines:**
- **Discord Forums**: Create posts in appropriate forum channels with clear, descriptive titles
- **Reddit**: Utilise community-specific support threads and appropriate flair
- **GitHub**: Use issue templates for bug reports, feature requests, and technical support
- **Social Media**: Engage appropriately with community hashtags and threads

**Support Request Best Practices:**
- **Be Specific**: Clearly describe what type of support you're seeking (emotional, technical, informational, etc.)
- **Provide Context**: Include relevant details, error messages, or screenshots for technical issues
- **Respect Boundaries**: Understand that community members are volunteers with limited capacity
- **Use Appropriate Channels**: Choose the right platform and channel for your specific need
- **Be Patient**: Allow time for community members to respond and engage
- **Show Appreciation**: Acknowledge and thank those who provide support
- **Follow Up**: Update the community on resolution or continued needs when appropriate

#### 2.2.2. Technical Support Specific Guidelines

**For Product and Development Issues:**
- **Include System Information**: Provide relevant system details (OS, browser version, device type)
- **Reproduce the Issue**: Document steps to reproduce the problem consistently
- **Check Documentation First**: Review available documentation and FAQs before requesting help
- **Provide Error Messages**: Include complete error messages and stack traces when available
- **Share Code Snippets**: For integration issues, provide relevant code snippets (sanitized of sensitive data)
- **Version Information**: Specify which version of the product or API you're using
- **Expected vs Actual**: Clearly describe what you expected to happen versus what actually occurred

**Best Practices for Technical Support Requests:**
- **Use Appropriate Templates**: Follow issue templates or discussion formats when available
- **Search Existing Issues**: Check if your issue has already been reported or resolved
- **One Issue Per Request**: Keep support requests focused on a single problem
- **Provide Screenshots**: Include screenshots or screen recordings when they help illustrate the issue
- **Test Environment**: Specify if you're using development, staging, or production environments
- **Recent Changes**: Note any recent changes to your setup that might be related to the issue

#### 2.2.3. Emergency and Crisis Support

:::tip[Heads Up!]{icon=pen}
The policy or policies in this section are still a work in progress. We have not yet implemented the necessary infrastructure to comply with this section.

We are working very hard to get them in place as soon as possible. If you would like to help, consider [applying to join our team!](https://forms.nhcarrigan.com/o/docs/forms/mCxDu3snk9TzFiDjrT4Vc8/4)
:::

**Important Limitations:**
- Community members are **NOT** mental health professionals
- Peer support does **NOT** replace professional mental health services
- For mental health emergencies, contact professional crisis services immediately
- Community support is supplemental to, not a replacement for, professional care

**Crisis Resource Integration:**
- Immediate connection to crisis hotlines and professional services
- Clear escalation procedures for serious concerns
- Staff notification protocols for safety concerns
- Integration with our Crisis and Mental Health Management Policy
- Resource databases for professional services and emergency support

### 2.3. Receiving Support Effectively

#### 2.3.1. Engagement Guidelines

**Active Participation:**
- **Communicate Clearly**: Share what you need and what would be helpful
- **Be Open to Different Perspectives**: Community members bring diverse experiences and viewpoints
- **Respect Advice Boundaries**: Understand the difference between peer support and professional advice
- **Engage Authentically**: Be genuine whilst maintaining appropriate privacy boundaries
- **Follow Through**: Let supporters know how their assistance worked out when appropriate

**Privacy and Safety:**
- **Share Appropriately**: Only share what you're comfortable having known by community members
- **Maintain Boundaries**: You are not obligated to share personal details or follow all advice
- **Report Concerns**: If support interactions become inappropriate, contact staff immediately
- **Protect Others' Privacy**: Respect the privacy of others who may be mentioned in your support requests

#### 2.3.2. Managing Multiple Support Sources

**Coordination Strategies:**
- **Professional Services First**: Prioritise professional mental health, medical, or legal services when needed
- **Community Support as Supplement**: Use community support to complement, not replace, professional services
- **Avoid Overwhelming Supporters**: Be mindful of the capacity and boundaries of community volunteers
- **Update Supporters**: Let community supporters know when situations change or resolve

## 3. PROVIDING SUPPORT TO COMMUNITY MEMBERS

### 3.1. Peer Support Responsibilities and Boundaries

#### 3.1.1. Role Definition and Limitations

**What Peer Support IS:**
- Sharing personal experiences and what has worked for you
- Listening with empathy and without judgement
- Providing resources and information from your own knowledge
- Offering practical assistance within your capacity and expertise
- Being present and available when you can be
- Connecting people with others who might have relevant experience
- Providing technical assistance with community products and tools
- Helping troubleshoot software issues and bugs
- Sharing knowledge about APIs, documentation, and development practices

**What Peer Support is NOT:**
- Professional counselling, therapy, or mental health treatment
- Medical advice or diagnosis of any kind
- Legal advice or representation
- Financial advice or monetary assistance commitments
- Crisis intervention or emergency response services
- Solutions to complex problems requiring professional expertise

#### 3.1.2. Professional Boundary Maintenance

**Clear Communication About Limitations:**
- Always clarify that you are not a professional service provider
- Acknowledge when questions or needs exceed peer support scope
- Redirect to appropriate professional services when necessary
- Be honest about your own knowledge limitations and experience boundaries
- Avoid giving advice outside your areas of experience or expertise

### 3.2. Best Practices for Providing Support

#### 3.2.1. Effective Support Techniques

**Active Listening and Empathy:**
- **Listen First**: Focus on understanding before trying to solve or advise
- **Validate Experiences**: Acknowledge the person's feelings and experiences as valid
- **Ask Questions**: Clarify what type of support the person is seeking
- **Reflect Understanding**: Demonstrate that you understand what they're sharing
- **Avoid Minimising**: Don't downplay or dismiss concerns, even if they seem minor to you

**Resource Sharing and Information:**
- **Share Relevant Experience**: Offer insights from your own similar experiences when appropriate
- **Provide Resources**: Share helpful resources, websites, books, or tools you know about
- **Make Connections**: Introduce people to others who might have relevant experience or expertise
- **Follow Up**: Check in when appropriate to see how things are going
- **Maintain Confidentiality**: Respect privacy and don't share personal details with others

#### 3.2.3. Technical Support Best Practices

**Troubleshooting Methodology:**
- **Systematic Approach**: Work through problems systematically rather than jumping to conclusions
- **Reproduce First**: Attempt to reproduce the issue yourself when possible
- **Check Documentation**: Verify your understanding against official documentation
- **Test Solutions**: Test suggested solutions in safe environments before recommending
- **Know Your Limits**: Recognise when issues exceed your technical knowledge
- **Escalate Appropriately**: Direct complex technical issues to maintainers or core developers

**Code and Integration Support:**
- **Code Review Guidelines**: Provide constructive feedback on code snippets and implementations
- **Security Awareness**: Be mindful of security implications in code suggestions
- **Best Practice Sharing**: Share established best practices and coding standards
- **Testing Recommendations**: Suggest appropriate testing approaches for implementations
- **Performance Considerations**: Consider performance implications of suggested solutions
- **Documentation Updates**: Help improve documentation when gaps are identified

**API and Product Support:**
- **Version Compatibility**: Help users understand version requirements and compatibility
- **Rate Limiting**: Educate users about API rate limits and best practices
- **Authentication**: Assist with proper authentication and authorisation setup
- **Error Handling**: Help implement proper error handling and retry logic
- **Integration Patterns**: Share common integration patterns and examples
- **Deprecation Awareness**: Keep users informed about deprecated features and migration paths

#### 3.2.4. Cultural and Trauma-Informed Support

**Cultural Responsiveness:**
- **Respect Differences**: Acknowledge that cultural backgrounds shape experiences and coping strategies
- **Ask, Don't Assume**: Learn about individual preferences rather than making cultural assumptions
- **Honour Different Approaches**: Respect that there are many valid ways to cope and heal
- **Learn Continuously**: Be open to learning about experiences different from your own
- **Address Your Limitations**: Acknowledge when cultural differences are outside your experience

**Trauma-Informed Approach:**
- **Assume Possibility of Trauma**: Recognise that many people have experienced trauma
- **Prioritise Safety**: Create interactions that feel safe and non-threatening
- **Offer Choice and Control**: Let people make their own decisions about sharing and participation
- **Emphasise Collaboration**: Work with people rather than directing or controlling their experience
- **Build Trust**: Be reliable, consistent, and honest in your interactions

### 3.3. Support Provider Self-Care and Sustainability

#### 3.3.1. Managing Your Own Capacity

**Setting Healthy Boundaries:**
- **Know Your Limits**: Be realistic about your time, energy, and emotional capacity
- **Communicate Availability**: Be clear about when and how you're available to provide support
- **Practice Saying No**: It's okay to decline support requests when you're not available or able
- **Take Breaks**: Regular breaks from support provision are healthy and necessary
- **Seek Your Own Support**: Support providers need support too - don't hesitate to seek it

**Preventing Burnout:**
- **Distribute Support Load**: Encourage multiple people to provide support rather than taking everything on yourself
- **Recognise Warning Signs**: Know the signs of emotional exhaustion and burnout
- **Practice Self-Care**: Maintain your own well-being through whatever practices work for you
- **Professional Support**: Seek professional support for your own challenges when needed
- **Community Among Supporters**: Connect with other support providers for mutual support

#### 3.3.2. Handling Difficult Support Situations

**When to Escalate to Staff:**
- **Safety Concerns**: Any indication of immediate danger to self or others
- **Harassment or Abuse**: Inappropriate behaviour during support interactions
- **Professional Service Needs**: Situations clearly requiring professional intervention
- **Boundary Violations**: When support requests become inappropriate or overwhelming
- **Community Policy Violations**: Any behaviour that violates community standards

**Managing Challenging Interactions:**
- **Stay Calm**: Maintain composure even when interactions become difficult
- **Redirect Appropriately**: Guide people to more appropriate resources when needed
- **Document Concerns**: Keep records of concerning interactions for staff review
- **Seek Consultation**: Ask staff or experienced community members for guidance when unsure
- **Protect Yourself**: Prioritise your own safety and well-being in all interactions

## 4. PLATFORM-SPECIFIC SUPPORT GUIDELINES

### 4.1. Discord Support Protocols

#### 4.1.1. Channel Organisation and Usage

**Designated Support Channels:**
- **#support**: General questions and peer support requests
- **#support-ticket**: Technical assistance and troubleshooting
- **#accessibility**: Accessibility-related assistance and resources (for accommodation requests, use our [Accessibility Accommodation Request Form](https://forms.nhcarrigan.com/o/docs/forms/2FXY87PB6aaMHspcnXYCZX/4))
- **Identity-specific channels**: Support spaces for specific communities and identities

**Direct Message Guidelines:**
- **Respect Consent**: Always ask before moving support to direct messages
- **Maintain Documentation**: Keep records of concerning interactions for staff review
- **Escalation Protocols**: Know when and how to involve Discord moderators and staff
- **Privacy Protection**: Respect confidentiality whilst ensuring safety

#### 4.1.2. Discord-Specific Safety Measures

**Moderation Integration:**
- **Staff Notification**: Clear processes for alerting staff to concerning situations
- **Emergency Protocols**: Immediate escalation procedures for crisis situations
- **Evidence Preservation**: Proper documentation of problematic interactions
- **Community Protection**: Mechanisms for protecting vulnerable community members

### 4.2. Discord Forum Channels and Reddit Support

#### 4.2.1. Public Support Best Practices

**Post Guidelines:**
- **Descriptive Titles**: Clear titles that indicate the type of support needed
- **Appropriate Categorisation**: Use correct flairs and categories for support requests
- **Privacy Considerations**: Share only what you're comfortable being public
- **Follow-Up Responsibility**: Update threads when situations resolve or change

**Response Guidelines:**
- **Constructive Contributions**: Ensure responses are helpful and supportive
- **Avoid Speculation**: Don't make assumptions or diagnose situations
- **Resource Sharing**: Provide links to helpful resources and information
- **Respectful Disagreement**: Handle differing perspectives constructively

#### 4.2.2. Community Upvoting and Visibility

**Helpful Content Promotion:**
- **Upvote Helpful Responses**: Use voting systems to promote good support
- **Share Valuable Resources**: Promote posts that provide helpful information
- **Community Curation**: Help ensure quality support content is visible
- **Constructive Feedback**: Provide feedback that improves support quality

### 4.3. Professional Platform Support (LinkedIn, GitHub)

#### 4.3.1. Professional Context Considerations

**LinkedIn Support:**
- **Professional Boundaries**: Maintain appropriate professional boundaries
- **Career Development**: Focus on career-related support and networking
- **Skill Sharing**: Professional skill development and knowledge sharing
- **Networking Ethics**: Responsible networking and professional relationship building

**GitHub Collaboration:**
- **Technical Support**: Code-related assistance and collaboration
- **Bug Reports and Issues**: Help with creating detailed bug reports and issue descriptions
- **Pull Request Review**: Collaborative code review and improvement suggestions
- **Open Source Contribution**: Guidance on contributing to projects
- **Documentation Support**: Help with technical documentation and resources
- **Learning Facilitation**: Supporting technical learning and development
- **API Integration**: Assistance with integrating community APIs and services

#### 4.3.2. Code-Specific Technical Support

**Issue Management:**
- **Issue Templates**: Use and help others use appropriate issue templates
- **Label Usage**: Apply appropriate labels to categorise issues effectively
- **Milestone Tracking**: Help track issues against project milestones and releases
- **Duplicate Detection**: Identify and link duplicate issues to reduce fragmentation
- **Triage Assistance**: Help maintainers triage and prioritise issues
- **Resolution Documentation**: Document solutions and workarounds in issue comments

**Code Collaboration:**
- **Fork and Branch Strategy**: Guide contributors through proper fork and branch workflows
- **Commit Message Standards**: Help maintain consistent commit message formatting
- **Code Style Compliance**: Assist with code style and linting requirements
- **Testing Requirements**: Guide contributors through testing requirements and procedures
- **CI/CD Pipeline**: Help troubleshoot continuous integration and deployment issues
- **Release Process**: Support community members through release and deployment procedures

**Documentation and Knowledge Sharing:**
- **README Improvements**: Help improve project README files and getting started guides
- **Code Comments**: Encourage and assist with proper code documentation
- **Wiki Maintenance**: Contribute to and maintain project wikis and knowledge bases
- **Tutorial Creation**: Support creation of tutorials and learning materials
- **FAQ Updates**: Help maintain and update frequently asked questions
- **Example Code**: Provide and maintain example implementations and use cases

## 5. SAFETY AND RISK MANAGEMENT

### 5.1. Identifying and Managing Risk

#### 5.1.1. Risk Assessment for Support Situations

**High-Risk Indicators:**
- **Immediate Safety Concerns**: Threats of self-harm or harm to others
- **Crisis Situations**: Mental health crises requiring professional intervention
- **Harassment or Abuse**: Reports of harassment, abuse, or exploitation
- **Boundary Violations**: Repeated violations of support boundaries
- **Professional Service Needs**: Situations requiring legal, medical, or mental health professionals
- **Security Vulnerabilities**: Reports of security issues requiring immediate attention
- **System Compromise**: Indications of compromised accounts or systems
- **Data Breach Concerns**: Potential data security or privacy violations

**Escalation Protocols:**
- **Immediate Staff Notification**: Contact staff immediately for high-risk situations
- **Documentation Requirements**: Proper documentation of concerning interactions
- **Resource Provision**: Connection to appropriate professional services
- **Follow-Up Procedures**: Ongoing monitoring and support coordination
- **Community Protection**: Measures to protect vulnerable community members

#### 5.1.3. Technical Support Risk Management

**Security-Related Support Risks:**
- **Credential Exposure**: Prevent sharing of passwords, API keys, or other sensitive credentials in support channels
- **Code Injection**: Be cautious of code suggestions that could introduce security vulnerabilities
- **Malicious Code**: Screen for and prevent sharing of potentially malicious code or links
- **Social Engineering**: Recognise and prevent social engineering attempts disguised as support requests
- **Phishing Prevention**: Help community members identify and avoid phishing attempts

**Technical Support Safety Protocols:**
- **Sandbox Testing**: Encourage testing of solutions in safe, isolated environments
- **Backup Reminders**: Always recommend backups before making significant changes
- **Production Warnings**: Clearly identify when suggestions should not be used in production
- **Version Control**: Encourage use of version control for tracking changes
- **Rollback Plans**: Help users understand how to reverse changes if needed
- **Documentation Requirements**: Ensure critical changes are properly documented

#### 5.1.2. Community Safety Measures

**Protective Policies:**
- **Harassment Prevention**: Clear policies preventing exploitation of vulnerable community members
- **Privacy Protection**: Safeguarding personal information shared in support contexts
- **Boundary Enforcement**: Enforcement of healthy boundaries between supporters and those seeking support
- **Staff Oversight**: Regular staff monitoring and oversight of support interactions
- **Community Feedback**: Mechanisms for reporting concerning support interactions

### 5.2. Crisis Intervention and Professional Referral

#### 5.2.1. Crisis Recognition and Response

**Crisis Identification:**
- **Warning Signs**: Recognition of signs indicating professional intervention needs
- **Risk Assessment**: Quick assessment of immediate safety concerns
- **Appropriate Response**: Immediate connection to professional crisis services
- **Staff Coordination**: Coordination with community staff for ongoing support
- **Documentation**: Proper documentation for professional service providers

**Professional Service Integration:**
- **Resource Databases**: Comprehensive databases of professional services
- **Referral Processes**: Clear processes for connecting people to professional help
- **Ongoing Coordination**: Coordination between community support and professional services
- **Privacy Compliance**: Respect for privacy whilst ensuring safety
- **Follow-Up Support**: Continued community support alongside professional services

#### 5.2.2. Legal and Ethical Obligations

**Mandatory Reporting:**
- **Legal Requirements**: Compliance with local laws regarding mandatory reporting
- **Child Protection**: Special procedures for situations involving minors
- **Elder Abuse**: Protocols for elder abuse and exploitation situations
- **Immediate Danger**: Procedures when someone is in immediate physical danger
- **Law Enforcement Coordination**: Appropriate coordination with law enforcement when required

**Ethical Considerations:**
- **Informed Consent**: Clear communication about limitations of community support
- **Confidentiality Boundaries**: Understanding of when confidentiality must be broken
- **Professional Scope**: Clear boundaries about what community members can and cannot provide
- **Cultural Sensitivity**: Respect for cultural differences in approach to crisis and support
- **Community Values**: Alignment of all crisis response with community values and principles

## 6. QUALITY ASSURANCE AND CONTINUOUS IMPROVEMENT

### 6.1. Support Quality Standards

#### 6.1.1. Effective Support Characteristics

**Quality Indicators:**
- **Respectful Interaction**: All support interactions demonstrate respect and dignity
- **Appropriate Boundaries**: Clear maintenance of peer support boundaries
- **Resource Accuracy**: Accurate and helpful resource sharing
- **Cultural Responsiveness**: Appropriate consideration of cultural differences
- **Safety Awareness**: Recognition and appropriate handling of safety concerns
- **Technical Accuracy**: Technically sound advice and solutions
- **Security Consciousness**: Awareness of security implications in technical recommendations
- **Documentation Quality**: Clear, accurate, and helpful technical documentation

**Feedback and Evaluation:**
- **Community Feedback**: Regular feedback collection from support recipients
- **Peer Evaluation**: Peer feedback amongst support providers
- **Staff Review**: Regular staff review of support quality and safety
- **Continuous Improvement**: Ongoing improvement of support practices and resources
- **Training Updates**: Regular updates to support training and resources

#### 6.1.2. Resource Maintenance and Updates

**Resource Quality Assurance:**
- **Regular Review**: Periodic review of shared resources for accuracy and relevance
- **Community Input**: Community input on resource effectiveness and needs
- **Professional Consultation**: Professional review of resource recommendations when appropriate
- **Accessibility Assessment**: Regular assessment of resource accessibility
- **Cultural Appropriateness**: Ongoing evaluation of cultural appropriateness of resources

### 6.2. Community Learning and Development

#### 6.2.1. Skill Building and Education

**Support Skills Development:**
- **Peer Education**: Educational opportunities for improving support skills
- **Cultural Competency**: Ongoing learning about cultural responsiveness
- **Trauma-Informed Approaches**: Education about trauma-informed support practices
- **Boundary Management**: Training on maintaining healthy support boundaries
- **Crisis Recognition**: Education about recognising crisis situations
- **Technical Competency**: Ongoing learning about products, APIs, and technical systems
- **Security Awareness**: Education about security best practices and threat recognition
- **Code Review Skills**: Training on effective and constructive code review practices

**Resource Development:**
- **Community-Generated Resources**: Support for community members creating helpful resources
- **Best Practice Documentation**: Documentation of effective support practices
- **Learning Opportunities**: Educational opportunities related to community support
- **Skill Sharing**: Opportunities for community members to share relevant skills and knowledge
- **Professional Development**: Support for community members pursuing relevant professional development

#### 6.2.2. Innovation and Improvement

**Support System Evolution:**
- **New Approach Development**: Innovation in peer support approaches and methods
- **Technology Integration**: Appropriate use of technology to improve support access and quality
- **Community Needs Assessment**: Regular assessment of community support needs
- **Best Practice Research**: Research into effective peer support practices
- **Community Adaptation**: Adaptation of support approaches based on community feedback and needs

**Partnership and Collaboration:**
- **Professional Service Partnerships**: Appropriate partnerships with professional service providers
- **Community Organisation Collaboration**: Collaboration with other community organisations
- **Resource Sharing Networks**: Participation in resource sharing networks
- **Best Practice Communities**: Participation in communities focused on peer support best practices
- **Research Participation**: Appropriate participation in research on effective community support

---

*This Community Support Policy is designed to create a safe, supportive, and sustainable framework for mutual aid within our community. This policy works in conjunction with our Crisis and Mental Health Management Policy, Community Code of Conduct, and staff training materials to ensure comprehensive community support. For questions about this policy or to report concerns about support interactions, please contact community staff through established channels.*

