The Design/Change-Time Policy Used for Consumer Registration
The enhanced consumer registration functionality enables the consumer registration process without explicitly creating a consumer-registration policy, and also completes the consumer registration process without requiring the owner of the asset to review and accept the user's request.
If you want to impose an approval process on consumer registration, that is, control which consumers can invoke an asset, you can create a design-time policy with one of the CentraSite’s built-in approval actions for the OnConsumerRegistration event. For example, you can create a design-time policy, named Consumer-Registration Policy, which requires a designated group of approvers to review and approve all consumer requests for invoking the asset. Upon reviewing, the approvers may approve or reject such requests.
For more information about creating the Consumer-Registration Policy, refer to the section “Using Approvals with OnConsumerRegistration Events” in the CentraSite User’s Guide.
When you register as consumers of an asset, the policy is triggered and the “Register as Consumer” request is submitted to all members of the approval list specified in the Initiate Approval action. Then, the approvers can either approve or decline the request. If the approvers approve the request, the consumers will be registered as consumers for the asset. Consider, you have configured the Set Consumer Permission action in this policy; CentraSite assigns the appropriate permissions to the specified set of users, groups and arbitrary assets.