List of Strapi plugins

🚧 This section of the user guide is a work in progress. Stay tuned!

No matter if they are installed by default, or additional, Strapi plugins allow to expand your application by adding more options and possibilities. All options are documented in their right places throughout the user guide. However, you can use the following documentation as a reference guide to know which Strapi plugins are available, how they work and which options they add to your Strapi application.

Default plugins

Internationalization plugin

The Internationalization plugin is installed by default on all Strapi applications running on version 3.6.0 or higher. For lower versions, a migration is needed (see Update Strapi version (opens new window) in the developer documentation), as well as a manual installation of the plugin (see Installing plugins via the Marketplace).

This plugin allows to manage content in different languages, called "locales". With the Internationalization plugin, it is possible to:

• define what locales should be available in the Strapi application,
• define which content-types and fields can be translated in different locales, or should only be available in the default locale,
• translate content and manage it each locale at a time.

The Internationalization plugin impacts several parts of the admin panel. The table below lists all the additional options and settings that are added to a Strapi application once the plugin has been installed.

Section impacted	Options and settings
Settings	Addition of a new "Internationalization" setting sub-section, from which to add, edit or delete locales available for the application (see Configuring Internationalization locales). 👉 Path reminder: General > Settings > Global Settings > Internationalization Addition of new permissions for administator roles: access to content-types, as well as possible actions on the content-types, can be defined depending on the locale (see Configuring role's permissions). 👉 Path reminder: General > Settings > Administration panel
Content-Types Builder	Addition of a new setting at content-type level, to allow or not localisation/translation of the content-type (see Creating a new content-type). Addition of a new setting at field level, to allow or not localisation/translation of the content-type (see Configuring fields for content types).
Content Manager	Addition of new Locales filter in collection types list view, to manage entries per locale (see Introduction to the Content Manager). Addition of new options in content-types edit view, to translate content and manage it per locale (see Translating content).

Users & Permissions plugin

The Users & Permissions plugin is installed by default on all Strapi applications.

This plugin allows to manage end-users, who consume the content that is created and managed with a Strapi application and displayed on a front-end application (e.g. website, mobile application, connected device etc.). With the Users & Permissions plugin, it is possible to:

• manage end-users accounts, based on a "User" collection type available through the plugin,
• define the available end-users roles and their related permissions,
• manage available providers to enable end-users to login through third-party providers,
• configure available email templates aimed at the end-users (e.g. password reset, email address confirmation).

The Users & Permissions plugin impacts several parts of the admin panel. The table below lists all the additional options and settings that are added to a Strapi application once the plugin has been installed.

Section impacted	Options and settings
Settings	Addition of a "Users & Permissions plugin" setting section, which contains 4 sub-sections: Roles (see Configuring end-users roles), Providers, Email Templates, and Advanced Settings (see Configuring Users & Permissions plugin). 👉 Path reminder: General > Settings > Users & Permissions plugin
Content-Types Builder	Creation of 3 default collection types: "User", "Role" and "Permission". They respectively allow to manage the end-users, the end-users roles and their permissions. These collection types cannot be deleted and their composing fields cannot be edited, but addition of new fields is possible. Out of the 3, only the "User" collection type is then available via the Content Manager.
Content Manager	Addition of the default "User" collection type that allows to manage end-user accounts (see Managing end-users accounts). By default, the following fields are available: Username, Email, Password, as well as Confirmed and Blocked as boolean fields. The "User" collection type has a relation established with the "Role" collection type. All end-user accounts must indeed be attributed a role: by default, the end-user is attributed the end-user role set as default, but that role can be changed via the end-users entries directly in the Content Manager.