Permissions overview

To allow another user to reference one of your datasets, you can use the Platform to create a permission.

When you use the Platform to import a dataset, we say that you own it. At first, datasets which you own are visible only to you.

Each permission gives a single user the ability to reference a single dataset. If you want a user to be able to reference more than one dataset you own, create a permission for each one.

A permission does not grant access to your Bunker, and it doesn't allow access to individual records or to your original data. You always remain in control of permissions for datasets you own. If you give another user permission to reference a dataset, they can't extend that permission to anyone else.

When you create a permission, you define how another party can use your dataset. You will be presented with a series of decisions with many different permutations. For insight and activation datasets, the options available are slightly different.

Insight dataset permissions

Use the permissions below to decide how another party can analyse, query and activate your insight datasets.  All sent permissions must contain a setting from level 1 and level 2. Level 3 contains optional settings.

See example permissions for examples of how another party can use your dataset.

Level 1 permissions

These permissions let you select what the other party is able to do with your data.

Permission setting

What can be done with my data?

View meta-data and assess the intersection with other datasets

The other party can see statistical data only for the intersection with your dataset where you have matching records. The other party cannot query the intersection.

The other party can view meta data for your dataset and change the Private ID.

Query the intersection with other datasets

The other party can query the intersection only between your dataset and theirs where you have matching matching records.

Query the whole dataset

The other party can query anything in your dataset regardless of whether or not they have matching records.

Level 2 permissions

These permissions let you select how the other party can use your data.

Permission setting

How can my data be used?

In combination with datasets they own

The other party can only query your dataset with datasets they themselves have uploaded.

If you’re unsure, we recommend selecting this option as you can always change this permission later on.

In combination with datasets they own or have permission to use

The other party can query your dataset with datasets that other people have given them permission to see or datasets they themselves have uploaded.

Level 3 permissions

These permissions let you select how records found are sent from the Platform. Selecting these options allows raw individual record information to be sent from the Platform.

Permission setting

How can my data be sent from the Platform?

And including activation bunkers

The other party can use your insight dataset in an activation query.

Warning: Selecting this option on its own means the other party can send raw individual record information to someone else.

Restrict to use with activation bunkers owned by you

The results of an activation query by the other party always come back to you.

This option is always selected by default. This prevents the other party from sending records to someone else. 

The permissions settings tree on the right highlights the permissions you have selected. Hover your mouse over an icon to see information on a permission.

An error message appears if you select a combination of permissions that are incompatible. For example, if you restrict access to your activation bunkers, but do not combine this with access to datasets the other party has permission to use.

Activation dataset permissions

The permissions you can give for activation datasets are slightly different, as shown below.

See example permissions for examples of how another party can use your dataset.

Level 1 permissions

These permissions let you select what the other party is able to do with your data.

Permission setting

What can be done with my data?

View meta-data and assess the intersection with other datasets

The other party can see statistical data only for the intersection with your dataset where you have matching records. The other party cannot query the intersection.

The other party can view meta data for your dataset and change the Private ID.

Query the intersection with other datasets

The other party can query the intersection only between your dataset and theirs where you have matching matching records.

Query the whole dataset

The other party can query anything in your dataset regardless of whether or not they have matching records.

Level 2 permissions

These permissions let you select how the other party can use your data.

Permission setting

How can my data be used?

In combination with datasets they own

The other party can only query your dataset with datasets they themselves have uploaded.

If you’re unsure, we recommend selecting this option as you can always change this permission later on.

In combination with datasets they own or have permission to use

The other party can query your dataset with datasets that other people have given them permission to see or datasets they themselves have uploaded.

The permissions settings tree on the right highlights the permissions you have selected. Hover your mouse over an icon to see information on a permission.

You can also restrict the destination of any results to a push-connector of your choice. This means that the other party could use your activation dataset to run activation queries, but would not be able to see the results. These results can only be pushed to the location defined by you when creating the permission, such as your SFTP server or Amazon S3 storage, so stay within your control at all times.

Monitoring usage

You can view the usage of any permission by switching to the Permissions Sent tab on the left side menu - and vice versa in the Permissions Received tab.