# Access from UX/UI

In **Data & Content Management**, **Access from UX/UI** describes how users interact with **images, files, and documents** through user interface components.

ONEWEB provides different capabilities for file and image handling through **Smart Forms** and **Pages**, depending on the design intent and usage context.

***

#### **Access from Smart Forms**

**App Designer** provides a built‑in **Upload Field** that allows users to upload and attach:

* Images
* Documents
* File attachments

to a **Smart Form**.

The Upload Field integrates directly with entity data, making it suitable for:

* Form‑based document uploads
* Attaching files to business records
* Managing file metadata alongside structured data

> For detailed information about the Upload Field, refer to:\
> **Upload Field**\
> <https://docs.oneweb.tech/oneweb/reference/app-designer-reference/entity/create-new-entity/fields/upload>

***

#### **Access from Pages**

**Page Designer** does not currently provide an out‑of‑box field for uploading documents directly on web pages.\
However, users can extend pages by implementing **custom JavaScript functions** to create and manage upload functionality when required.

This approach provides flexibility for advanced or custom UI designs, while keeping file handling logic explicit and controlled.

***

#### **Image Support in Page Designer**

Page Designer provides **native support for images**, including:

* **Static images**, embedded directly in the page design
* **Dynamic images**, loaded at runtime

Dynamic images can be retrieved from the database as **Base64‑encoded strings** using **Microflow**, and then displayed on the page.

This approach is commonly used for:

* User profile images
* Product images
* Dynamically generated visual content

***

#### **UX/UI‑Level Content Handling**

From a **Data & Content Management** perspective, file and image access from the UI layer ensures that:

* Content is accessed through defined UI components
* Data and file operations remain governed by application logic
* Direct file system access from the UI is avoided
* Different UI technologies support content access in appropriate ways

This separation helps maintain consistency between data handling and user interaction.

***

#### **Summary**

**Access from UX/UI** enables users to work with images, files, and documents through structured interface components.

In ONEWEB:

* **Smart Forms** provide built‑in support for file and document uploads
* **Pages** support images natively and allow custom file handling via JavaScript
* **Microflow** bridges UI components with backend storage and processing

This model ensures that file‑based content is accessed and managed in alignment with **Data & Content Management** principles.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onewebstack.com/building-apps/data-and-content-management/images-files-and-documents-access/access-from-ux-ui.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.