> 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/organisation-and-storage/product-settings.md). # Product Settings Product data lifecycle and quality control ### What are Product Settings? Product Settings allow Client Admins to define how Products are created, displayed, and checked in HIVO. For example, a Product might have been created but lacks a SKU, has no Description, has not been tagged or the Product's Asset is not ready to be published. Product Settings help businesses standardize these requirements into common rules within the system, rather than relying on users to remember a checklist on their own. πŸ‘‰ Instead of letting each user create Products in different ways, Client Admins can configure:

Product Status Settings

The statuses that Products can use & default status when creating a Product

Product List View Settings

The information displayed in the Product List

Product Custom Attributes Setting

System Attributes, Custom Attributes, and Metadata that need to be collected

Product Metadata Settings

Which Metadata fields are mandatory right upon Product creation

Product System Attributes

Which fields must be completed before a Product passes the quality check

Quality Control Settings

Whether Assets linked to a Product need to pass the Readiness Check
⚠️ **User Right Required:** User must have the permission: *β€œIs Client Admin - User can manage the Client Profile”.* **πŸ”Ή** Navigate to Product Settings: **Client Profile** -> **Settings** **tab** -> **Product** **Settings**
### **1. Setting up Status Settings** Status Settings determine the statuses used to represent which stage a Product is at in the workflow. * **Add Status Options:** Enter a new status name (e.g., *Draft, In Progress, In Review*, ). * **Select Default Status for new products:** In the **Default Status** section, select a status to be automatically applied to newly created products (e.g., *Draft*).
* When creating a Product, the default status will be automatically applied. However, you can still customize the status to suit your needs when [**adding or editing a Product**](https://support.hivo.co/products/add-new-product-and-edit-information).
*** ### **2. Customizing list View Settings** List View Settings allow the Client Admin to decide what information appears directly in the Product List (e.g., Product Name, Price, Created Date, etc.). * **Reorder columns**: Click and drag to arrange the columns in your preferred order. Keep only the columns you frequently use to make the interface cleaner and easier to follow. * Add new Column: Select **+ Add Column** to add more information to the Product List.
* **Preview example:** Product list displayed according to settings
*** ### **3. Product Attributes Settings** Product Attributes allows Administrators to configure the fields used to describe a Product within HIVO, while controlling which attributes appear during Product creation, which fields are mandatory, and which are evaluated in the Mandatory Attributes Check. Product Attributes consists of two categories: * **Product System Attributes:** Built-in HIVO attributes, including Product ID, SKU Code, Label, Description, and Tags. * **Product Custom Attributes:** Custom attributes defined by the organization to fit its specific Product data requirements. ### 3.1. Configure Product System Attributes Under the Product System Attributes section, you will see the default Product attributes provided by HIVO, such as: *Product ID, SKU Code, Label, Description, Tags.* * **Include in Mandatory Attributes Check:** Enable Include in "Mandatory Attributes Check" for the attributes you want HIVO to evaluate during the Product data completeness check.
* For example, if SKU Code, Label, and Description are enabled: * HIVO will verify these attributes when running a Mandatory Attributes Check. * If a Product is missing a value for any of these selected attributes, it will be flagged as incomplete for the corresponding Mandatory Attributes.
⚠️ Note: Enabling *Include in Mandatory Attributes Check* does not mean the user is forced to enter that field during Product creation. Entry enforcement is controlled separately by the Is Required setting for Custom Attributes. ### 3.2. Configure Product Custom Attributes Product Custom Attributes allows you to create custom fields tailored to your organization's Product management workflow. You can organize related Attributes into a Group and use various data types, including **Text, Date, and Table.** #### πŸ”Ή Detailed configuration instructions Configurations are organized by Attribute Groups. Within each group, you can configure each individual attribute with the following components: * **Attribute Name:** Enter the identifying name for the attribute (e.g., Demo 1, Demo 2). * **Type:** Select the input format for the attribute, including: Text, Table, Date * **Description:** Add a brief note or guideline about the attribute (defaults to None if not needed). * **Default Value:** Set a pre-filled value for the attribute if applicable (defaults to None). * **Selectable Options**: Enter a list of suggested/pre-defined values for users to choose quickly during data entry. Add a new attribute: Click the **+ Add Attributes** button #### πŸ”Ή Configure how the Attribute will be used: * **Include in Product Creation:** Displays the Attribute in the Product creation form. * **Is Required:** Requires users to enter a value for the Attribute when creating a Product. * **Include in Mandatory Attributes Check:** Includes the Attribute in the Product data completeness check. *You can use the ↑/ ↓ arrows to reorder display hierarchy or click Γ— to delete an Attribute.* #### πŸ”Ή **For Examplae: ExConfiguring the "Nutrition & Ingredients" Attribute Group** Suppose your organization operates in the Food & Beverage (F\&B) sector and needs to track detailed nutritional tables and ingredient lists for products. You can set up the configuration under Product Custom Attributes Setting as follows:
*** ### 4. **Product Metadata Settings** **Product Metadata Settings** is a feature used to configure information fields (metadata entries) associated with products in the system. This feature allows Client Admins to **define custom attributes** (such as field name, data type, default value, selectable options) to collect detailed information or categorize products when creating or uploading them. πŸ‘‰ To access and configure this, go to **Product Settings** β†’ locate **Product Metadata Settings.** #### πŸ”Ή Step 1: Add a New Metadata Entry Add a new field: Click the **+ Add Metadata Entry** button at the bottom of the list if you want to add more metadata fields for the product. #### πŸ”Ή Step 2: Fill in the product metadata components Each Metadata Entry includes the following main settings: * **Entry Name:** Enter the identifying name for the metadata field (e.g., Demo 1, Demo 2). * **Type:** Select the display and input format for the field, HIVO offers options for text and date. * **Description:** Provide a brief note or guideline on the purpose of this field to help users input data accurately. * **Default Value:** Set a pre-filled value for the field if necessary (or leave it as None). * **Selectable Options:** Enter a list of available option values so users can quickly select them during operation. #### πŸ”Ή Step 3: Configuring Product Metadata display conditions * **Include in Product Creation**: Check this box if you want the metadata field to appear in the product creation/upload workflow. * **Is Required:** Check this box if it is mandatory for users to fill in/select a value before completing.
#### πŸ”Ή Step 4: **Conditional Display Setting** * Select the condition field Under *β€œ**Show metadata entry in Product metadata when 1+ metadata value are entered in any of the following entries**”*, select the related field. * If one field is selected: The field being configured will appear when the related field has at least one value entered. * If multiple fields are selected: The field will appear as long as at least one of those fields has a value. * Leave empty: The field being configured is always displayed. * Select a specific triggering value - if needed. Under *β€œ**Optionally require certain metadata value are entered from the dependent entry list**”*, select the specific value to use as a condition. * Select a specific value: The field only appears when the selected input matches that condition. * Leave empty: Any value in the related field will trigger the display, without restricting to a specific value.
*** ### 5. **Quality Control Settings** Quality Control Settings allows administrators to configure data quality review and approval processes before products or digital assets are officially put into use.This feature helps ensure that all created products comply with the enterprise's strict data standards, contain all mandatory attributes, and have their attached asset files ready. ⚠️ Note: This feature is currently in development and is subject to change or updates in upcoming releases. πŸ‘‰ To access and configure this, go to **Product Settings** β†’ locate **Quality Control Settings.** #### πŸ”Ή Step 1: Enable Quality Control Process * Activates all system filters and quality controls. When this option is disabled, the verification processes below will be temporarily suspended. #### πŸ”Ή Step 2: Select Quality Check Options: Once the Enable Quality Control Process toggle is turned on, you must enable at least one of the following check types (or both): #### 1. Enable Mandatory Attributes Check * Products can only transition to a ready/published status if the user has filled in all mandatory attributes.
* When this option is enabled, the system automatically scans and checks all data fields marked as required ***(Include in Mandatory Attributes Check***) within the **Product System Attributes** and **Product Custom Attributes Settings.**
#### 2. Enable Asset Readiness Check * This option ensures that assets (images, videos, etc.) linked to the product meet all readiness criteria for use. * Select Readiness Form configuration: In the Select Readiness Form field, click the dropdown menu. * Select the appropriate readiness check form from the list. * This form will be applied to evaluate the digital assets linked to the product.
Once "Quality Control Process" is enabled, assets will be scanned and checked. Administrators can view the results by going to **Products β†’ Quality tab** and clicking on the desired asset
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/organisation-and-storage/product-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.