> 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/~/changes/eaCuYFhybbREuBouwZp6/client-profile/client-profile-settings/sensitive-settings.md).

# Sensitive Settings

### Keep everything safe with sensitive settings!

Are you storing important information such as employee records, financial reports or customer data? If yes, then Sensitivity is the great tool for you :tada:

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FHNFITpYC5y9A7EuUyBa5%2FSensitive%20setting%20open.png?alt=media&amp;token=35842abe-1059-4594-82c8-07f382edde56" alt=""><figcaption></figcaption></figure>

### What is Sensitive Settings?

Sensitive Settings allows users to manage  and control access to sensitive content stored on the system :thumbsup:

{% hint style="info" %}

### Why should you use Sensitive Settings?

Sensitive Settings helps you automatically track and manage sensitive assets, ensuring these assets are not accessed illegally

For example, you belong to the human resources department and want to manage candidate records and limit access to the admissions department.
{% endhint %}

### How to use Sensitive Settings?

Using “**Sensitive Settings**" is extremely simple, just a few basic steps:

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2Fa8Bodde1aZwv15fZf1Pi%2Fsensitive%20setting.gif?alt=media&amp;token=0679a47c-f7a1-4749-9c72-3d9a696cc3fe" alt=""><figcaption></figcaption></figure>

1\. **Search for Sensitive Settings: Client Profile => Setting => Sensitive Settings**

2. **Adjust Archive Setting**: Select settings appropriate to your organization's digital assets and operations:

* **Enable default Sensitive date**: Mark Assets as Sensitive after number of days after initial upload. "**Sensitive assets**" can only be seen by Users who have **user rights** to do

\+ Functionality: This setting allows uploaded assets to be automatically marked as "sensitive" after a certain number of days from the original upload date.&#x20;

\+ What it means: This setting is useful for assets that are time-sensitive, such as financial reports or personal information. Automated marking helps ensure that these assets are not accessed without authorization after their useful life has expired or they are no longer relevant.

* **Notify Admins when Assets are marked as sensitive:**&#x20;

\+ Function: This setting notifies administrators when an asset is marked as "sensitive".

\+ What it means: This setting helps administrators monitor the management of sensitive assets and can take necessary actions, such as reviewing access permissions or applying additional security measures.

* **Notify Admins prior to Assets being marked as sensitive**: Notify Admins number of days before Assets are marked as sensitive

\+ Functionality: This setting notifies administrators before an asset is marked as "sensitive", along with the number of days before the mark.&#x20;

\+ What it means: This setting gives administrators time to reconsider marking assets as "sensitive" and take necessary actions, such as changing settings or excluding assets. property from the automatic rule.

3. **Save settings**: Save changes so this takes effect for future uploaded Assets.

Once installed, "**Default Sensitive date**" will become the default value for uploaded assets.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2F0UnYCYWQJQmxrQb4qjNw%2FSensitive%20date%20upload%20setting.png?alt=media&amp;token=098e1b78-4a30-45e7-a9f3-10c1090aab06" alt=""><figcaption></figcaption></figure>

Users can also edit the "**Archive date**" after uploading the asset by accessing the asset in **The Library => View detail => Permision => Sensitive date**

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FrVhQiYz1zlSj9X9LI6NY%2Fsensitive%20setting%20access%20permission.gif?alt=media&amp;token=98e31fd3-53a1-435c-9c0b-0bf0f70f8a3a" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.hivo.co/~/changes/eaCuYFhybbREuBouwZp6/client-profile/client-profile-settings/sensitive-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.