Piraja CRM uses a flexible module-based architecture that allows you to enable only the features you need. This guide explains how the module system works, the two-level access system (business + user), how to manage modules, and best practices for optimal configuration.
What Are Modules?
Overview
Modules are specialized features in Piraja CRM that provide specific functionality. Choose the plan that fits your team — Free, Plus, or Pro — and enable the modules your business needs within your plan for a customized CRM experience.
Examples of Modules:
- Individuals: Contact management
- Organizations: Company management
- Tickets: Support ticket system
- Opportunities: Sales pipeline
- Services: Service catalog
- Finance: Invoice and transaction management
- Pipeline: Visual sales pipeline
- Mailbox: Email management
- Storage: Cloud file management
- Notes: Universal notes
Why Modules?
Flexibility
- Enable only what you need
- Reduce interface clutter
- Focus on relevant features
Scalability
- Add modules as you grow
- Adapt to changing needs
- Pay only for what you use
Customization
- Tailor CRM to your workflow
- Role-specific module sets
- Department-specific configurations
Two-Level Access System
Business Level (Business Administrators)
Controls:
- Which modules your business can access
- Business-wide module availability
- Overrides user preferences
Question: "Can my team access this?"
Access: Business administrators
Use Cases:
- Enable modules your team needs
- Disable modules not relevant to your business
- Control costs by limiting module access
User Level (Individual Users)
Controls:
- Which modules appear in your navigation
- Personal module visibility
- Individual preferences
Question: "Do I want to see this?"
Access: All users
Use Cases:
- Hide modules you don't use
- Customize your interface
- Focus on your role's modules
How It Works
Both levels must allow access for a module to appear:
Business Enabled → User Enabled = Module Visible
If either level blocks access, the module won't appear.
Managing Modules as a User
Personal Module Management
Access: Navigate to /modules or Settings → Modules
What You Can Do:
- Toggle modules ON/OFF for your view
- Hide modules you don't use
- Show modules you need
What You Cannot Do:
- Enable modules disabled by business admin
- Access modules not enabled for your business
- Override business-level settings
When to Hide Modules
Hide modules when:
- You don't use them in your role
- They clutter your interface
- You want to focus on specific features
- They're handled by other team members
Example Scenarios:
Sales Team Member:
- Show: Organizations, Opportunities, Pipeline
- Hide: Tickets, Services, Finance
Support Team Member:
- Show: Tickets, Individuals, Notes
- Hide: Pipeline, Opportunities
Manager:
- Show: Most modules for visibility
- Hide: Only specific integrations you don't use
Managing Modules as a Business Administrator
Business Module Management
Access: Navigate to /business/modules or Business Settings → Modules
What You Can Do:
- Enable/disable modules for entire business
- View module pricing
- Manage paid module access
- See module usage analytics
What You Cannot Do:
- Enable modules not available for your subscription (contact support if you need access)
- Affect other businesses' settings
Module Selection Guide
Essential Modules (Most Businesses):
- Individuals
- Organizations
- Notes
- Tasks
Sales-Focused:
- Opportunities
- Pipeline
- Organizations
Service-Focused:
- Tickets
- Services
- Finance
- Individuals
Productivity:
- Tasks
- Notes
- Storage
Integrations:
- BRREG (requires Organizations)
Best Practices
Enable Based on Need:
- Don't enable everything "just in case"
- Users can hide modules themselves
- Review module usage periodically
Think About Dependencies:
- Some modules require others
- Check dependencies before disabling
- Plan module combinations
Module Dependencies
Understanding Dependencies
Some modules require others to function:
BRREG Integration:
- BRREG requires Organizations module
- Used for importing Norwegian companies
- Only works with Organizations enabled
Dependency Rules
When Enabling:
- System checks dependencies automatically
- You'll see warnings if dependencies missing
- Cannot enable without required modules
When Disabling:
- Check if other modules depend on it
- Disabling Organizations disables BRREG
Common Dependency Patterns
Base Module → Integration:
- Organizations → BRREG
Core → Advanced:
- Most modules work independently
- Some advanced features require core modules
Module Categories
Core CRM Modules
Customer Management:
- Individuals (Contact management)
- Organizations (Company management)
- BRREG (Norwegian business registry)
Sales & Revenue:
- Opportunities (Sales pipeline)
- Pipeline (Visual sales pipeline)
- Finance (Invoice and transaction management)
- Services (Service catalog)
Support & Operations
Customer Service:
- Tickets (Support tickets)
- Tasks (Task management)
- Notes (Documentation)
- Storage (File management)
Email & Communication
Mailbox:
- Mailbox (Unified email management, Gmail/Outlook/forwarding)
Integrations
Available integrations:
- BRREG (Norwegian business registry, requires Organizations)
Module Availability
How Module Access Works
Available modules depend on your subscription. Your business administrator can enable or disable modules for your organization; individual users can then show or hide modules in their own navigation.
If You Need More Modules:
- Contact your business administrator to enable modules for your business
- If a module is not available, contact support at support@piraja.io
- Ensure any required dependencies are enabled (e.g. Organizations for BRREG)
Troubleshooting
Common Issues
Module Not Appearing:
- Check business-level: Is the module enabled for your business? (Ask your business administrator)
- Check user-level: Is the module enabled for you? (Go to Settings → Modules and ensure it is toggled on)
- Refresh the page in case of caching
Can't Enable Module:
- Your business administrator may have disabled it for your organization
- The module may not be part of your subscription — contact support@piraja.io if you need access
- Check for dependencies (e.g. BRREG requires Organizations)
Module Disabled But Still Visible:
- May be cached; refresh the page
- Check both access levels (business and user)
Integration Not Working:
- Check base module is enabled
- Verify integration is enabled
- Check integration configuration
- Review integration setup guide
Getting Help
For Users:
- Contact business administrator
- Check Knowledge Base
- Review module guides
For Business Admins:
- Contact support at support@piraja.io
- Check module documentation
Best Practices
For Users
Module Management:
- Hide modules you don't use
- Keep interface clean and focused
- Enable modules as you need them
- Review module visibility regularly
Role-Based Configuration:
- Sales: Enable sales modules
- Support: Enable support modules
- Management: Enable most modules
For Business Administrators
Strategic Enablement:
- Enable based on business needs
- Consider different departments
- Review module usage analytics
- Don't enable "just in case"
Cost Management:
- Enable only what you need
- Monitor module usage
- Optimize module selection
Team Communication:
- Communicate module changes
- Explain why modules are enabled/disabled
- Provide training on new modules
- Gather feedback from team