In case your customers, through metrics, publish sensitive data, e.g., recipes/programs/schemes that are subject to trade/commercial secrets, and for no reason, users outside the company should access them, you can mark these metrics as privatizable.
When a metric is marked as privatizable, the end customer can decide whether actually to make it private. Data from private metrics can only be read by internal customer users; other users (organization, partners, and data recipients) will not get any results, either from the  frontend or via API requests from third-party systems.

Configuring Privatizable Metrics

To make a metric Private, you should:

1. Enter the Catalog page and then select a Thing Definition.

2. Select the Private metrics enabled checkbox. 
   

3. Go to the Metric you want to privatize and select the Privatizable by customer checkbox.
   

4. Now it's the customer's turn to decide whether to make the metric private or not.

Note that all types of metrics  (e.g., Computed, Insights) can also be made privatizable.

Configuring Private Metrics in the DPS

By logging into DPS as a customer user, it is possible to define whether a metric is private or not.

Prerequisites

• A real DPS user must be logged in. So, Console Views cannot be used.

• The user must have the Customer account administrator permission.

How to make a metric private:

1. Log in to the DPS as a customer user.

2. From the User menu, go to the Account page and select the Privacy tab.

3. Select the metrics you wish to make private and save. By default, all metrics are public.

If necessary, by changing the Make All Data Public switch, private metrics can be unlocked for a limited period of time (24 hours).

After the timeout date, the metrics will be restored as private.