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.

This extension provides password expire functionality to CiviCRM standalone.

Once a password is expired the user can still login but has to set a new password after logging in.

With scheduled reminders once can setup e-mails to remind people to set a new password or to inform them that their password is expired.
Current Usage:
The Postmark bounce handler CiviCRM extension helps track email bounces by listening for webhooks from the Postmark mail server and adding a contact activity indicating that the email bounced. The specific details regarding why the email bounced are logged as well.
Current Usage:
Adds an input type of "Signature" to file fields in FormBuilder.
Current Usage:
This extension aims to be a toolkit to help you comply with the GDPR.

What does it do?

The core of this toolkit is a new custom group where you can store consent records with your contacts. These records can be explicit or implicit consent, opt-outs, and similar things.

It integrates neatly with the UI, and gives you some search and data entry helpers.

Each record has the following fields:

date and time
category (e.g. "newsletter")
source (e.g. "main website")
type (e.g. "opt-in", "opt-out", "soft opt-in")

In addition, there are also some optional fields for each consent record:

expiry date (consent expires after the given date/time)
terms and conditions. (the full text of the TOC that the user agreed to*)
note (in case you want to add a remark)

(*) it has a clever mechanism so that it doesn't store the same TOC text over and over.
How do I use this?

Since the actions or consequences derived from the collected data differ greatly between organisations, this toolkit doesn't do anything automatically. However, it can be used as a basis for further automation, e.g. by using the SQL Tasks extension to tag contacts for deletion if the basis for a contact's retention is not there anymore.


That's it?

Yes and no. There are some additional features that might interest you as a developer:

- There is a feature to make the communication preferences read-only, in case you want to derive them from the contact's consent record.
- There is a fully functioning API
- It defines a custom hook to be triggered if the consent records are modified for a contact. This way you can add code update the contact's permissions/subscripts/whatever right away.

What's next?

We'll keep on extending the built-in functionality of this extension, while aiming to keep it compatible with earlier versions. However, since the implementation of the GDPR is very specific to the individual organisation, this will never be "plug&play" solution for any user.

Feel free to raise ticket if you have a question.
Current Usage:
MapIt UK is an API service which matches points and boundaries. In this extension, it is being called to map data against UK postcodes held in the CiviCRM address fields.
Current Usage:
Fixes contact matching when individuals and organizations share the same email address during on-behalf-of contributions
Current Usage:
Currently an empty repo for collaboration
Current Usage:
Provides extra settings to customize the Contact Reference search fields (autocomplete), such as which fields are used for searching, and which fields are displayed in the results.
Current Usage:
This extension creates contact records with recurring contributions from an exported customer list from iATS
Current Usage:
Provide a couple of tools to display a public counter based on the number of contacts in a group.
Current Usage:
This is an extension used to run unit tests. You wouldn't use it on a live site.
Current Usage:
Implements the shariff (https://github.com/heiseonline/shariff) buttons in the social network template. This allows admins to select from a variety of social network and styles, to be displayed instead of the default buttons from core. This extension is complaint with the GDPR.
Current Usage:
Lightweight theme for the CiviCRM admin interface. <strong>It is no longer actively supported and has been replaced by RiverLea: HackneyBrook.</strong>
Current Usage: 229
Adds the Nominatim OpenStreetMap server as a geocoding option.
Current Usage: 128
processor plugin but no longer recommended
Current Usage: 1