An asset can have one or more dependent objects. For example, a Service asset can refer to a WSDL which in turn can refer to one or more XML Schema assets. You can optionally choose whether the permissions assigned to an asset instance should be automatically propagated to the asset instance's dependent objects.

The access level permissions that are assigned on an asset are implicitly propagated to these dependent objects. This behavior is activated when you select the check box Propagate permissions to dependent objects in the asset's Permissions tab. For example, assigning Modify permission on a Service asset propagates the Modify permission to the asset's WSDL, schemas, and so on.

If you do not have permission to assign instance-level permissions to a dependent object, the dependent object will not be modified and a warning message will be issued.

You can propagate permissions only for the following asset types:

In addition to propagating permissions that control the access to an asset instance, it is also possible to propagate permissions that control the access to the asset instance's profiles. This means that the profile permissions that you define for an asset instance can be propagated to the asset's dependent objects. However, this is only possible if the dependent object is of the same asset type as the first object; this restriction arises because different asset types can have different sets of profiles.

This behavior is activated when you mark the check box Propagate profile permissions in the asset's Permissions tab. This check box is only available for the following asset types: