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.

In the context of CentraSite Business UI, propagation of permissions means that the new permissions completely replace the old permissions; the new permissions are not merged with the old permissions. As an alternative, you can use a change-time policy containing the action Set Instance and Profile Permissions. With this action, you can choose whether the new permissions will be merged with the old permissions or will replace the old permissions. For details, see the CentraSite Developer’s Guide.

By default, the access level permissions that are assigned on an asset are implicitly propagated to these dependent assets. This behavior is activated when you mark the checkbox Propagate asset permissions in the asset's Advanced Settings. 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.

In addition to propagating permissions that control the access to an asset instance (as described above), 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 assets. 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 checkbox Propagate profile permissions in the asset's Advanced Settings.