Concorbit HelpAll guides →

Module Management

Module Management

concorbit is organised into modules, discrete feature sets that you can activate or deactivate based on your team's needs. The Modules page gives you a visual overview of every available module and lets you toggle them on or off.

URL: /settings/modules
Required permission: settings.tenant

Accessing Module Management

  1. Go to Settings from the sidebar.

  2. Click the Modules card (described as "Activate and manage platform modules").

Page Layout

The Modules page displays:

  • Header with the total active count (e.g., "12 of 18 active") and a progress bar.

  • Module cards grouped by category, each with a toggle switch.

Module Categories

Modules are organised into logical groups:

CategoryDescription
CoreEssential platform features that are always active.
BusinessOperational tools for running your business.
CommunicationTools for connecting with clients and contacts.
DataTools for organising, analysing, and reporting on data.

Module Card Anatomy

Each module card shows:

  • Icon: a colour-coded icon representing the module.

  • Name: the module's display name.

  • Description: a one-line summary of what the module does.

  • Badge: indicates the module's status:

    • Always on: core modules that cannot be deactivated.

    • concorbit: available on the concorbit tier and above.

    • Pro: requires the concorbit Pro tier.

    • Agency: requires the Agency tier.

    • Coming soon: placeholder for modules not yet available.

  • Toggle switch: turn the module on (coloured) or off (grey).

  • Left colour bar: active modules display a coloured left border.

Click a module card to expand it and see:

  • Feature list: bullet points describing what the module includes.

  • Dependencies: other modules required for this one to function (e.g., "Requires: CRM").

Activating a Module

  1. Find the module in the grid.

  2. Click its toggle switch. The switch turns coloured to indicate the module is active.

  3. The module's features immediately become available in the sidebar and throughout the workspace.

No page reload is required. The activation is instant.

Deactivating a Module

  1. Click the toggle switch on an active module to turn it off.

  2. The module's features are immediately hidden from the sidebar and workspace.

Impact of Deactivation

  • Data is preserved. Deactivating a module does not delete any data. If you reactivate the module later, all your records will still be there.

  • Sidebar and navigation. The module's menu items are hidden from all users.

  • Permissions. Permissions related to the deactivated module have no effect while it is off, but they are not removed from roles. They become active again if the module is reactivated.

  • Webhooks and integrations. Webhook events related to the deactivated module will stop firing.

  • Portal. Any portal sections tied to the deactivated module are hidden from portal users.

Tier Gating

Some modules are restricted to higher subscription tiers. When a module requires a tier above your current subscription:

  • The toggle switch is replaced with a lock icon.

  • A link below the card says "Upgrade to Pro" or "Upgrade to Agency" and links to the Subscription page.

Tier Requirements

TierWhat it unlocks
concorbitCore modules, CRM, basic Billing, basic Email, Files
concorbit ProEverything in concorbit plus Vault, advanced Email (campaigns), Docs, Projects, Forms, Helpdesk
concorbit AgencyEverything in concorbit Pro plus sub-tenant management, automation, analytics, advanced portal features

The exact module-tier mapping may evolve. The Modules page always shows the current requirements.

Module Dependencies

Some modules depend on others. For example, a module might require the CRM module to be active because it relies on contact data.

Dependencies are shown in the expanded card detail:

Requires: CRM, Email

If you try to deactivate a module that other active modules depend on, concorbit will warn you. Deactivating the dependency may automatically deactivate dependent modules as well.

Always-Active Modules

Core modules (marked "Always on") are essential to the platform's operation and cannot be deactivated. These typically include:

  • Dashboard

  • User management

  • Settings infrastructure

  • Notifications

Platform Tenant

The platform tenant (the concorbit system workspace) has access to all modules regardless of tier, including all Pro and Agency modules. This is automatic and does not require a subscription.

Available Modules Reference

Below is a reference of the modules available in concorbit. The exact list may change as new modules are developed.

Core (Always Active)

  • Dashboard: workspace overview with key metrics and activity feed.

  • Settings: workspace and user configuration.

  • Notifications: in-app notification centre.

  • User Management: team member accounts and role assignment.

Business

  • CRM: contact, company, deal, task, and appointment management. The foundation for most other modules. Available on all tiers.

  • Billing: invoices, credit notes, products, subscriptions, payment collection, and Stripe Connect integration. Available on all tiers.

  • Vault: encrypted password and secret storage with tiered folder access (Staff, Management, Director). Requires concorbit Pro tier or above.

  • Projects: project and task management with timelines. Requires concorbit Pro tier or above.

  • Proposals: create and send professional proposals to clients. Available on all tiers.

Communication

  • Email: email campaigns, templates, mailing lists, segmentation, and send analytics. Basic email (transactional) is available on all tiers; advanced campaigns require concorbit Pro.

  • Portal: client self-service portal for viewing invoices, documents, vault items, and sending messages. Available on all tiers with enhanced features on higher tiers.

  • Messages: internal messaging and client communication. Available on all tiers.

  • Secure Send: encrypted file and message sharing with external recipients. Requires concorbit Pro tier or above.

Data

  • Docs: internal and publishable documentation with a rich editor. Requires concorbit Pro tier or above.

  • Forms: custom form builder for lead capture, surveys, and data collection. Requires concorbit Pro tier or above.

  • Helpdesk: support ticket management. Requires concorbit Pro tier or above.

  • Analytics: advanced reporting and data visualisation. Requires Agency tier.

  • Automation: workflow automation with triggers and actions. Requires Agency tier.

Coming Soon

Modules marked "Coming soon" appear as greyed-out placeholder cards. They cannot be activated yet but are shown so you can see what is on the roadmap.

Modules and Permissions

Each module registers its own set of permissions (e.g., crm.view, crm.create, vault.reveal). When a module is deactivated:

  • The permissions still exist in role definitions.

  • They have no practical effect because the module's features are hidden.

  • When the module is reactivated, the permissions take effect again.

This means you can configure roles with permissions for modules you plan to activate later, without those permissions causing errors in the meantime.

Modules and the Portal

Modules directly affect what portal users can see:

  • CRM active + Portal active: Portal users can view their contact record.

  • Billing active + Portal active: Portal users can view and pay invoices.

  • Vault active + Portal active: Portal users can view vault items shared with them.

  • Docs active + Portal active: Portal users can read published documentation.

Deactivating a module hides its portal section automatically.

Troubleshooting

"A module I need shows a lock icon"

Your workspace is on a tier that does not include this module. Click the "Upgrade to [tier]" link below the card to go to the Subscription page and upgrade.

"I toggled a module but nothing changed in the sidebar"

Try refreshing the page. Module activation is instant, but the sidebar may need a page reload to reflect the change.

"A module says 'Requires: CRM' but CRM is active"

Ensure both the dependency and the dependent module are active. If the dependency was recently activated, try refreshing the page.