In case your customers, through metrics, publish sensitive data, e.g., recipes/programs/schemes that are subject to trade secret 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 client can decide whether to actually make it private. Data from a private metric can only be read by internal client users; other users will not get any results, either from the DPS frontend or via API requests from third-party systems.

Configuring Privatizable Metrics

In order 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 the turn of the customer to decide whether to make the metric private or not.

Note that Computed metrics and Insights can also be made privatizable.

Configuring Private Metrics in the DPS

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

1. Log in to the DPS as a Client user.
   Note that Console Views cannot be used; a real DPS user is required.

   
   

   The user must have the Customer account administrator permission

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

3. Select the metrics you wish to make public 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.