JetEngine Dashboard Settings Overview

The JetEngine plugin is a set of flexible tools designed to build dynamic websites and avoid more manual work. The settings to be managed via the JetEngine Dashboard are located in the WordPress Dashboard > JetEngine > JetEngine tab.

Modules

In this tab, the Default and External modules are available. Each Module can be activated by the corresponding toggle. Each module in this settings menu tab represents a JetEngine feature you can add or remove from the website.

More information can be found by hitting the “info” icon next to the corresponding module.

After that, a pop-up will open with a YouTube video tutorial, a short description of the feature, and links to helpful documentation. Also, the pop-up will display which editor the module supports: Elementor, WordPress block editor (Gutenberg), Bricks, etc. Users can enable only the modules they need to avoid overloading websites.

Default modules

The following Default Modules are available: Maps Listings, Data Stores, REST API Listings, Forms (Legacy), Custom Content Type, Profile Builder, Grid Gallery, Slider Gallery, QR Code, Listing Grid injections, and Dynamic Visibility.

Each Default Module represents an inbuilt feature. After activating the required Default Module, the “Save” button should be pressed. Then, the page will be reloaded with some changes. The following scenarios happen after enabling some Modules:

1. If the Maps Listings, Data Stores, REST API Listings, and Forms (Legacy) modules are enabled, their settings tabs appear in the JetEngine dashboard page. Also, the Forms tab will appear in the WordPress Dashboard > JetEngine tab.

2. Once activated, Custom Content Type, Profile Builder, and Forms (Legacy) features appear on the WordPress Dashboard.

3. After enabling the Grid Gallery, Slider Gallery, or QR Code modules, the corresponding options will appear in the Dynamic Field widget/block/element settings. Enabling the Filter field output toggle adds these features to the Callback drop-down menu. For instance, the “QR Code,” “Images gallery slider,” and “Images gallery grid” options are added in the Dynamic Field widget in Elementor.

These options are also added into the Dynamic Field block settings.

As well, the same options are added to the Dynamic Field element in the Bricks editor.

4. Some modules, such as the Calendar, will appear as widgets in the Elementor widget menu.

As to the WordPress block editor (Gutenberg), the same Calendar module will appear as the Dynamic Calendar block.

As to the Bricks editor, the same Calendar module will appear as the Dynamic Calendar element.

5. After activating the Listing Grid injectionsoption, the “Inject alternative listing items” option appears in the General block of the Content settings tab of the Listing Grid widget in Elementor.

As to the WordPress block editor (Gutenberg), the same toggle will appear in the Listing Grid block settings.

As to the Bricks editor, the same toggle will appear in the Listing Grid element settings.

After activation, the Dynamic Visibility section will be added to the Advanced settings tab of all Elementor widgets and sections.

In the WordPress block editor (Gutenberg), one should click the “eye” icon. Then, the pop-up with the visibility condition settings will appear. Also, the Block Visibility section will be added to the block’s settings.

As in the WordPress block editor (Gutenberg) and Elementor, the shortcodes can be applied to set visibility conditions in Bricks.

Grid Gallery and Grid Slider for the Dynamic Field widget

These features are intended to display pictures added to the gallery-type meta field using the JetEngine or Advanced Custom Fields plugins on the website’s page as a grid.

The module’s functionality is implemented via the Dynamic Field widget/block/element. In particular, after activation of these Modules, one should navigate to a preferred editor, place the Dynamic Field widget/block/element; turn on the Filter field output toggle, and select the “Images gallery grid” or “Images gallery slider” Callback from the drop-down menu. To learn more, proceed to the How to Display Grid and Slider Galleries with Dynamic Field Widget/Block tutorial.

QR Code for Dynamic Field widget

This Module is intended to choose any text data placed in the meta field and display it as a QR code.

After activating this Module, one should create a Meta Field with a link, pull out the content using the Dynamic Field widget/block/element, enable the Filter field output toggle, and select the “QR Code” Callback from the drop-down menu. Watch the How to display QR codes with the Dynamic Field widget video tutorial to learn more.

Dynamic Calendar

The Dynamic Calendar module is intended to display dynamic content from the Custom Post Type (CPT) meta fields of different types (text, media, and more) in calendar listings and redirect users to the event’s page after clicking.

If enabled, this module activates the Dynamic Calendar widget/block/element in Elementor, the WordPress block editor (Gutenberg), and the Bricks theme.

The Dynamic Calendar module:

• displays listings according to the post’s publication/modification dates;
• selects a custom meta field containing dates;
• uses comments, terms, users, and Custom Content type (CCT) items;
• displays recurring events with the necessary frequency;
• displays posts from two or more different post types;
• hides past events and starts from a month the user wants;
• applies visibility conditions to data.

This feature is described in the How to Create a Dynamic Calendar tutorial.

Forms (Legacy)

This is a legacy form builder functionality that will be updated only for critical bug fixes. The JetFormBuilder plugin provides the latest updates, including new form features. After activation, the Forms tab will be added to the JetEngine submenu. In this submenu, one can create new forms and edit existing ones. This module also adds a new widget/block/element to the corresponding editor to display previously created forms. More details on customizing the form layouts are provided in the How to Create a Form Layout tutorial.

Listing Grid injections

This option allows you to use different Listing Templates within one Listing Grid widget/block/element. More information about this widget can be found in the How to Use Alternative Listing Template Functionality in Listing Grid tutorial.

Profile Builder

This module is intended to create a personal user’s account page on your website or users’ public profiles similar to social media profiles. After activation, the Profile Builder tab will be added to the JetEngine submenu. This feature is explained in the User Profile Builder Overview tutorial.

Maps Listings

This widget displays any Custom Post Type items as pop-up markers on a map.

To apply this functionality, an API key should be obtained and pasted into a corresponding Maps Settings tab field, as described in the Choosing Different Front-end and Geocoding Map Providers for Map Listings tutorial.

After activation, the Maps Settings tab will be added to the JetEngine Settings dashboard. Besides that, the Map Listing widget/block/element will appear in the Elementor widget menu, WordPress block editor (Gutenberg), and Bricks editor, respectively.

Dynamic Visibility for Widgets and Sections

This module is intended to set the visibility of widgets/blocks/elements, columns, and sections depending on the meta field values, user roles, and other conditions.

After activation, the Dynamic Visibility section will be added to the Advanced settings tab of all Elementor widgets and sections, and the Block Visibility section will be added to the block’s settings in the WordPress block editor (Gutenberg).

More information about managing visibility conditions for meta fields, posts, listings, and relations is available in the Dynamic Visibility Module Overview.

Data Stores

This module adds wishlist, favorites, likes, bookmarks, and other functionality to your website.

After activation, the Data Stores tab will be added to the JetEngine dashboard. Besides that, in the Source drop-down menu of the Content settings tab of the Dynamic Link widget/block/element, an “Add to store” option will appear.

The information on creating pages for users and configuring the needed settings can be found in the Data Stores Module Overview.

Custom Content Type

This module is intended to create custom tables in the website database, fill them with data manually or using front-end forms, and then export that information or show it on the website pages using the Listing Grid widget/block/element. After activation, the Custom Content Types tab will be added to the JetEngine submenu. 

More about the CCT functionality for better site organization is presented in the How to Create a Custom Content Type tutorial.

REST API Listings

This module is intended to display information from a third-party REST API using the Listing Grid widget/ block/element.

After activation, the REST API Endpoints tab will be added to the JetEngine Settings dashboard. Besides that, a “REST API Endpoint” option will be available in the Listing creation window. Also, this module adds the “REST API Request” notification to the JetEngine and JetFormBuilder forms.

FullWidth WordPress block editor (Gutenberg)

After activation of the Module, it makes blocks in the Gutenberg editor area full-width, regardless of the theme styles. For example, that’s how the Calendar block looks with the usual width.

And that’s how the block looks when the FullWidth WordPress block editor (Gutenberg) module is enabled.

External Modules

The following External Modules are available:: Dynamic Tables Builder, Custom Visibility Conditions, Dynamic Charts Builder, Dynamic Tables Builder, Get Attachment File Link by ID, Layout Switcher, Trim String Callback, and Post Expiration Period Module.

