Skip to end of metadata
Go to start of metadata

When data block definitions have been created, the associated data blocks are available in shared HoriZZon sites that are based on that model package. Without data policies, the data blocks are editable in sites, via the data block sections below the element's Properties section. Data blocks can be edited by any Contributor user with access to the site (unless write access has been limited).

When using data policies, data blocks will also be available on the model package data entry page in HoriZZon. This page shows all elements with data blocks within the package the Contributor user is able to edit. The user does no longer need to visit the pages in sites to edit the data blocks. In fact, this user doesn't need access to sites to be able to edit the data blocks. Data policies allow you to:

  • Limit data block editing for Contributor users.
  • Enable Contributor users to edit data blocks on the model package data entry page.
  • Set up data maintenance for data blocks.

Data policy configuration possibilities

Data policies are defined in HoriZZon, in each model package containing elements with data blocks. Currently, data policies can be set for individual diagrams, views, objects, and relations. You have the following options for configuring data policies:

  • At element level. You set up one default data policy for all data blocks attached to the element (diagram, view, object, or relation). It allows you to assign general editor permissions that apply to all data blocks present.
  • At data block level. You set up a data policy per data block that is attached to the element. It allows you to assign specific editor permissions for each data block.
  • A combination of element level and data block level. When using a combination, you set up a default data policy for all data blocks and data policy exceptions at data block level.

Required roles

Lead Designer

Setting up data policies

  1. In the sidebar menu, click Packages, and then click the model package in which you want to set up data policies.

  2. On the model package page, in the sidebar menu, click Policies. The Data policies page appears, showing a model tree containing all elements present in the model package.



  3. In the model tree, navigate to the element for which you want to set up data policies, and select it. The section for editing data policies appears on the right. This section is visible on each element in the model package, but policies can only be set for the elements that do have data blocks, as can be seen on the bottom part of the page.



  4. Depending on how you want to set up the data policies, continue with the appropriate procedures:


    Only set up a default data policy

    1. Setting up a default data policy

    Only set up data policies per data block
    1. Setting up data policies per data block

    Set up a default data policy and exception policies
    1. Setting up a default data policy
    2. Setting up data policies per data block as exception

Setting up a default data policy

  1. Under Default data policy, next to Default, click .



  2. In Editors, add one or more users or groups that must have editor permissions. When you start typing, the available names to select will appear. Only users and groups that have the Contributor role can be selected. Additional fields are added automatically.



  3. Click  to save the changes. The user(s) and/or group(s) that you have selected are now shown in the default policy as well as each data block policy:


You have now set up a default data policy that applies to all data blocks attached to the element. The individual data blocks inherit their data policy from the default data policy. If you want to specify exceptions to the default policy, continue with setting up data policies for data blocks that need an exception policy.

Setting up data policies per data block

If you only want to set up data policies at data block level, then perform the procedure below for each data block attached to the element that must have a data policy.

  1. As can be seen under Data policies per data block, the individual data blocks do not have a data policy. Click  next to a data block name to add a data policy.



  2. In Editors, add one or more users or groups that must have editor permissions. When you start typing, the available names to select will appear. Only users and groups that have the Contributor role can be selected. Additional fields are added automatically.



  3. Click  to save the changes. The user(s) and/or group(s) that you have selected are now the allowed editors for this specific data block:


When you are done, you have set up data policies for each data block that needs one. Any data blocks that do not have a policy will remain editable to all Contributor users with access to the sites these blocks are in (as is also indicated in the blue info box on the data policies page), unless you decide to set a strict data block write access.

If you want the values of a data block with a data policy to be periodically updated by users, you can add a data update schedule.

Setting up data policies per data block as exception

If you have set up a default data policy for all data blocks, then follow the procedure below to set up a policy for each data block that needs to be an exception on the default policy.

  1. As can be seen under Data policies per data block, all data blocks currently inherit their policy from the default data policy. Click  next to a data block name to change its policy.



  2. In Editors, make the desired changes to the data policy. You can add one or more users or groups that must have editor permissions, but also remove the current editor that is inherited from the default policy. When you start typing, the available names to select will appear. Only users and groups that have the Contributor role can be selected. Additional fields are added automatically. In the example below, the editor from the default policy has been removed and another editor has been added.


    Removing all editors from the data block policy means that the data block will not be editable by anyone. Although no editors are set, the policy will still be set (as will be indicated by the  label in the policy). This may be a conscious decision, but be aware of it.

    Also, if an editor has been set for the data block and this editor's contributor permissions are revoked, the editor will automatically be removed from the data block policy. If this was the only editor for the data block policy, it would leave the policy without an editor.

  3. Click  to save the changes. The user(s) and/or group(s) that you have selected are now the allowed editors for this specific data block.



When you are done, you have set up data policies for some of the individual data blocks. The data blocks for which you have not set a specific data policy will use the default data policy.

If you want the values of a data block with a data policy to be periodically updated by users, you can add a data update schedule.