---
title: "Reasons for the “You are not allowed to view this content.” message"
date: 2026-04-23
author: "GravityKit"
link: "https://www.gravitykit.com/docs/gravityview/common-problems/you-are-not-allowed-to-view-this-content/"
---

GravityView has many levels of security in place to make sure that your content is visible only when you want it to be. If you see the notification "You are not allowed to view this content.", there are multiple reasons why this might happen.

 To determine why you cannot access a View or entry, [enable logging](https://www.gravitykit.com/docs/gravityview/advanced/gravityview-logging-tools/) and reload the page. You should see a line in the log with a message similar to "Entry ID #{entry\_id} is not active" because the content is not accessible.

### Some possible reasons why the message is displayed:

- **Prevent Direct Access** setting is enabled for a View, and you're attempting to visit the View, not the post or a page where it is embedded. 
    1. Does the URL have "/view/" in it? if so, this counts as "direct access", and is likely the issue. **To fix:**
        1. Edit the View
        2. Scroll down to View Settings
        3. If checked, uncheck the setting "Prevent Direct Access", and save the View
        4. If unchecked: have you modified the code using the `gravityview\_direct\_access` filter? If not, "Direct Access" is not the reason you see the error.

- The entry you are attempting to access has been **put in the "trash"** in the Gravity Forms
- **Custom entry URL slugs** are enabled, and the URL "slug" and entry details don't match
- The View is configured only to show approved entries, and the **current entry is not approved**
- The current **search parameters** (or Advanced Filters settings) prevent the entry from being displayed
- You are attempting to access the REST API, and **REST API is not enabled** (or is disabled specifically) for the View
- **The View is privately published**, and you don't have access to reading it
- If you are running **the Avada theme** and have the  shortcode inside a "Code" field. Instead, place the shortcode in a Text field.
- **The entry's status is stored with non-standard capitalization.** The entry appears normally in the Multiple Entries list, the Gravity Forms admin, and exports, but opening or editing a single entry shows this message for everyone, including administrators. This happens when the entry's status is saved with different capitalization (for example `Active` instead of the standard lowercase `active`), which can happen when entries are imported. Lists keep working because the database compares status text case-insensitively, but the single-entry access check compares it more strictly. To fix it, normalize the stored status back to lowercase with the snippet below: run it once against the affected form (for example with `wp eval-file`), then remove it. The same capitalization can affect an entry's approval status (for example `Approved` instead of `approved`). A future GravityView release compares these values case-insensitively, so once you are on that version the error will not recur from capitalization alone, though normalizing the data is still recommended.

```
 'active' ) );

foreach ( $entries as $entry ) {
    GFAPI::update_entry_property( $entry['id'], 'status', 'active' );
}
```