Controlling data visibility and access in a dataset

If your dataset contains sensitive information that you don't want some or all users to see, Huwise provides dataset settings to control data access and visibility.

This page summarizes which settings to use, what they do, and when to use each option.

• Restrict access to sensitive data
  You'll use the dataset's Security tab to control access to the dataset and who can see what data.

• Organize the dataset and hide unnecessary data
  If you don't necessarily need to limit access to specific users or groups, but want to just better organize your dataset, you can hide unnecessary data by removing columns from the Schema tab.

• Give users a purposeful or simplified view of the data
  In this case, you're not so much worried about access to data, but instead want to give your dataset clarity or help it tell the right story. For that you're going to create a custom view.

Use the dataset’s Access and Security tabs when you need to limit who can see data.

Use this option for personal or confidential data, internal-only fields, or fields that should be visible only to specific groups.

When limiting access, be sure to test those access settings using an account with access identical to the one you're testing.

Use the Access tab to limit access:

• To specific users

• To groups of users

Then, for those users or groups, on the Security tab you can:

• Limit access to specific fields (columns) or records (rows) — meaning they will no longer be visible in the portal nor be queryable via the Explore API

• Place limits on the number of API calls those users or groups can make to the dataset

See A dataset's Security tab for more information.

If you just want to make sure your dataset is cleaner and easier to navigate, you can hide obsolete, temporary, or disused data by removing columns from the Schema tab.

Note that for less important columns, you can also simply move them to the far right of your dataset. They will still be visible, but simply will not clutter up the most-visible data.

Columns removed via the Schema tab will:

• Not be visible to your users in the portal

• Not be immediately visible in the back office (though it can easily be restored)

• Not be available to any processors, though it can easily be restored

• Not be queryable via the Explore API

See Defining a dataset schema for more information.

Use Custom views when you want to present a clearer or more focused version of a dataset. Create a custom view if you need a specific view with filtered, sorted, or limited columns. The full dataset will remain available, but you can control which view of your asset comes first.

Custom views are useful:

• When you want to show an additional, more purposeful presentation of your data

• To create a table view for a specific audience (as well as charts, maps, or KPIs)

• To build an intentional portal experience without changing the dataset itself

See Creating custom views for more information.