You are tasked with analyzing user categories and suggesting appropriate feature mappings based on role requirements and access control best practices. Your goal is to create comprehensive and secure feature mappings that align with each category's responsibilities.

Current Module: {module_name}
Tech Stack: {tech_stack}

User Category:
{category_details}

Available Features:
{available_features}

{custom_instruction}

IMPORTANT RESPONSE STRUCTURE:
1. First analyze the user category's:
   - Role and responsibilities
   - User type and level
   - Department context
   - Importance level
   - Workflow requirements

2. Then for each relevant feature, provide:
   - Feature ID and name
   - Recommended access level (read/write/admin)
   - Detailed justification for the mapping
   - Any security considerations
   - Related features that should also be mapped

Example Response Structure:

Feature Mapping Analysis for [Category Name]

Role Analysis:
- Primary responsibilities: [List key responsibilities]
- Workflow requirements: [List workflow needs]
- Security considerations: [List security requirements]
- Access patterns: [Describe how the user interacts with the system]

Recommended Feature Mappings:

1. [Feature Name] (feat_12345678)
Access Level: write
Function: func_87654321
Mapping Reason: Required for core job responsibilities including [specific tasks]
Security Notes: 
- Access limited to department-specific data
- Audit logging required for sensitive operations
Related Features:
- feat_23456789: Required for complete workflow
- feat_34567890: Supports primary function

2. [Feature Name] (feat_23456789)
Access Level: read
Function: func_98765432
Mapping Reason: Needed for viewing reference data and reports
Security Notes:
- Read-only access sufficient for requirements
- No sensitive data exposure
Related Features:
- feat_45678901: Complementary reporting feature

Access Level Guidelines:
- read: View-only access to data and functions
- write: Ability to create and modify data
- admin: Full control including configuration

Security Considerations:
1. Principle of Least Privilege
2. Separation of Duties
3. Need-to-Know Basis
4. Audit Requirements
5. Regulatory Compliance

Remember to:
1. Justify each mapping with clear reasoning
2. Consider security implications
3. Identify related features
4. Follow access control best practices
5. Consider workflow efficiency
6. Account for emergency scenarios
7. Address compliance requirements

If you cannot complete the analysis in one message, end your response with:
[TO BE CONTINUED]
Current completion: X%
Next section will cover: [brief description of what comes next]

Please provide a comprehensive analysis following this format, ensuring all mappings are properly justified and security considerations are addressed.