Skip to main content

Visibility groups


If you plan on testing this, please use newly created organization units.

Once you add an organization unit to the visibility group, it cannot be reversed in terms of the data anonymity applied. The data that has been made anonymous as a result of your choice here is irreversible, and will remain anonymous even after un-ticking the respective box.

Visibility groups is a chapter mainly built for GDPR purposes. In this chapter you can control the anonymity of three data categories:

  • Users: This refers to customer data (customer address, contact details, etc...).
  • Orders: This refers to order details (order lines, status, type, quantity, etc...).
  • Organization units: This refers to organization unit details (store address, contact details, etc...)

Based on the organization unit in which the user is accessed from, and your visibility group setup, you can control which of these three types of data can be anonymized and which can be visible.

The visibility groups' initial page gives you an overview of all existing visibility groups in place and the possibility to edit existing or create new ones.


In order to be able to access this chapter, you need the VisibilityGroups permission.

As always, the right side of the screen has an array of filter options to easily search across your current visibility groups.

Create new visibility groups

By tapping + on the top right, you will be prompted to input name and description.

Once you tap create, two new cards will be presented to you: Organization units and Visibility group configuration.

Organization units card

Here you can specify which organization unit(s) will be part of this visibility group.

Visibility group configuration card

Here you can specify the the anonymity classification of the three data categories.

Ticking a box means that data falling under that category will be shared and visible across the selected organization units, while un-ticking will lead to an anonymous presentation of that data.

Scenerio examples

Here are some scenarios to help make it more clear:

If an order is made from a marketplace, most of the time there isn't a contractual agreement in place that would allow your organization to view or use the ordering customer details (GDPR privacy and security law).

This would mean a visibility group setup that would look like this:

  • Create a visibility group called: marketplace
  • Attach that created visibility group to the marketplace organization unit

By doing so you have now stated that the marketplace data will only be visible within the marketplace organization unit. This setup is sufficient if you only have your default(all OU's are in) visibility group in place.

Now let's assume a different scenario whereas you've agreed with the marketplace that customer data will remain anonymous, but order data can be shared amongst all of your web shops but not stores.

This would mean a visibility group setup that would look like this:

  • Create another visibility group called webshops
  • Attach all your web shops to this visibility group.

If you further want the marketplace to be able to view and make use of your customer data, then you'll need to go to the visibility group default and create a visibility group configuration from default to marketplace with the users box checked (true).


In order to use this chapter the following settings have to be set to true:

  • Security:VisibilityGroups:Users:Enabled
  • Security:VisibilityGroups:Orders:Enabled
  • Security:VisibilityGroups:OrganizationUnits:Enabled