Understanding the Module System

Learn how Piraja CRM's module system works. Understand the two-level access system, how to enable and disable modules, module dependencies, and best practices for module management.

Published 11/16/2025Updated 11/16/20257 min read

What Are Modules?

Overview

Modules are specialized features in Piraja CRM that provide specific functionality. Instead of a one-size-fits-all approach, you can enable only the modules your business needs, creating a customized CRM experience.

Examples of Modules:

  • Individuals: Contact management
  • Organizations: Company management
  • Tickets: Support ticket system
  • Opportunities: Sales pipeline
  • Services: Service catalog
  • Billables: Invoice management
  • Calendar: Event scheduling
  • Aiden: AI assistant

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 unreleased modules
  • 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, Billables

Support Team Member:

  • Show: Tickets, Individuals, Notes
  • Hide: Pipeline, Opportunities, Agreements

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:

  • Access unreleased modules
  • Override system-disabled modules
  • Affect other businesses' settings

Module Selection Guide

Essential Modules (Most Businesses):

  • Individuals
  • Organizations
  • Notes
  • Tasks

Sales-Focused:

  • Opportunities
  • Pipeline
  • Agreements
  • Organizations

Service-Focused:

  • Tickets
  • Services
  • Billables
  • Individuals

Productivity:

  • Calendar
  • Tasks
  • Notes
  • Storage

Integrations:

  • Google Calendar (requires Calendar)
  • Outlook Calendar (requires Calendar)
  • 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

Consider Your Plan:

  • Free plan has limited modules
  • Pro plan includes more modules
  • Enterprise plan has all modules

Think About Dependencies:

  • Some modules require others
  • Check dependencies before disabling
  • Plan module combinations

Module Dependencies

Understanding Dependencies

Some modules require others to function:

Calendar Integrations:

  • Google Calendar requires Calendar module
  • Outlook Calendar requires Calendar module
  • You cannot enable integrations without Calendar

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 Calendar disables all calendar integrations
  • Disabling Organizations disables BRREG

Common Dependency Patterns

Base Module → Integration:

  • Calendar → Google Calendar
  • Calendar → Outlook Calendar
  • 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)
  • Agreements (Contract management)
  • Billables (Invoice management)
  • Services (Service catalog)

Support & Operations

Customer Service:

  • Tickets (Support tickets)
  • Tasks (Task management)
  • Notes (Documentation)
  • Storage (File management)

Calendar & Communication

Scheduling:

  • Calendar (Event management)
  • Google Calendar (Integration)
  • Outlook Calendar (Integration)

Communication:

  • Communication (Multi-channel messaging)

Content & Marketing

Content Management:

  • CMS (Content management)
  • AI Integration (AI content)
  • Facebook (Social media)
  • Instagram (Social media)

Analytics & Intelligence

Business Intelligence:

  • Performance (Business analytics)
  • Aiden (AI assistant)

Plan Tiers and Module Access

Free Plan

Included Modules:

  • Core CRM modules
  • Basic features
  • Limited users
  • Community support

Module Limitations:

  • Some advanced modules unavailable
  • Limited integrations
  • Basic functionality

Pro Plan

Included Modules:

  • All core modules
  • Advanced features
  • More integrations
  • Priority support

Module Access:

  • Most modules available
  • Advanced integrations
  • Enhanced features

Enterprise Plan

Included Modules:

  • All modules
  • All features
  • All integrations
  • Dedicated support

Module Access:

  • Unlimited module access
  • Custom integrations
  • Advanced security

Upgrading Plans

To Access More Modules:

  1. Review your current plan
  2. Check module requirements
  3. Upgrade if needed
  4. Enable new modules

Troubleshooting

Common Issues

Module Not Appearing:

  • Check business-level: Is module enabled?
  • Check user-level: Is module enabled for you?
  • Verify your plan includes the module

Can't Enable Module:

  • Business admin may have disabled it
  • Business admin may have disabled it
  • Your plan may not include it
  • Check for dependencies

Module Disabled But Still Visible:

  • May be cached, refresh page
  • Check both access levels
  • Verify you're checking correct level

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
  • Review plan limitations
  • 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:

  • Understand plan limitations
  • 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
Was this helpful?