When data block definitions have been created, their 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 by all Contributors with access to the site (unless write access is limited). The data blocks can be viewed by any Consumer user.

Using data policies allow you to:

  • Limit data block editing for Contributor users by assigning editors.
  • Enable Contributor users to edit data blocks on the model Contribute page.
  • Set up data maintenance for data blocks.
  • Hide data block information from users by assigning readers.

The Contribute page shows all elements with data blocks within the model the Contributor user is able to edit. The user does not need to visit the pages in sites to edit the data blocks. This user doesn't need access to sites to be able to edit the data blocks.

Data policy configuration possibilities

Data policies are defined in Horizzon, in a model package containing elements with data blocks. Currently, data policies can be set for individual diagrams, views, objects, and relations. The following options are available 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 and reader 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 and reader 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.

Configuring data policies using the Bizzdesign Open API

In addition to directly managing the data policies in Horizzon, it is also possible to manage them using the Bizzdesign Open API. This includes assigning editors and readers to data blocks as well as setting up data update schedules for data blocks.


The procedures below describe setting up data policies when using open data block write access and when using strict data block access, and their effect on the policies and users. To be able to set up data policies for data blocks in a model package you need to be invited to the model package.

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 Policies page appears in which you can set up object policies and data policies. The Object policies tab is shown.



  3. Click the Data policies tab. The model package tree on the left shows the contents of the model package.


    If you prefer to view the model package content in a different language than is currently shown, you can change the model language, provided that the model package has more than one language available.

  4. In the tree, navigate to the element for which you want to set up data policies, and select it. It can be an element from an Enterprise Studio model in the package but also one from external models ("Collections"), if available in the model package.

    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 elements that do have data blocks. Any data blocks will be shown below the default data policy.

    Strict data block write access
    If data block write access is set to "Strict" for the model package, the data blocks cannot be edited by any Contributor user via sites as long as they have no editors assigned. If the data blocks have no readers assigned, they are always visible to all Consumer users via sites.



    Open data block write access
    If data block write access is set to "Open" for the model package, the data blocks can be edited by all Contributor users via sites as long as they have no editors or readers assigned. If the data blocks have no readers assigned, they are always visible to all Consumer users via sites.



  5. Depending on how you want to set up the data policies for the element, continue with the appropriate procedure(s):


    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

If you set up a default data policy for all data blocks attached to the element, you assign editor and reader permissions that apply to all data blocks of the element.

  1. Under Default data policy, next to Default, click , and add editors and/or readers to set up the data policy. You can add up to eight users and groups as editor and as reader for the default policy.

    When you start typing a name, the available names to select will appear. Only users and groups that have the Contributor role can be selected as editor, only users and groups that have the Consumer role can be selected as reader. Once a user or group has been selected, it is no longer available to add to the default policy.



    Editors
    Set editors if you want to add users and groups that must be able to edit the data blocks available on the element. They will be able to edit them via sites and via the model Contribute page.

    If you set only editors and no readers, other Contributor users will not be able to edit the data blocks, they can only view them via sites. The data blocks can also be viewed by Consumer users via sites.

    If you also set readers, only these readers and the editors that have been set will be able to view the data blocks.

    Readers
    Set readers if you want the data blocks only to be visible to specific users and groups.

    If you set only readers and no editors, only these readers will be able to view the data blocks via sites. Other Consumer users and all Contributor users will not be able to view the data blocks via sites.



    According to the above example, only Annie, John, and Jane will be able to view all data blocks of the element. John and Jane will also be able to edit the data blocks.

  2. Click to save the changes. If you have set readers and this is the first time for the data block definition of the data block for which you set up the data policy, then subsequently click Confirm in the message that pops up.

    Setting readers is brought to your attention explicitly because assigning readers has
    effects and consequences when using the values of data blocks with assigned readers in Enterprise Studio. You should be aware of that.

    The users and groups that you have selected are now shown in the default policy as well as each individual data block policies below it.