The External Modules, unlike the Default Modules, are installed as separate plugins.

Also, after installation and a page reload, the Dynamic Charts and Dynamic Tables builders appear in the WordPress Dashboard > JetEngine tab.

The Attachment file link by ID and Trim string callback modules will be displayed in the Dynamic Field widget/block/element after installation. In this case, the Filter field output toggle should be enabled to observe these features in the Callback drop-down menu in Elementor.

These options are also added into the Dynamic Field block settings.

As in the WordPress block editor (Gutenberg) and Elementor, the same options will be added to the Bricks Builder elements.

The Post expiration period, Custom visibility conditions, and other features are free add-ons one can download from the free DevTools kit page.

Dynamic Tables Builder

The add-on is intended to create different tables based on dynamic data, be it tables of posts, WooCommerce products, users, terms, comments, etc. Users can also build tables based on CCT data or tables with data queried directly from the SQL database. In the table cells, one can either display the data pulled from the database or the Listing templates built based on this data.

Also, the Dynamic Tables module is compatible with JetSmartFilters, so the selected data can be filtered or sorted as you like.

After enabling the Dynamic Tables module, it appears as a submenu in the WordPress Dashboard, is installed as a separate plugin, and is available as a widget and block.

More information about this feature can be found in the Tables Builder Overview.

Dynamic Charts Builder

This module is designed to display dynamic data in a graph format. After enabling the Dynamic Charts module, it’s shown as the submenu in the WordPress Dashboard, installed as a separate plugin, and available as a widget and block in the Elementor and Gutenberg editors, respectively.

More about this module is explained in the Dynamic Charts Builder Overview.

Attachment file link by ID

This one allows you to display download links for .pdf, .zip, and other file formats using the Dynamic Field widget/block/element and use it to output such links to the archive and single page templates. This module adds a new callback to the Dynamic Field widget/block/element and is installed as a separate plugin.

Custom visibility conditions

The Custom Visibility Conditions add-on is part of the Dynamic Visibility module, so it should also be enabled. To learn more about this feature, proceed to the Dynamic Visibility Module Options Overview.

The add-on adds the “Is post by current user” condition (makes sections/columns/widgets visible/invisible to the post’s author) and the “Post Status is” condition (shows/hides the sections/columns/widgets depending on the post status) custom visibility conditions to the corresponding widgets/blocks. In particular, it adds these options to the Dynamic Visibility tab in the Advanced section of any widget in the Elementor editor.

In the WordPress block editor (Gutenberg), hitting the “eye” icon displays these options in the Condition drop-down.

This tab has such settings:

• Optimized DOM 一 a toggle that, if enabled, removes some additional HTML wrappers from the JetEngine elements. The number of removed wrappers depends on each specific element;

• Elementor Views  一 a toggle that, if disabled, turns off widgets and Dynamic Tags for the Elementor editor;
• Blocks Views 一 a toggle that, if disabled, turns off blocks and Dynamic Tags for the WordPress block editor (Gutenberg);
• Bricks Views 一 a toggle that, if disabled, turns off elements for the Bricks editor;
• Timber/Twig Views 一 a toggle that, if enabled, suggests the Timber plugin be installed. Then, listing items in the Timber/Twig editor can be created.

After changing the settings, click the “Save tweaks config“ button.

Skins Manager

The Skins Manager settings menu tab allows import or export post types, taxonomies, listing items, queries, CCTs, relations, meta boxes, etc., from one website to another. To learn how to work with this feature, proceed to the How to Import and Export Custom Post Types, Terms, and Meta Fields tutorial. The settings include the Import Skin, Export Skin, and Presets tabs.

In the Import Skin tab, the needed dynamic content, such as a JSON file, can be uploaded.

In the Export Skin tab, any JetEngine content can be selected and imported to another website to avoid creating the same elements several times.

The Presets tab is only available if the Profile Builder and Forms (Legacy) default modules are activated. There are the following settings:

The Presets tab is available only when the Profile Builder and Forms (Legacy) default modules are activated.

