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
Adds new settings to determine if a priceset field value should be displayed for one-time donations, recurring or both.
Administration interface for CiviCRM world regions, countries and states.
CiviCRM payment processor extension for eWAY which uses the latest eWAY Rapid API and ensures PCI DSS compliance. Requires eWAY account.
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.
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.
Creates a "confirm email address" field for profiles to ensure users enter the same email address twice, thus reducing typos.
Allows you to specify that when two people have a particular relationship and one makes a contribution, the other is automatically soft credited.
Allows the ability to set the button label on the Register and Confirm page of the event.
Create temporary groups with this extension. A temporary group will be automatically deleted after a given date.
Control who can see which contact notes. This extension will create a CMS permission for every additional Privacy level you create. Notes for which a user has no permission will be hidden.
This extensions will give admins a notification bubble if any of CiviCRM's database queries is taking a very long time, and gives you the options to stop (i.e. "kill") it. Use this with caution.
You can also set up a cron job to drop you an email in case such a long-running query is detected.
You can also set up a cron job to drop you an email in case such a long-running query is detected.
