> 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/faqs/how-to-hide-custom-versions-while-keeping-cdn-link.md).

# How to Hide Custom Versions while keeping CDN link

If your organisation uses an integration such as **Drupal** and has a Custom Version specifically created for that integration, you may not want general users to see this Version when working with Assets in HIVO.

For example, if a Custom Version named **Drupal Web** is used by your Drupal integration, a Client Admin can configure this Version to be **hidden by default in HIVO**, while keeping it available for Drupal and maintaining its CDN URL.

⚠️ **User Right Required:** User must have the permission: **“Is Client Admin - User can manage the Client Profile”.**

#### **🔹 Step 1: Open the Custom Version**

* Go to: **Client Profile -> Settings -> Version Settings -> Automated Versions**
* Select the Custom Version used for the integration, for example **Drupal Web**.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FbMvZtTf1o76AkPd8TwVB%2FGroup%20904.png?alt=media&amp;token=82da276c-e407-4fc4-a21e-aa07fa120136" alt=""><figcaption></figcaption></figure>

**🔹 Step 2: Configure the Version**

Configure the Version settings based on your requirements, such as **Type, Quality, Dimensions, Fit, Background, Colour Space, DPI**, and other available options.

These settings determine how the Version will be generated and processed when it is created.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2Fkr6M3rU8pOUyVxg9Jj7C%2FGroup%201130.png?alt=media&amp;token=de1edcd3-5df4-4fa4-bf2c-fce39d17bf85" alt=""><figcaption></figcaption></figure>

#### **🔹 Step 3: Configure Version Visibility**

To hide the Version from general users while keeping its **CDN URL accessible** and the Version available in **HIVO Connectors**, enable both options:

* **Hide this version by default:** Hides newly created Versions of this type from users who do not have the **Can See Hidden Versions** right.
* **Skip filtering hidden versions for connectors:** Keeps the hidden Version visible and accessible through **HIVO Connectors**.

With both options enabled, the Version is **hidden from general users in the HIVO App, remains available in HIVO Connectors, and its CDN URL continues to work as normal**.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FxzKPC564lC59VfZO2afe%2FGroup%201131.png?alt=media&amp;token=39da8a23-ccf3-442c-95cd-38c7e4921db9" alt=""><figcaption></figcaption></figure>

👉 For example: Drupal Web created → Hidden from general users in HIVO → Available through Drupal → CDN URL remains functional

The default hidden setting is supported for:

* **Automatic Version creation** when Assets are uploaded.
* **Manual Custom/Resize**, including resizing through **Drupal and Salesforce**.
* **Creating or overwriting an existing Version** by manually uploading a new Version in the main HIVO App or through supported extensions/plugins.

Note: Hiding a Version does not disable or delete it. **CDN URLs for hidden Versions remain functional and publicly accessible**, regardless of these settings.

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/faqs/how-to-hide-custom-versions-while-keeping-cdn-link.md?ask=<question>&goal=<user_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.
