> ## Documentation Index
> Fetch the complete documentation index at: https://docs.izumi.akiaconsulting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Source: upload

> Add documents by hand.

Checked on Izumi 0.5.7, 2026-11-21.

An **Upload** source is for documents you upload by hand, from a folder or as files, with no connection to an outside system. This page also covers the **Web clip** source, installing the web clip extension and the policy text your people see in the extension.

## Before you start

* You must be a company admin.
* The company must have at least one domain. Every uploaded file goes into the domain you choose.
* `.md` and `.txt` files are accepted, or a `.zip` that contains them (from the code).

## Create an Upload source

**1. Add a source**

Open **Sources** and click **Add source**. Choose the card **Upload** ("Upload Markdown (.md) and text (.txt) files from a folder."). The dialog **Upload a Markdown folder** opens.

![Izumi, Upload a Markdown folder dialog](https://mintcdn.com/akia-consulting/RvQAknt4j1yWbS4K/images/en/sources-upload/01-add-upload.png?fit=max\&auto=format\&n=RvQAknt4j1yWbS4K\&q=85\&s=fe1f17dfd630933fc7b4b9bb25f035f3)

**2. Enter a name and choose a domain**

**Source name** has up to 120 characters, otherwise it says *"Enter a name (up to 120 characters)."* The **Domain** list offers the domains of the company: "Every uploaded file goes to this domain. You can change it later." Click **Create source**. The message is *"The source was created. Add files under Rules and scope."* The new card has the label **New**.

**3. Open Upload files**

Click **Rules and scope**. The section **Upload files** has the fields **Domain**, **Folder** and **Files**. The buttons for choosing a file are drawn by the browser, so their text follows the browser language, not the Izumi language.

![Izumi, Upload files section on the source card](https://mintcdn.com/akia-consulting/RvQAknt4j1yWbS4K/images/en/sources-upload/02-upload-files.png?fit=max\&auto=format\&n=RvQAknt4j1yWbS4K\&q=85\&s=94390d889f40d25396a5fa683c81a2f9)

**4. Upload**

Choose a folder or files. The upload starts at once. The message is for example *"Uploaded: 1, skipped: 0."* After a few seconds the card shows the number of **Documents** and the state **OK**.

![Izumi, upload finished](https://mintcdn.com/akia-consulting/RvQAknt4j1yWbS4K/images/en/sources-upload/03-upload-done.png?fit=max\&auto=format\&n=RvQAknt4j1yWbS4K\&q=85\&s=2f9c28e362381e274a53ec106ac88798)

The same file with the same path and changed content updates the existing document, it does not create a new one (checked live: the number of documents stayed the same). You change the domain of the source in the **Domain** list in the **Upload files** section: *"Domain saved. New files go there."* Files that were already uploaded stay in the old domain (from the code).

### Deleting an Upload source

The three-dot menu on the card has **Delete source**. The dialog **Delete the source?** says that the source and all its documents are removed and that this cannot be undone. Click **Delete**. The message is *"The source was deleted."* The source and the documents are gone (checked live).

## The Web clip source

The **Web clip** source is not created by hand. It appears by itself when the first web clip arrives in the company, and then the card shows up.

**1. Look at the card**

The card has the name **Web clip**, the kind label **Web clip** and the state **OK**, with the number of documents. The text on the card says the extension fills it and that nothing is connected or imported here. There is no **Rules and scope**, only the three-dot menu.

![Izumi, Web clip source card](https://mintcdn.com/akia-consulting/RvQAknt4j1yWbS4K/images/en/sources-upload/04-web-clip-source.png?fit=max\&auto=format\&n=RvQAknt4j1yWbS4K\&q=85\&s=80e43d939f5f4ee47914c4822d05710c)

**2. Delete the source (if needed)**

**Delete source** deletes all clips of the company, and the dialog lists the number of documents. A single clip is not deleted from the document list.

How people send clips is on the page [Web clip](https://docs.izumi.akiaconsulting.com/en/using/web-clip.md).

## Web clip policy text

The policy text is a short company rule that the extension shows before a page is sent, for example what may be sent.

**1. Enter the text**

Open **Companies and members**, section **Settings**. The field **Web clip policy text** takes up to 1000 characters, and the counter is next to the field. Click **Save settings**. An empty field means nothing is shown.

![Izumi, Web clip policy text field](https://mintcdn.com/akia-consulting/UfDKk95B0JApANc6/images/en/companies-domains-roles/04-clip-policy.png?fit=max\&auto=format\&n=UfDKk95B0JApANc6\&q=85\&s=efc3c6fdb115657fab871ab5e992887f)

**2. Example text**

"Send only pages that your team may keep and that are not confidential. Do not clip pages that show personal data, client passwords, or internal systems. A clip is readable by everyone who can read the domain you choose."

The text is shown as plain text above the choice of domain, every time a person selects that company in the extension (from the install guide, not checked live). Remind people that a clip is a copy of the page as text, that it is kept as an untrusted source, and that search results mark it as a web clip.

## Install the web clip extension

The extension is not in the extension store. The administrator sets it up, and each person creates their own token.

> [!WARNING]
>
> Not checked live yet: this whole section. The description is from the product's install guide. Installing by policy on a managed Chrome or Edge computer waits for the first client with managed computers.

* The operator packages the extension (CRX and `updates.xml`) and puts it on any https static host the computers can reach. The Izumi server does not host it. The files contain no token and no server address.
* The extension reads a page only when you press its button. From Izumi it reads only the list of domains where you are an editor and the policy text of the company.
* Forced installation outside the store works only on managed computers: Chrome on Windows in an Active Directory domain, Azure AD or Chrome Enterprise Core, Chrome on macOS through MDM or Chrome Enterprise Core, Edge on macOS through MDM, Edge on Windows only in an Active Directory domain (outside a domain only Edge Add-ons). A personal computer without management ignores the policy.
* Chrome: the policy `ExtensionSettings` with `installation_mode` `force_installed`, `update_url` and `override_update_url` `true`. Check on the computer: `chrome://policy` and `chrome://extensions`. Edge: the same structure, check `edge://policy` and `edge://extensions`.
* Fallback for unmanaged computers: the Chrome Web Store with visibility Unlisted. Each person installs from a link.
* Per person: create a web clip token (see [Web clip](https://docs.izumi.akiaconsulting.com/en/using/web-clip.md)) and in the extension settings enter **Server address** (https, http only for `localhost`) and the token. The server address is not pre-filled by policy, so everyone enters it once. The token is valid for at most 90 days.
* Removal: revoke the person's token. The extension stays, but every send is refused. A web clip token stops working for a domain as soon as the person loses the editor role there.

## Limits

* Upload accepts `.md`, `.txt` and a `.zip` that contains them. Other kinds are skipped and counted in "skipped" (from the code).
* At most 50 MB per file, 1000 files per upload, 10000 entries from zip files and 256 MiB in total in one upload (from the code).
* The path of a file is its outside id in the source. The same name with the same path updates the document.
* A web clip is not deleted one by one. The whole **Web clip** source is deleted.

> [!WARNING]
>
> Not checked live yet: the size and count limits, changing the domain of the source after uploading, and uploading kinds of files that Izumi skips. One `.md` file was checked live, in the English and the Serbian version.

## Troubleshooting

* *"The upload is too large. Send fewer or smaller files."* Send fewer files at once (from the code).
* *"The files could not be read. Send .md, .txt or .zip files."* The file is not in a supported format (from the code).
* *"The upload failed. Try again."* A general error. Repeat the upload.
* The card still says **New** and 0 documents after the first upload. Once we saw a card not refreshing for almost half a minute, and only the second uploaded file helped. We did not check whether reloading the page is enough.
* The **Web clip** source does not exist. It appears only after the first clip in the company.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.