Tutorials

How to Let Users See Their Own Form Submissions in WordPress

A member account page listing the logged-in user's own past form submissions

You run a member site, a course, an application process or a support desk. People log in, fill in a form, and a week later they email you asking what they sent. The obvious fix is a page where each logged-in user sees their own submissions. Nobody else’s. Just theirs.

Video: Let People See the Forms They Sent (Free + Pro)
Video: Let People See the Forms They Sent (Free + Pro) (0:58)

It sounds like a checkbox. In most form plugins it isn’t one. Two Forminator users asked for exactly this in the same week of November 2026. One wrote, in a thread titled “Show Users Submissions”: “is there a way to show each users submissions on a specific page?” Support replied: “Out of the box, it is not possible to show each user’s submissions on a specific page. However, it could be possible with custom coding.” The other thread got “I’m afraid this is not possible” and a pointer to a third-party table plugin.

So let’s go through why it’s awkward, what the big builders actually offer, how to do it yourself, and where it can go wrong.

One note first. This post is about each user seeing only their own entries. If you want entries on a public page (a directory, a testimonials wall, a table), that’s a different job and we covered it in how to display form entries on the front end.

Why this is harder than it looks

Two things have to be true before a “my submissions” page can work.

The entry has to be tied to a person. A form entry is just a row of field values. Unless something recorded who sent it, there’s nothing to filter on. There are two ways to make that link, and they behave very differently.

The page has to be strictly private. These entries often hold addresses, phone numbers, health details, application answers. Showing user A one of user B’s entries is a data leak, and under GDPR it’s a reportable one. So “mostly filtered” isn’t good enough.

Matching by user ID

When someone submits while logged in, most builders can save their WordPress user ID with the entry. Later you list entries where that ID equals the current user’s ID. This is the reliable method. The ID can’t be typed into a form field, it doesn’t change when someone edits their profile, and two people can’t share it.

The catch: it only covers entries sent while logged in. Anything submitted before the person had an account, or while logged out, has no user ID and won’t show up.

Matching by email

The other way is to compare the email field on the entry with the email on the user’s account. This picks up older entries, including ones sent before registration, which is often what people actually want.

But it needs care. Anyone can type any email address into a form, and on many sites anyone can register an account with any email address. If your site doesn’t confirm emails, a stranger could sign up as [email protected] and be shown everything Jane ever submitted. So an email match is only as trustworthy as your proof that the account owner really controls that address. Treat an unverified email as a hint, never as identity.

Our rule of thumb: use user ID for anything sensitive, and only use email matching where you understand how accounts get their email on your site.

What the big form builders offer

We only list what we could confirm in each vendor’s own docs or support replies in November 2026. If your builder isn’t here, check its docs before assuming either way.

Gravity Forms + GravityView

Gravity Forms doesn’t do this on its own. GravityView (from GravityKit, paid) does, with its Advanced Filter extension. In the View’s settings you turn on “Show only entries created by the currently logged-in user”, which adds a Created By filter. There’s also a variant that lets administrators still see everything. It filters by the user who created the entry, so it’s the user ID method, and it’s well thought out. It’s also two paid products before you’ve shown a single row.

Formidable Forms

Formidable has a hidden User ID field that records who submitted, and its docs describe creating a View that displays a logged-in user’s entries. Views aren’t in the free plugin, so this needs a paid plan.

WPForms

WPForms publishes a developer tutorial with a code snippet you add yourself. It registers a [wpforms_entries_table] shortcode, and user="current" limits the table to the logged-in user’s entries. Read the tutorial carefully, though: it says that if the visitor isn’t logged in, all entries for the form display. That’s the opposite of what you want on a private page, so you’d have to put the page behind a login yourself. It also needs a WPForms plan that stores entries, since WPForms Lite doesn’t. There’s a third-party add-on, Views for WPForms, that lists a “Display only User submitted Entries” option among its Pro features.

Forminator

As quoted above, support says it’s not possible out of the box, and points to custom code or a table plugin integration.

The DIY route: a small shortcode

If your builder stores entries in its own database table with a user ID column, you can write a tiny shortcode. Every builder names its tables and columns differently, so treat this as pseudocode. Swap in your builder’s real table, column names and API (and use its API if it has one, rather than raw SQL).

