Portal user actions must be approved by operators with authorization privileges. Portal user actions require approval by just one operator.

Only operators that did not perform the actions can approve the actions. In addition, if the action requires approval by two operators, a different operator must perform each approval level.

B2B Data Exchange does not send notifications for new pending operator actions. Operators can review pending actions in the

Authorization

page or in the

Dashboard

page.

If the B2B Data Exchange administrator defined that actions that operators perform on a partner do not require approval but actions that operators perform on the accounts of the partner require approval, when you create a partner with accounts B2B Data Exchange creates the partner and submits the request to create the accounts for approval. You can view or edit the accounts only after the approval of an operator with authorization privileges.

Only manual operator actions can require approval. If B2B Data Exchange receives an action on the object from the command line utilities or an API, B2B Data Exchange automatically accepts the action.

If an operator performs an action with an external API on an object that already contains a pending action before the pending action is approved, B2B Data Exchange prevents the approval of the pending action by cancelling the action request when an operator attempts to approve the action. This ensures that approval of the original action does not override more recent actions.

When an operator deletes an object with related objects, the approval for the parent object applies to all related objects even if the related objects require a different approval level. For example, if an operator with authorization privileges approves an action request to delete a partner with a profile that requires second level approval, B2B Data Exchange deletes that profile without requiring second level approval.