• User profile with editable content 一 imports an Account page with three subpages: “Main” with the Listing Grid that displays posts created by the current user, “Edit post” with the “Edit post” form, and “New post” with the “New post” form;
• Editable user settings page for user profile 一 imports the “User Settings” subpage with the “Edit User” form.

More details are described in the How to Apply a Preset for User Account Page tutorial.

Shortcode Generator

The Shortcode Generator tab is intended to generate JetEngine-related values as shortcodes (e.g., create QR code shortcodes using the QR Codes for Dynamic Field widget Module) and to create conditional shortcodes that can be used in text editors or builders like Bricks.

The Dynamic Conditions can now be embedded directly into content or used to control the visibility of elements in Bricks. If the Dynamic Visibility module is activated, the Shortcode drop-down list will include the “JetEngine Data (default)” and “JetEngine Condition” options. More information is provided in the How to Operate with Dynamic Visibility via Shortcodes tutorial.

JetEngine Data

JetEngine Data (default) 一 an option that, if selected, displays JetEngine field data with a shortcode that fetches and shows custom field information dynamically. The following settings are available:

• Source 一 a drop-down list that allows selecting the shortcode’s source (e.g., the “Post/Term/User/Object Data,” “Meta Data,” “Query Variable,” “Options.” In turn, if set, each of the options activates the corresponding field(s), allowing the specification of the needed source;
  • Post/Term/User/Object Data — an option that pulls the content from the default meta fields of the post, term, user, or object. The field can be specified in the Object Field select or defined by typing in the Custom Object Field / Meta field / Repeater key field;
  • Meta Data — an option that takes the content from one of the meta fields created by the JetEngine plugin’s functionality; in particular, a specific field in the Meta Field drop-down menu can be chosen or defined by typing in the Custom Object Field / Meta field / Repeater key field;
  • Query Variable — an option that activates the Variable Name text field, which allows posts to be displayed on the Search Results page. For example, if the letter “s” is added to the Variable Name field and if someone uses the search feature to search for “flowers,” the shortcode will return posts of the specified post type that have a match in title, content, or excerpt. Read the AJAX Search widget or block tutorial to learn how to use such a shortcode;
  • Options — an option that activates the Options drop-down list for selecting a meta field created for the Options Page. 
• Hide if Empty 一 a toggle that activates the toggle to hide the value if it’s empty. The toggle is set to deactivated by default and enables the Fallback Value field that allows inserting an alternative text in case the info is missing;
• Filter Field Output 一 a toggle that, if selected, applies callbacks to the generated shortcode you generate and activates the Applied Callbacks section to choose the needed callback in the Callback drop-down list. Pressing the “Add new item” button in the Applied Callbacks section allows adjusting the callback. Learn more about different callbacks from the Dynamic Field Widget Overview;
• Customize field output 一 a toggle that, if selected, activates the Field format field that allows adding some text before and after the value pulled from the meta field; %s stands for the value that is pulled; usage of the %1$s inserts the same value multiple times in the Field format field;
• Context 一 a drop-down list that helps specify the field’s source and collaborates with the Source option. According to the selected settings, there can be such options:
  • Default Object — an option that shows data for the current page or listing template;
  • Current User (global) — an option that shows data according to the user for whom the page was created;
  • Current User (for current scope) — an option that shows data according to the user who is currently proceeding. For example, a user listing shows the user’s posts when clicked. In this case, if you choose the Current User (for current scope) context, it will display the meta field value of the user you have just clicked on, not the logged-in user;
  • Queried User — an option that shows data for the currently logged-in user or the user mentioned in the URL (the user ID is in the URL);
  • Current Post Author — an option that shows the meta field value of the user who is the author of the currently opened post;
  • Default WordPress Object (for current page) — an option that always shows the data of the current global object for the current page defined by WordPress. For instance, on a single page/single post, it will always be the current post, even if you go to the listing added to this page;
  • Current CCT item author — an option that shows the data in the meta field of the user who is the author of the currently opened CCT item. It can be used in the Listing Template for CCT to show information about the author of the CCT item. To learn more about CCT, proceed to the How to Create a Custom Content Type tutorial;
  • Related Items From… — an option that shows the data for the created relation. To learn more, navigate to the Relations Dynamic Output tutorial.

After the required options are set, the shortcode will be generated and displayed in the text field at the bottom of the page.

 JetEngine Condition

JetEngine Condition 一 an option that, if selected, generates a new shortcode with the Dynamic Visibility conditions. The following settings are available:

• Tag Enclosing Type 一 a drop-down list that allows to selecting the type of the shortcode’s tag:
  • Enclosing (e.g. [shortcode attrs]content… [/shortcode])” 一 an option that creates enclosing shortcodes that return the content that is inside the shortcode if the condition is met. This type is convenient for use in text editors or wherever you need to control the output of content. If selected, the option activates the Visibility Condition Type drop-down list that specifies how the condition result will be processed: “Show element if condition met” or “Hide element if condition met”;
  • Selfclosing (e.g. [shortcode attrs]) 一 an option that returns “true” or “false” depending on the condition. This type of shortcode is perfect for integration with the Bricks theme, where it can be used as a dynamic visibility condition;
• Condition 一 a drop-down list that allows selecting the condition that should be met. The conditions are divided into the “General,” “JetEngine specific,” “User,” “Date&Time,” “Listing” groups. Once selected, the options from this drop-down list enable other fields. For example, the “Greater than” option activates the Source field to select the source for comparison (e.g., a meta field).

After setting the needed options, the shortcode will be generated and displayed in the text field at the bottom of the page.

After completing, the generated shortcode can be copied and inserted into the Shortcode Gutenberg block or Bricks’ Element Condition field on a page. Also, the shortcode can be entered into the Text meta field.

Macros Generator

The settings in this tab are intended to generate macros for use where supported. There are such settings:

• Macros 一 a drop-down list that allows selecting a needed macro. Information about all available macros can be found in the Macros Guide;
• Context 一 a drop-down list that allows specifying a source. According to the specified settings, there can be such options:
  • Default Object 一 an option that shows data for the current page or listing template;
  • Current User (global) 一 an option that shows data according to the user for whom the page was created;
  • Current User (for current scope) 一 an option that shows data according to the user who is currently proceeding. For example, there is a listing of users that shows the posts written by the user after clicking on them. In this case, if the Current User (for current scope) option is set, the listing will display the meta field value of the user you have just clicked on, not the logged-in user;
  • Queried User 一 an option that shows data for the currently logged-in user or the user mentioned in the URL (the user ID is in the URL);
  • Current Post Author 一 an option that shows the meta field value of the user who is the author of the currently opened post;
  • Default WordPress Object (for current page) 一 an option that shows the data of a current global object for the current page defined by WordPress. For instance, on a single page/single post, it will always be the current post, even if you go to the listing added to this page;
  • Current CCT item author 一 an option that shows the data in the meta field of the user who is the author of the currently opened CCT item. It can be used in the Listing Template for CCT to show information about the author of the CCT item. To learn more about CCT, proceed to the How to Create a Custom Content Type tutorial;
  • Related Items From… 一 an option that shows the data for the created relation. To learn more, navigate to the Relations Dynamic Output tutorial.
• Fallback 一 a field that allows you to define what text to show users if the value is empty.

After setting the needed options, the shortcode will be generated and displayed in the text field at the bottom of the page.

Maps Settings

The information on the map providers and other additional settings is presented in the Choosing Different Front-end and Geocoding Map Providers for Map Listings tutorial.

Glossaries

These settings are explained in the Glossaries Functionality Overview.

Data Stores

The first step of the How to Create Favorites Page Using Data Stores Module tutorial is dedicated to the Data Stores tab settings.

REST API Endpoints

The REST API functionality is described in the How to Display Custom Content Type Items Using REST API tutorial.

Forms Settings (Legacy)

The settings allow entering the reCAPTCHA, ActiveCampaign, Mailchimp, and GetResponse keys here. Afterward, they will be stored on the website, and you won’t need to enter them whenever you set up a new form.

Advanced

The Advanced tab in JetEngine provides developer-oriented settings that control how metadata is processed, how the Query Editor behaves, and how JetEngine interfaces appear. These options are useful for troubleshooting, performance adjustments, and ensuring consistent behavior in custom setups. It contains such options:

• Disable legacy User Meta processing — a toggle, when enabled, forces JetEngine to always retrieve the meta directly from the object by context (more predictable for developers working with custom meta structures). If disabled — when the meta key matches a JetEngine user meta field, data is automatically pulled from the current user or listing object;
• Disable Frontend Query Editor — prevents users or editors from modifying JetEngine-powered queries on the front end. Useful for locking layouts or improving security;
• Force LTR on JetEngine pages — forces JetEngine interfaces to use a left-to-right layout, even if the site’s language is RTL (right-to-left). Useful when working in RTL languages, but preferring a standard UI flow for better consistency with documentation or code snippets. Changing this setting reloads the page.

MCP Server

The Model Context Protocol (MCP) Server in JetEngine unlocks seamless communication between the WordPress website and external AI tools. Here, one can activate the server, view the MCP endpoint URL, and check the list of available tools that external apps can call — including operations for custom post types, listings, queries, taxonomies, meta boxes, glossaries, and other JetEngine data-management actions.

All tools — including global ones — fall into two categories:

• Tools — perform direct actions and can change the state of the website. Examples: creating posts, updating meta fields, registering taxonomies.
• Resources — provide data only and do not modify the website. They are used to supply context, configuration details, or metadata for other operations.

Such tools are available:

• Add Custom Content Type — creates a new Custom Content Type (CCT). The convenience is that there is no need to enable a module separately — everything will be done automatically in the background;
• Get JetEngine Configuration — retrieves the current JetEngine setup overview, including all registered post types (CPTs), CCTs, taxonomies, meta boxes, options pages, queries, relations, REST API endpoints, and glossaries in JSON format;
• Get Website Config — retrieves the current configuration of the entire site. While less detailed than the Get JetEngine Configuration option, it provides information about registered post types, taxonomies, and installed plugins in JSON format;
• Get JetEngine Macros — provides a list of macros available for invocation on this site, along with their arguments and usage examples for AI-assisted tooling. Together with the two previous resources, it helps supply the AI agent with accurate site context so it can correctly invoke other tools;
• Add Glossary — creates a glossary with manually provided options;
• Manage JetEngine Modules — lists active JetEngine modules and allows enabling or disabling modules upon request;
• Add Listing Grid Item — creates a listing item based on an existing query (if information about the query is in the agent’s context) or using legacy parameters (for a specific CPT, taxonomy, etc.);
• Add Custom Post Type — creates a CPT with the necessary meta fields. Provide the CPT name in general_settings.name; if general_settings.slug is omitted, it will be generated automatically from the name;
• Add Meta Box — adds a meta box with a required set of meta fields for a CPT, taxonomy, or user. Provide general_settings.name and describe the fields in meta_fields. The tool automatically enables the necessary visibility conditions when you supply its configuration;
• Add Taxonomy — creates a taxonomy with the necessary meta fields. Provide the taxonomy name inside general_settings.name and assign it to one or more post types via general_settings.object_type;
• Add Query — creates a new query to the Query Builder. The request must always include the query_args object when calling this tool. Requests without query_args are invalid and will be rejected. For query_type: “sql”, query_args must contain a non-empty sql string. For other types, query_args must contain the appropriate query arguments (WP_Query-style for posts, terms, users, etc.).

Valid examples: 

• SQL: {“name”:”Recent orders”,”query_type”:”sql”,”query_args”:{“sql”:”SELECT * FROM wp_posts WHERE post_type=’shop_order’ LIMIT 10″}}; 
• Posts: {“name”:”Latest posts”,”query_type”:”posts”,”query_args”:{“post_type”:”post”,”posts_per_page”:5}} 

Invalid example (will be rejected):

{“name”:”Latest posts”,”query_type”:”posts”} — missing query_args. 

Additionally, macros from the conversation context can be used for contextual params (IDs, user, dates) to make queries dynamic.

More details can be found in the How to Use MСP Server with VS Code + Copilot tutorial. Also, the Command Center Overview can be checked, which describes AI commands for advanced WordPress automation.

That’s all. Now you know all about the WordPress JetEngine Dashboard settings.