Title: Parse.ly Content Intelligence
Author: joshua
Published: August 1, 2022
Last modified: November 25, 2025

---

 1. [User handbook](https://docs.parse.ly/user-handbook/)
 2. [Tools and features](https://docs.parse.ly/user-handbook/tools-features/)
 3. Parse.ly Content Intelligence

#  Parse.ly Content Intelligence

Parse.ly Content Intelligence (PCI) is a set of content insights available to WordPress
users of the Parse.ly plugin ([wp-parsely](https://wordpress.org/plugins/wp-parsely/)).
When viewing the WordPress Admin dashboard and editing or authoring a post in WordPress,
users rely on PCI for curated analytics, content insights, and information otherwise
only available within the [Parse.ly Dashboard](https://docs.parse.ly/dashboard/).

**Note**

The PCI experience lives within WordPress. It’s powered by Parse.ly but does not
grant access to the complete Dashboard, [API](https://docs.parse.ly/api/), or [Data Pipeline](https://docs.parse.ly/data-pipeline/).

Learn more about [how to install the Parse.ly WordPress plugin](https://docs.parse.ly/wordpress-plugin-setup/)
and [how to put PCI to work with WordPress](https://docs.parse.ly/tools-features/content-intelligence/how-to/).

**Pro Tip**

Wondering if PCI is right for your team? Contact your Relationship Manager for more
information and to enable a PCI trial on your site.

## Prerequisites

General requirements to use PCI include:

 * Version 3.6 or greater of the [wp-parsely](https://wordpress.org/plugins/wp-parsely/)
   WordPress plugin (see [release notes](https://github.com/Parsely/wp-parsely/releases)
   for the latest version available).
 * The [WordPress block editor](https://wordpress.org/documentation/article/wordpress-block-editor/)
   to edit and publish content.

PCI’s AI features are available only to [WordPress VIP CMS](https://www.parse.ly/wordpress-vip-parsely/)
customers or customers of both WordPress VIP CMS and [Parse.ly](https://www.parse.ly/).

 * AI features require written consent to opt in — [submit your request here](https://wpvip.com/content-helper/#content-helper-form).

WordPress VIP CMS customers must first [activate Parse.ly as an integration](https://docs.wpvip.com/parse-ly/enabling-and-disabling/)
to use PCI with production sites.

Parse.ly-only customers first need to purchase the [Parse.ly API](https://docs.parse.ly/api/)
to enable PCI. Then, find the API secret under the [API Settings](https://docs.parse.ly/account-management/api-settings/)
page of the Parse.ly Dashboard’s [account menu](https://docs.parse.ly/account-management/).
Enter the API secret into the [wp-parsely plugin’s settings](https://docs.parse.ly/wordpress-plugin-setup/#h-basic-settings)
in the WP Admin dashboard.

**Note**

Parse.ly-only customers who would like to purchase the API can contact their Relationship
Manager for more details and assistance.

## PCI settings

Customize PCI, including which user roles can access AI-powered features, from the
Parse.ly Settings page in the WP Admin dashboard.

![Access Parse.ly settings from the WordPress Admin dashboard.](https://docs.parse.
ly/wp-content/uploads/sites/5/2025/07/Parsely-plugin-settings.png)

Access Parse.ly settings from the WP Admin dashboard.

 1. Log into your site’s WP Admin dashboard.
 2. Click `Parse.ly` in the left navigation menu, then `Settings`.
 3. Click the Content Intelligence tab to access all PCI-specific settings.

![PCI settings.](https://docs.parse.ly/wp-content/uploads/sites/5/2025/07/PCI-settings.
png)

PCI settings.

**Note**

Settings for PCI’s AI features require version 3.16.0 of the wp-parsely WordPress
plugin or greater.

## Permissions Filter

The `wp_parsely_current_user_can_use_pch_feature` filter provides a way to customize
which users can access specific Content Intelligence features. This filter runs 
before the default permission checks and allows developers to override the standard
role-based access control with custom logic. Implementing this filter enables granular
permission rules based on user attributes, post properties, or any other contextual
information available in WordPress. The filter receives information about the feature
being accessed, the current user, and the post being edited (if applicable), enabling
sophisticated access control rules tailored to the organization’s specific needs.

### Parameters󠀁[](https://gist.github.com/vaurdan/8e1c8bb3777ba125148580a62a871ba0#parameters)󠁿

| Parameter | Type | Description | 
| `$can_use_feature` | `?bool` | Whether the current user can use the feature. Default is `null`, which means the filter is not being used. | 
| `$feature_name` | `string` | The name of the feature being checked (e.g., ‘smart_linking’, ‘title_suggestions’, ‘excerpt_suggestions’, ‘traffic_boost’). | 
| `$current_user` | `WP_User` | The current WordPress user object. | 
| `$post_id` | `int|false` | The post ID if checking for a specific post, or `false` otherwise. |

### Return Value󠀁[](https://gist.github.com/vaurdan/8e1c8bb3777ba125148580a62a871ba0#return-value)󠁿

Return `true` to grant access to the feature, `false` to deny access, or `null` 
to fall back to the default permission logic.

### Example Usage

    ```lang-php
    <?php
    /**
     * Example of using the wp_parsely_current_user_can_use_pch_feature filter
     */

    /**
     * Custom function to control access to Parse.ly Content Intelligence features.
     * 
     * This example allows authors to use all features except the Excerpt Generator,
     * which is restricted to editors and administrators only.
     */
    function custom_parsely_permissions( $can_use_feature, $feature_name, $current_user ) {
        // For the Excerpt Generator feature
        if ( 'excerpt_generator' === $feature_name ) {
            // Only allow editors and administrators
            if ( in_array( 'editor', $current_user->roles, true ) || 
                 in_array( 'administrator', $current_user->roles, true ) ) {
                return true;
            } else {
                return false;
            }
        }

        // For all other features, use the default permission logic
        return $can_use_feature;
    }

    // Add the filter with 10 priority and 3 parameters
    add_filter( 'wp_parsely_current_user_can_use_pch_feature', 'custom_parsely_permissions', 10, 3 ); 
    ```

## Disable PCI

By default, all available PCI features are enabled. Technical teams can disable 
PCI — either entirely or specific features — using the following filters:

    ```lang-php
    // Disable PCI entirely.
    add_filter( 'wp_parsely_enable_content_helper', '__return_false' );

    // Disable the PCI WP Admin dashboard widget.
    add_filter( 'wp_parsely_enable_content_helper_dashboard_widget', '__return_false' );

    // Disable the PCI Parse.ly Stats column.
    add_filter( 'wp_parsely_enable_content_helper_stats_column', '__return_false' );

    // Disable the PCI block editor sidebar.
    add_filter( 'wp_parsely_enable_content_helper_editor_sidebar', '__return_false' );

    // The above filters can be used in conjunction. Here's an example of 
    // disabling all PCI features except for the WP Admin dashboard widget.
    add_filter( 'wp_parsely_enable_content_helper', '__return_false' );
    add_filter( 'wp_parsely_enable_content_helper_dashboard_widget', '__return_true' );
    ```

Last updated: November 25, 2025