Extensions Directory

Extensions are installable packages which give CiviCRM new functionality, and this directory provides a centralized list of extensions which the CiviCRM community has created. This listing displays CiviCRM extensions that work on all Content Management Systems (CMS).

The newest extensions · Create an extension · Add an extension to this directory

Platform integrations

As well as extensions that install within CiviCRM and work on all CMSs listed below, you can browse directories of integrations that are made specifically for Backdrop, Drupal, Joomla and WordPress.

Current Usage: 7
This extension add the nationality field to individuals. The option group is filled from a text file in the extension.
Current Usage: 7
Current Usage: 7
Extension to print the Member Book according to the Italian law for Associations an Co-operatives.
Current Usage: 6
CoShares is a front end for CiviShares. This extension provides custom data fields and configuratoin that is used by CoShares.
Current Usage: 6
The extension allows you to manage different resources in CiviCRM - such as staff and volunteers or rooms and materials. It provides an UI to define resources and demands and an algorithm to match them.
Current Usage: 6
Campaign Manager (Next Generation) is an upgraded version from the original extension de.systopia.campaign.
Current Usage: 6
Restricts payment methods to specific domains. For multisite CiviCRM instances.

This is especially helpful with accounting integration to ensure that your different sites all use payment methods tied to specific bank accounts.
Current Usage: 6
Allows generating CDN Tax Receipts via a CiviRules action.
Current Usage: 6
Shopify sync
Current Usage: 6
Combines the flexibility of Smart Groups with the utility of Static Groups.
Current Usage: 6
Developer's tool to automatically patch core CiviCRM files.
Current Usage: 6
Provides a way to record and monitor certifications that need periodic re-validation. For example, tracking First Aid certificates that need to be renewed every 3 years, or policy documents where you want to check people have read the latest version.
Current Usage: 6
On a production site, where your error settings are usually pretty low, errors from bad smarty code in message templates can disappear or on some sites it may go to the apache error log or somewhere not very easily findable by the user or even the site admin. This makes it hard to diagnose why messages aren't going out. There are some differences between what happens on different CMS's too, so this evens it out.
Current Usage: 6
Provides more strict permissions to Reports
Current Usage: 6