New Extensions

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 were recently added to this extension directory. We also have an RSS feed. Click here to return to the extension directory.

With this extension you can give constituents access to their CiviCRM data without them needing a Drupal account.

This extension has been created with the following use case in mind: Let people read and change their contact data in a drupal webform. To access the data, people need to enter their email address. A link to the prefilled webform will be sent to that email address if and only if the email address exists within CiviCRM.
Current Usage: 15
Implements a SearchKit display using leaflet.js for showing lat/lon on a map.
Current Usage:
The functional requirement for this extension is that the funding customer (https://www.domusmedica.be/) has a lot of situations where an individual becomes a member or registers for an event but wants his/her company to pay for this. Partially this is possible in core CiviCRM using soft credits (for memberships) but it is somewhat confusing. The user does not see the actual payer of the membership on the membership screens, and the invoice does not show the name of the actual member.

This extension allows another contact than the member to pay for a membership and another contact then the participant to pay for an event registration. The extension will show the actual contact paying in the membership and participant screens and will also add the name of the participant or member on the invoice.
Current Usage: 1
Manage shares in community enterprises.
Current Usage: 2
Processes AWS SES bounces and complaint notifications in CiviCRM. Uses native AWS bounce and complaint types instead of trying to match them to out of the box CiviCRM bounce types.
Current Usage: 54
This is a front-end theme with three-purposes:
- stops Bootstrap3 from loading on FormBuilder & SearchKit pages (by overwriting with a blank file). This is useful if you have a Bootstrap theme in your front-end that's trying to do things differently and there's clashes.
- removes most of CiviCRM's CSS beyond a few essential bits.
- uses CSS variables to style those 'essential bits' with goal of making it quick to style CiviCRM elements (buttons, input boxes, tables, etc) to match your front-end theme.

NB - this is a work-in-progress, tested only on the few specific front-end pages I needed it for. Please use at your own risk (and feel free to PR more 'essentials bits').
Current Usage: 5
Provides a dashboard widget with a chatbot trained on the CiviCRM documentation.
Current Usage: 1
When a new contribution recur is created by a contribution page store the contribution page ID also on the contribution recur entity.
Current Usage:
This is an extension used to run unit tests. You wouldn't use it on a live site.
Current Usage:
This Extensions aims to provide tools for a "European" interpretation of the "membership" concept. In the Anglo-Saxon countries (CiviCRM's native land) a membership is regarded as a service. If you don't pay anymore, you won't get the service - that's it. In a lot of other countries the conception is different: it's more like a indeterminate binding contract.
Current Usage: 71
This extension integrates Twingle donation and membership forms with CiviCRM.
Current Usage: 123
This extension allows to build event registration forms with an editor. Those forms can be used in the Remote Events extension.
Current Usage: 5
This extension provides a lot of additional features to CiviCRM's events. In particular, you will be able to configure events in CiviCRM, display/use that information in other remote systems and submit registrations for those events back to CiviCRM.

The general idea is that your organization's staff can do all relevant event configurations in CiviCRM. CiviCRM will then make this information available via its REST API. The extension's API also has built in logic and actions to receive and update registrations.

Any external system can interact with the API and display event calendars, detailed event information, registration forms etc. (this could be a remote system or the CMS your CiviCRM runs on) and also submit information entered by your constituents back to CiviCRM.

All of this requires that you have or set up an external system to act as a frontend for your event listings, registration forms etc. In case you would like to build your system based on Drupal 8 you will most likely want to have a look and/or use the CiviRemote Drupal module which includes a lot of pre-built features (https://github.com/systopia/civiremote).

Note that this extension may be used alongside regular CiviCRM event registrations - you can choose whether you would like to use the remote features or not for each event.
Current Usage: 29
The focus of this extension is to facilitate the initial import and continuous update of the following data:

Committees - e.g. parliaments
Contacts, along with address, email, phone and website - e.g. members of parliament
Committee memberships
For that will find the importer in Contact menu with the "Import/Synchronise Committees" item. There you'll have to select:

an importer module suitable for your data source, e.g. the German Kürschner list.
a syncer module that defines the way the data is represented in your CiviCRM instance.
If the existing modules don't really work for you, you can contact us for new/adjusted modules at info@systopia.de.
Current Usage: 5
Control the profile visibility using CMS user roles.

This will control the accessibility of your profile based on your role, even if you give permissions to the CMS like profile create, 'profile listings', etc.

Each profile can have its own controls for accessibility.
Current Usage: 3