> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-forms/editor/member-form-submissions.md).

# Member Form Submissions

Review a member's form activity from the Members section using the Forms tab on the member editor.

{% hint style="info" %}
This feature is available from Umbraco Forms 17.5 and 18.1.
{% endhint %}

The member editor in the **Members** section includes a **Forms** tab. The tab lists the forms a member has submitted and lets you open their entries without leaving the Members section.

## The Forms tab

Open a member in the **Members** section. The **Forms** tab appears alongside the member's other tabs.

![The Forms tab on a member, showing the empty state for a member with no entries](https://3134593492-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xCfyNy4WLrfX8D6oTtt%2Fuploads%2Fgit-blob-ae36e6ab5f18695fe2d5ad29b3b244dc8526c300%2Fmember-forms-tab.png?alt=media)

The tab is hidden in two cases:

* The member is new and has not been saved. A new member has no entries.
* You do not have access to the **Forms** section.

## Listing forms

The tab lists every form the member has at least one entry for, with the number of entries per form.

![The Forms tab listing a form the member has submitted, with the entry count](https://3134593492-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xCfyNy4WLrfX8D6oTtt%2Fuploads%2Fgit-blob-f1b03385fd58e54bb6aa74d2c55d065b923d2a52%2Fmember-forms-tab-list.png?alt=media)

Forms the member has not submitted are not listed. Forms you do not have permission to access are not listed either.

When the member has no entries for any form, the tab shows a standard empty state.

## Navigating to entries

From the list you can drill into the member's activity:

* Select a **form name** to open the form's details in the **Forms** section.
* Select the **entry count**, or **View entries for this form**, to open the member's entries for that form.
* Select an **entry** to open the entry details.

The entries and entry details reuse the same views as [Viewing And Exporting Entries](https://github.com/umbraco/UmbracoDocs/tree/main/18/umbraco-forms/viewing-and-exporting-entries.md), filtered to the current member.

## Permissions

The Forms tab respects Forms permissions.

* The tab is hidden when you do not have access to the **Forms** section.
* Forms you cannot access are filtered out of the list on the server, so they are never shown or navigable.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-forms/editor/member-form-submissions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.