Visibility of Objects

This article explains the concept of Visibility for Dalet Flex objects. It explains how visibilty is set and how it is used to manage the availability of objects and which users can use them.

Introduction

The visibility of an object in Flex indicates whether it is available to a user who logs in to an account or sub-account. In combination with Role permissions, visibility is used to manage who can view, edit and use objects in Dalet Flex. Visibility can be set for an Account/Sub-Account and for Groups.

The availability of an object is based on the Account the object is created in and the Visibility assigned to it. Visibility influences whether assets, workflow, users, actions, resources etc:

• Can be seen in the account you login to
• Are available for use in the account for example in configuration screens, workflows etc
• Can be selected as values for metadata fields
• Can be used by a user in a particular Group

Setting Visibility

The visibility of an object in Dalet Flex is set when the object is created.

Visibility for Accounts/Sub-Accounts

For example, you can set the visibility of an Action.

You can set the visibility of a variant.

Visibility for Groups

In the drop-down list, you can set the visibility of some objects to Groups. This controls which users can use the object.

Visibility Hierarchy

Accounts in Dalet Flex are hierarchical: Master Account, Account, Sub-Account and Dalet Flex supports hierarchical visibility upwards and downwards between the accounts in an environment.

For example, in these Accounts, visibility supports availability of objects as shown in the table.

MasterAccount –type Master Account

Account1 – type Account

SubAccount1 - type Account and is child of Account1

Account2 - type Account

SubAccount2 - type Account and is child of Account2

Upward Visibility means

If you login to a Master Account you can see all the objects created on the Master Account.

If you login to an Account, you can see all the objects created on the Account you logged in to and on the Master Account.

If you login to a Sub-Account, you can see all the objects created on the Sub-Account you logged in to and all the objects created on the Parent Account and on the Master Account.

Downard Visibility means

If you login to a Master Account you can see all the objects created on the Master Account and all the objects on all the Accounts/Sub-Accounts under the Master Account.

If you login to an Account, you can see all the objects created on the Account you logged in to and all the objects on all its Sub-Accounts.

If you login to a Sub-Account, you can see all the objects created on the Sub-Account you logged in to.

Upward and Downward visibility combines these properties.

Important Notes

- Every object has two Properties: Account and Visibility. The Account property sets the level of ownership of the object. The Visibility property sets the level of availability of the object, if applicable (not all objects support visibility).

- Visibility of an object also depends on the permission and workspace access that the user has for objects.

- To edit the Visibility property of an object, the object must be disabled. 

- You can edit the properties of objects created at the level of the account you logged in to. 

- You can edit the properties of objects created on accounts level below the level you logged in to.

- You cannot edit the properties of objects created with an Account property on a higher level than the account you logged in to even if the object has visibility for the account you logged in to.

- There is no visibility of objects between sibling accounts or sibling sub-accounts

Example 1

This action has been created on Master Account with visibility Master Account.

The action has Upward and Downward availability and is visible on Master Account, all Accounts and all Sub-Accounts in Master Account.

The action can only be modified in Master Account.

Example 2

This action has been created on dineshkanna Account with visibility dineshkanna Account.

The action has Upward and Downward availability and is visible on Master Account, dineskanna Account and all Sub-Accounts in dineshkanna account. It is not visible on any other sibling Accounts/Sub-Accounts under Master Account.

The action can be modified in dineshkanna Account and in Master Account.

Example 3

This action has been created on Master Account with visibility dineshkanna.

The action has Upward and Downward availability and is visible on Master Account, dineskanna Account and all Sub-Accounts in dineshkanna account. It is not visible on any other sibling Accounts/Sub-Accounts under Master Account.

The action can only be modified in Master Account. You cannot edit objects created with an Account property higher level than the account you logged in to even if the object has visibility for the account you logged in to.

Example 4

This action has been created on dineshkanna Account with visibility all members Group.

The action has Upward and Downward availability and is visible to all users on Master Account, dineskanna Account and all Sub-Accounts in dineshkanna account. It is not visible on any other sibling Accounts/Sub-Accounts under Master Account.

The action can only be used in a workflow or run against an asset by members of the all members Group.

Tags, Taxonomy, Thesaurus

These object types do not support visibility and are only visible and available in the Account level they are created at.

Special Cases

Storage Resource/Folder Resource/Hot Folder Resource/CDN Resources are only visible and available in drop down lists for use in actions/workflows on Accounts they have Visibility for. This means that Storage Resource/Folder Resource/Hot Folder Resource/CDN Resources created on Master Account are NOT visible and available in drop down lists for use in actions/workflows on Accounts they DO NOT have visibility for even though are displayed in the Desktop of Accounts and Sub-Accounts.

UDOT Visibility

User Defined Object Type (UDOT) has downwards visibility with regards the listings in the GUI.

UDOTs have upward visibility with regards creating a User Defined Object (UDO) from a UDOT.

In other words, the + drop down list only displays UDOTs that are created on the account you are logged into and above. 

This means that you cannot create a UDO from a UDOT that is created on a lower level. 

For example, create a UDOT, called udotest, on a sub-account.

Login to the parent account,. In the + drop down list to create a UDO, the UDOT created on the sub-account, udotest, is not available in the + drop down list to create a UDO from..