> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.11/development/flow-studio/applications/workflow/user-step/file-gallery.md).

# File gallery

With the file gallery is it possible to show files that the user can open and use on their device. The user can also add files to the gallery.

* **Target Variable**\
   The name of the new table variable in which the data stores.
* **Prompt**\
   The label displayed above the file gallery.
* **Source**\
   Choose a source table that contains files.
* **Uploads**\
   Choose upload type, singel or multiple upload.
  * **Single:** if the user only should upload one file.
  * **Multiple:** if the user should be able to upload more then one file (or zero files).
* **Allow File Endings**\
   Enter file endings for those type of files that should be allowed to add to the file gallery. For example; .doc, .xls
* **Target Image Size**\
   Use target image size to scale images or make it possible for the user to decide what size the image should be scaled to.
  * **Original:** All attached images will not be scaled.
  * **Small (25%):** All attached images will be scaled to the size of 25% of the original size.
  * **Medium (50%):** All attached images will be scaled to the size of 50% of the original size.
  * **Large (75%):** All attached images will be scaled to the size of 75% of the original size.
  * **User defined:** The user will be able to decide if the image should be scaled and what size it should be scaled to.

![A configuration of the file gallery in the designer, and how it looks in the web client](https://543770944-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-oh38gD3L5x-VPk2LG%2F-M-ohD4RuFrFBWS-IIj-%2Fhelp_root_applications_workflow_user_items_file_gallery.png?alt=media\&token=f103f5f0-ee85-4cf7-9d94-ba57dd8a7c42)


---

# 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://help.novacuraflow.com/6.11/development/flow-studio/applications/workflow/user-step/file-gallery.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.