> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/configurator/product-setup/general-product-settings.md). # General product settings Set product names, availability, access, categorisation and preview images in the General tab. The **General** tab holds a product’s core information: its names and code, availability, access settings, categorisation and preview images. To open it, go to **Products**, select a product and open **General**. This tab is available for **Standard, Component, Modular and Hybrid Modular** products. The controls you can edit depend on your permissions and account features. Many of these fields also appear as columns in the **Products** list, where you can search and filter by them. See [Admin Panel Overview](/configurator/getting-started/admin-panel-overview.md#products-list). {% hint style="info" %} **Component products:** The General tab is still available, but Privacy, Brand Information, Product Groups, Product Categories, Visible in Menu, Mouseover and Zoom disabled are hidden. Components cannot be embedded independently. Name, Display Name, Variant Code, Description, Status, Tags and the standard preview image remain available. {% endhint %} ## Name and code
FieldWhat to enter
NameThe internal name used in product administration. You can make it more descriptive for your team; it is not the name shown publicly to customers. Required.
Display NameThe name shown in customer-facing product lists and on the configurator panel. Required.
Variant CodeThe product’s unique identifier, used in configurator links and integrations. Choose a clear code when you create the product, and normally keep it unchanged.
Name and Display Name support multiple languages. Use the language controls to provide the appropriate text for each language you use. {% hint style="warning" icon="triangle-exclamation" %} **Keep the Variant Code stable.** It can be edited, but changing it may break existing links, configurations or integrations that use the previous code. Read the warning in the app and check those references before changing it. {% endhint %} ## Description Use **Description** for a formatted description of the product. It supports multiple languages, bold and italic text, lists and links. The text can be used in PDF output or custom integrations, depending on how those are configured. ## Status, privacy and menu visibility These controls answer different questions: * **Status:** Is the product available for customers to use? * **Privacy:** Who can access it? * **Visible in Menu:** Should it appear in the product list? ### Status **Active** allows the product to be used by customers, subject to its privacy and listing settings. **Inactive** removes it from normal customer use, including embedded configurators and customer product lists. You can still manage the product in the Admin Panel. Status is a functional setting, not just an informational label. ### Privacy For Standard, Modular and Hybrid Modular products, choose: * **Public:** Available to customers without a company-group restriction, provided the product is Active. * **Restricted:** Available only to customers in the selected **Company Groups**. * **Private:** Kept for internal access by users of your company with the appropriate permissions; unavailable for normal public customer access. When you select Restricted, assign the Company Groups that should have access. Create and manage these under **Settings → Data → Company groups**. {% hint style="info" %} **Restricted access requires customer authentication.** Configure authentication so Mimeeq can identify the customer and their company-group access. See [Restricted Access](/users-and-permissions/access-and-login/restricted-access.md) before using this setting. {% endhint %} For example, with authentication configured, select Restricted and assign a “Trade Customers” company group to make the product available only to those customers. ### Visible in Menu Use **Visible in Menu** in the Product Groups Assignment area to control whether the product appears in the customer product list. Turning this off does **not** make the product private. An Active, Public product can still be opened directly in its configurator even when it is hidden from the list. Use Privacy or Status when you need to restrict access. {% hint style="danger" %} **Check the impact on shared customers.** If a product is already shared with other customers, making it Inactive or Private, or changing it to Component, can deactivate their linked products. When an affected sharing connection exists, Mimeeq shows a warning and requires you to type **CONFIRM** before accepting the change. Read the message and check the impact before continuing. Changes to Restricted access can also require you to review sharing connections. See [Sharing as Owner](/configurator/sharing-products/sharing-as-owner.md) for the sharing workflow. {% endhint %} ## Product type The product mode determines how the configurator works and which editor tabs are shown. See [Product Types](/configurator/getting-started/product-types-and-limits.md) for the differences between Standard, Component, Modular and Hybrid Modular. You can switch between **Standard, Component and Hybrid Modular** where your account features and permissions allow. Existing products **cannot be changed into or out of Modular mode** through the General tab. Shared-product restrictions may also prevent a change. Review existing configurations and rules after changing the mode. ## Brand information Available for Standard, Modular and Hybrid Modular products.
FieldPurpose
ManufacturerThe company that manufactures the product.
DesignerThe designer or design studio behind the product.
CollectionThe brand or collection the product belongs to.
These values help customers find products through search in the Business Panel product list. Where Collection is displayed in the configurator depends on the layout; it does not have a fixed screen position. ## Tags Add keywords to help find the product in the Business Panel product list. Type a tag and press **Enter** or **Tab** to add it, then enter the next tag. A comma is not the tag separator. For example: `outdoor`, `dining`, `clearance`. ## Product groups and categories Available for Standard, Modular and Hybrid Modular products. **Product Groups** let you create filtered product lists for embedding on your website. Create the groups first under **Settings → Data → Product groups**, then assign the product to the relevant groups in General. Only active groups are available for selection. **Product Categories** organise the navigation tree in the product list. Create them under **Settings → Data → Product categories**, then assign the product to the relevant categories. The category selector is shown when **Visible in Menu** is on. Groups select the products included in a list; categories help customers browse that list. See [Product Categories](/configurator/getting-started/product-categories.md) and [Embed Types](/configurator/embeds-and-translations/embed-types.md) for more detail. ## Preview images Preview images present the product in listings. Choose an image that is clear at thumbnail size.
ControlWhat it does
Standard viewSets the default product preview image. Available for all product modes.
MouseoverSets an alternative image shown when a customer hovers over the product in a desktop product list. Not available for Components.
The same as standardUses the Standard view image for Mouseover. Turn it off to choose a separate hover image.
Zoom disabled

Stops the preview image enlarging on product-list hover.

To avoid confusion, it does not disable zooming the 3D model inside the configurator. Not available for Components.

--- # 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://help.mimeeq.com/configurator/product-setup/general-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.