You have now set up a default data policy that applies to all data blocks available on 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, perform the procedure below for each data block available on the element for which you want to set up a data policy. You can also choose to leave data blocks without a data policy, if desired.

  1. As can be seen under Data policies per data block, there are no data policies for the individual data blocks, not individually set, nor inherited from a default policy. Click next to a data block name and add editors and/or readers to set up a data policy. You can add up to eight users and groups as editor and as reader.

    When you start typing a name, the available names to select will appear. Only users and groups that have the Contributor role can be selected as editor, only users and groups that have the Consumer role can be selected as reader. Once a user or group has been selected, it is no longer available to add to the policy of the data block.



    Editors
    Set editors if you want to add users and groups that must be able to edit this data block. They will be able to edit the data block via sites and via the model Contribute page.

    If you set only editors and no readers, other Contributor users will not be able to edit the data block, they can only view it via sites. The data block can also be viewed by Consumer users via sites.

    If you also set readers, only these readers and the editors that have been set will be able to view the data block.


    Readers
    Set readers if you want this data block only to be visible to specific users and groups.

    If you set only readers and no editors, only these readers will be able to view the data block via sites. Other Consumer users and all Contributor users will not be able to view the data block via sites.



    According to the above example, only Annie, John, and Jane will be able to view the data block. John and Jane will also be able to edit the data block.

  2. Click  to save the changes. If you have set readers and this is the first time for the data block definition of the data block for which you set up the data policy, then subsequently click Confirm in the message that pops up.

    Setting readers is brought to your attention explicitly because assigning readers has
    effects and consequences when using the values of data blocks with assigned readers in Enterprise Studio. You should be aware of that.

    The users and groups that you have selected are now shown in the data policy of the individual data block. As can be seen in the example below, a data policy has been set for only one data block. The other data block has no data policy. Also, the data block write access of the model package is set to strict (blue info box). This means that data block "Application costs" can be edited and viewed according to the data policy that has been set up, and that data block "Application quality" cannot be edited by any Contributor user via sites, it can only be viewed. The data block is also visible to all Consumer users via sites.



When you are done, you have set up a data policy for each data block that needs its own policy. The data blocks that do not have a policy will remain visible to all Consumer users. They will also remain editable to all Contributor users with access to the sites these blocks are in, unless you have 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

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

  1. As can be seen under Data policies per data block, all data blocks currently inherit their policy configuration from the default data policy. Click next to the name of the data block for which you want to change the policy, and make the desired changes to the editors and/or readers.

    When you start typing a name, the available names to select will appear. Only users and groups that have the Contributor role can be selected as editor, only users and groups that have the Consumer role can be selected as reader. Once a user or group has been selected, it is no longer available to add to the policy.



    If you want different editors and/or readers for this particular data block, change the names. If you want no editors or readers at all, remove the names, but please be aware of the effects. See the note below for more information.

    If you set editors as well as readers, only these editors will be able to edit the data block via sites and via the model Contribute page. Only the readers that have been set will be able to view the data block.

    If you set only editors and no readers, only these editors will be able to edit this data block via sites and via the model Contribute page. Other Contributor users will not be able to edit the data block, they can only view it via sites. No Consumer user will be able to view the data block via sites.

    If you set only readers and no editors, only these readers will be able to view the data block via sites. Other Consumer users and all Contributor users will not be able to view the data block via sites.

    Removing all editors from an individual data block policy means that the data block will not be editable by any Contributor user. When removing al readers, no Consumer user will be able to view the data block. Although no editors or readers are set, the data policy will still be considered as set, as will be indicated by the label in the policy. This may be a conscious decision, but be aware of it. You cannot loosen the permissions for a particular data block. In that case, you should not set a default policy, but set data policies per data block and only restrict the permissions for the data blocks that need it.

    If an editor has been set for a data block policy 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 will leave the policy without an editor.




    In the above example, editor "John" has been removed and all readers have been removed. As a result of this, no Consumer user will be able to view the "Application costs" data block and only editor "Jane" will be able to edit this data block. Other Contributor users, including user "John", will only be able to view the data block. The other individual data block "Application quality" will still follow the default data policy.

  2. Click to save the changes. The editors and readers that you have selected are now shown in the data policy of the individual data block.



When you are done setting up data policies for one or more individual data blocks, these policies will override the default policy. Any data blocks for which you have not set a data policy will follow 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.