---
title: Example - WebDAV browse mode editing
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

The following example demonstrates how website file management using WebDAV Browse mode actually works. The sample Intranet Portal website is used for the purpose of the example.

> **Note:** Before trying this example on your machine, please make sure that your system meets all [requirements](https://docs.kentico.com/k82/managing-website-content/configuring-the-environment-for-content-editors/configuring-webdav/webdav-requirements-and-limitations.md), that you have WebDAV [settings](https://docs.kentico.com/k82/managing-website-content/configuring-the-environment-for-content-editors/configuring-webdav/adjusting-webdav-settings.md) adjusted properly and that you have [mapped a WebDAV network drive](https://docs.kentico.com/k82/managing-website-content/configuring-the-environment-for-content-editors/configuring-webdav/webdav-browse-mode/mapping-a-webdav-network-drive.md).

## Editing a CMS.File page type file

1. Open the **Pages** application and expand the **Company/Internal Policy** node in the content tree.
2. Select the **Dress Code** page.
3. Switch to the **Form** tab.

   - As Dress Code is a _CMS.File_ page, you can see that it has a **Dress-Code.docx** file uploaded in its File field.

![A CMS.File page](https://docs.kentico.com/docsassets/k82/example-webdav-browse-mode-editing/editing_file_form_tab.png "A CMS.File page")

Let's take a look at the page on our network drive.

1. Open **Windows Explorer** or any other file manager that you prefer.
2. Open the WebDAV network drive and browse to _content\\\Company\Internal-Policy_.

   - The **Dress-Code** page is represented twice in the folder —  first as the **Dress-Code** folder and second as the **Dress-Code.docx** file. The folder represents the page in the content tree and would contain unsorted attachments if the page had any. The file represents the **Dress-Code.docx** file uploaded in the page's File field.
3. Open the **Dress-Code.docx** file to see how it can be edited.

   - The **Dress-Code.docx** file gets opened in a client application (typically in Microsoft Office Word).
4. Edit the opened file and save your changes using the **Save** button.
5. Now open the file from Kentico.

You should see that the opened file contains the modifications that you made to it.

## Updating a file in a File field (attachment)

Next, we will try out how the file uploaded in File fields can be replaced with other files.

1. In the **Pages** application choose the **News/Record Sales in Q3** page in the content tree.
2. Switch to the **Form** tab.

   - You can see a file uploaded in the **Teaser** File field. 

     ![File attached to a page](https://docs.kentico.com/docsassets/k82/example-webdav-browse-mode-editing/editing_attachment_form_tab.png "File attached to a page")
   - This file is displayed in the summary of the News item on the live site.
3. Open the WebDAV network drive and navigate to _attachments\en-US\News\Record-Sales-in-Q3\\\[NewsTeaser]_. 

   - You should see that the original **Dollar.png** file in the folder.
4. Try copying another image file into the folder.

   - If you refresh the content of the folder (press F5) after a few seconds, you should see that the original file disappeared. This means that the original file in the File field has been replaced with the newly uploaded one.

The newly uploaded file should now also be visible in the UI.