add_shortcode( 'my_submissions', function () {
    if ( ! is_user_logged_in() ) {
        return '<p>Please log in to see your submissions.</p>';
    }

    global $wpdb;
    $user_id = get_current_user_id(); // never from the URL or a form field
    $table   = $wpdb->prefix . 'your_form_entries'; // your builder's table

    $rows = $wpdb->get_results( $wpdb->prepare(
        "SELECT id, form_title, created_at FROM {$table}
         WHERE user_id = %d ORDER BY created_at DESC LIMIT 50",
        $user_id
    ) );

    if ( ! $rows ) {
        return '<p>You have no submissions yet.</p>';
    }

    $out = '<ul>';
    foreach ( $rows as $row ) {
        $out .= '<li>' . esc_html( $row->form_title ) . ', '
              . esc_html( $row->created_at ) . '</li>';
    }
    return $out . '</ul>';
} );

A few things in there matter more than they look:

  • The user ID comes from get_current_user_id(), full stop. Never accept it from ?user= in the URL, a hidden field or a cookie you set. If the ID can come from the request, anyone can change it and read someone else’s entries. This is the single most common way these pages leak.
  • Escape everything you print. Form entries are untrusted input. A submitted value containing a script tag will run in the browser if you echo it raw. esc_html() on every value, every time.
  • Allow-list the fields. Print the columns you chose, not “all fields”. Builders store internal values (IP addresses, admin notes, payment references) next to the answers.
  • Use $wpdb->prepare() for anything going into SQL, even an integer.
  • Exclude the page from caching. A page cache that saves one user’s version and serves it to the next is a leak that no code review will catch. Most cache plugins skip logged-in users by default; check that yours does.

Then test it the boring way. Make two test accounts, submit as each, and confirm each one sees only their own. Log out and confirm you see nothing. Try adding ?user_id=1 to the URL and confirm nothing changes.

If you’re collecting anything personal, it’s also worth reading our notes on GDPR and WordPress forms, because a self-service page is part of how you answer “what data do you hold on me?”.

Our two plugins, which cover different cases

Full disclosure: these are ours, and we’re mentioning two because they solve this for different situations.

If you’re building the form fresh, Trinity Forms has a [trinity_forms_my_submissions] shortcode in the free core. Put it on any page and the logged-in visitor sees their own past submissions to Trinity forms, matched by the user ID saved with each entry. It’s read-only and strictly scoped to that user. [trinity_forms_my_submissions form="12"] limits it to one form. Logged-out visitors see “Please log in to see your submissions.” It doesn’t show entries sent before the person had an account, for the reasons above. It’s a free download from our site.

If your forms are already built with another plugin (Forminator, Contact Form 7 and others that EntryVault captures), EntryVault Pro (paid) has an [entryvault_my_entries] shortcode. It matches by the account’s email, but only when the user’s account is older than the entry. An account created after the entry doesn’t count, because its email may never have been confirmed. Users see their entries with an Edit link. An edit changes EntryVault’s copy only; the original form plugin’s entry stays as it was, which is worth knowing if you work from that plugin’s own screen.

Neither one is the only answer. If you’re on Gravity Forms with a budget, GravityView is a good one.

Frequently asked questions

Can users see their own form submissions in WordPress?

Not by default. WordPress itself has no such page, and many form plugins don’t offer it either. You need a builder feature or add-on that filters entries by the logged-in user (GravityView for Gravity Forms, Formidable Views, a WPForms snippet), a free plugin that includes it, or a small custom shortcode that filters by the current user’s ID.

Is it safe to show form entries on the front end?

It can be, if the page is limited to logged-in users, the user ID comes only from get_current_user_id() and never from the URL, every value is escaped, only chosen fields are printed, and the page isn’t cached. Test with two accounts and while logged out before you trust it.

Can a user see entries they sent before they registered?

Only if you match by email, since those entries have no user ID. That’s safe only when you know the account really owns that email address. If anyone can register with any email and it isn’t confirmed, a stranger could see someone else’s entries, so many sites skip pre-registration entries on purpose.