> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/client-profile/client-profile-settings/asset-and-metadata-management/uploader-settings.md). # Uploader Settings Uploader Setting allows you to manage how users upload assets to their accounts The **Uploader Settings** feature allows you to configure default settings when users upload files to the system. This includes ***default permissions, blocked file types, and automation options.***

Benefits of using Uploader Settings

* ***Time-saving**: Predefined permissions and automation options eliminate the need for manual configuration during each upload.* * ***Enhanced security**: Block unsafe file types at the point of upload to minimize security risks.* * ***Consistency**: Ensure uploaded files comply with established content management rules and standards.* * ***Automation**: Apply automated processes such as tagging and categorization to improve asset management efficiency.*

### How to use Uploader Settings? ⚠️ **User Right Required:** User must have the permission: **“Is Client Admin - User can manage the Client Profile”.** * Navigate to Uploader Settings: **Client Profile** → **Settings** **tab** → **Uploader Settings.**

### 1. Configure **Default Permissions** * Set default asset permissions that will apply to a particular user or group, which will appear as being preselected in the upload tool when a user goes to complete an upload. * In the **Default Permissions** section, you will see a list of entities in the system (e.g., *HIVO Demo Account*). * For each entity, you can select a default permission level such as: **can view, can share, can edit, add version, full access.**

### 2. **Blocked Types** * Prevent users from uploading certain types of files. You can block whole categories, or add your own MIME types and file extensions. 👉 **Note:** This is a general check and should not be relied upon as a complete security solution.

#### **2.1. Block a category** * Tick the checkbox next to a category to block every file type in it. * Click a category name to expand it and see the exact MIME types and extensions it covers.

Category	Blocks
Executables	Executable files, applications and installers (e.g. .exe, .dll, .msi)
Documents with Scripts	Macro-enabled Office documents and templates (e.g. .docm, .xlsm, .pptm, .dotm) and Flash files (.swf)
Scripts	Shell, AppleScript, JavaScript, Java, HTML, PowerShell, Batch, Python and PHP files (e.g. .sh, .js, .jar, .html, .ps1, .bat, .py, .php)
Binary / Unknown	Binary files and files with an unknown type (application/octet-stream, .bin)

#### **2.2. Block custom MIME types/ extensions** * In the **Custom MIME types / Extensions** field, type a value and press **Enter**. You can add as many as you need: * **A MIME type**, e.g. `image/png` * **A whole group of MIME types** with a wildcard, e.g. `video/*` blocks all video files * **A file extension**, with or without the dot, e.g. `png` or `.mp4`

* **What users see:** If a user tries to upload a blocked file, the upload is stopped and they see a message naming the blocked type, e.g. *File type ".exe" is restricted from being uploaded*. ### 3. **Set up Automation** * Allows you to choose what automation tasks should run on the uploaded assets during the Asset Details step in the Uploader. * **Visible Default Enabled:** You can select which default automation actions will be preselected to be performed when uploading files. * These preselected options include:

Type	Description
Tag Prediction	Run the auto tagger using image and video recognition technology. Tags will be auto generated on the uploads based on what is actually in the image or video.
Caption Prediction	Allows the system to automatically analyze and generate descriptions for digital assets as soon as they are uploaded. These captions are stored and managed directly within the Metadata section of the asset. You can review and edit these results in the Asset Information section on the Asset Detail page.
Scan Asset Text Content	Automatically read and extract text content from digital asset files, such as images, PDFs, or documents, allowing users to search for keywords that appear within the asset's content, even if the word is not in the file name or metadata.
Face Detection	Run the facial recognition detection technology on images and videos to detect faces.
Generate Transcript for video/audio assets	Automatically generates written transcripts from your video or audio assets using AI-powered speech recognition.
Run Governance Risk & Compliance Checks	Configuration rules uses to determine whether an asset violates policies, laws, or brand regulations
Run Check Asset Readiness	Checks and evaluates digital assets (images, videos, data) against predefined standards.
Create thumbnails	Automatically create a default thumbnail version of the assets being uploaded.
Create web version	Automatically create a default web version of the assets being uploaded.
Create watermark version	Automatically create a watermarked version of the assets being uploaded. These Automation tools will be automatically displayed in the step of adding Asset details during the process of uploading assets to the system.
Create custom version (image only)	Automatically create a specified custom version (size, dimensions, file type etc) of the assets being uploaded.

These **Automation tools** will be automatically displayed in the step of adding Asset details during the process of uploading assets to the system. ### 4. Configure Upload Link Defaults **Upload Link Defaults** allows Admins to set default values and required fields when users create new Upload Links. This helps ensure uploaded Assets are organised correctly with the appropriate permissions and ownership. 👉 Go to **Client Settings** for the client, select the **Uploader Settings** tab, and scroll down to **Upload Link Defaults.** #### 🔹 Step 1: Configure Default Values You can configure four fields:


Field	Description
Library Folder Path	Select or create a folder to store uploaded Assets.
Collection	Select one or more Collections, or create a new one.
Permission	Assign users or groups with Can View/ Can Share/ Can Edit or Can Edit access.
Asset Owner	Select the default owner for uploaded Assets.

#### 🔹 Step 2: Set Required Fields Tick **Required** next to any field users must complete when creating an Upload Link. * If a default value exists, users can change it but cannot leave the field empty. * If no default is set, users must select a value themselves.

#### 🔹 Step 3: Save Settings Click **Submit** at the bottom of the page to save your changes. #### 🔹 Step 4: Creating an Upload Link with defaults When someone opens the Upload Link dialog and starts a new link, the defaults are already filled in. * The first step is to configure the Link Settings (such as duration, setting a maximum limit, and customizing the upload link UI). * On the asset settings step, the folder path, collections, permissions and asset owner show the client's defaults. * Change any value if needed. **Required fields can be changed but not cleared.** * Click **Create Link** to generate **Upload Link.** Defaults take priority over context. If a Library Folder Path default is set, it's used even when the dialog is opened from a different folder. Without one, the dialog keeps using the folder or collection page it was opened from.

#### ⚠️ Important Notes * Only Admins with permission to edit Client Settings can configure these defaults. * Changes apply only to **new Upload Links**. Existing links are not affected. * **Required** fields are enforced when creating new Upload Links, not when editing existing ones. * The selected **Asset Owner** must be visible to the user creating the Upload Link. * Configured default Permissions replace the standard permission automatically granted to the link creator. If you have any questions, don't hesitate to ask, we're always here to help! --- # 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://support.hivo.co/client-profile/client-profile-settings/asset-and-metadata-management/uploader-settings.md?ask=&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.