Creare e gestire criteri di approvazione approval-policies

AI Knowledge Reference

This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.

For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.

• TL;DR: This page explains how administrators create, set conditions for, activate, and manage approval policies that determine which journeys and campaigns require sign-off before they go live.

Intents:

• Create an approval policy from Administration > Permissions > Policies and scope it to Journeys or Campaigns
• Enable Block self-approval to prevent creators from approving their own objects
• Define conditions under the If menu that determine which object or user triggers an approval request
• Define who validates the request under the Then, send approval request to menu, choosing a User Group or an individual User
• Combine multiple conditions using the And or Or operators
• Activate, edit, deactivate, or duplicate an approval policy

Glossary:

• Approval policy: A validation process configured by administrators that determines whether a journey or campaign requires approval before activation. (product-specific)
• Block self-approval: An option that prevents Journey/Campaign creators from approving their own objects. (product-specific)
• Condition: A rule, built from a Category, Matching Rule, and Options, that defines which object or user triggers an approval request. (product-specific)
• Category: The type of criterion a condition targets — for example Campaign type, Action, Tags, Object name, Requestor username, or Requestor user group.

Guardrails:

• To create approval policies, you must have system or product administrator privileges in Adobe Experience Platform.
• Once activated, policies cannot be edited; to modify conditions, deactivate the policy first (hard limit — page states policies “cannot be edited”).
• A policy applies either to Journeys or to Campaigns, selected per policy.

Terminology:

• Canonical name: Approval policy — variants: approval policies
• Do not confuse: “If” (condition defining which object or user triggers an approval request) ≠ “Then, send approval request to” (defining who can validate the request)
• Do not confuse: “Activate” (apply a policy) ≠ “Deactivate” (required before editing) ≠ “Duplicate” (copy a policy)
• Do not confuse: “Requestor username” (name and email address of a designated requestor) ≠ “Requestor user group” (name of the user group of designated requestors)

FAQ:

• Q: Where do I create an approval policy? — From the Administration menu, access Permissions then Policies, click Create in the Approval Policy tab, choose Approval Policy, and confirm.
• Q: Can I edit a policy after activating it? — No. Once activated, policies cannot be edited. Deactivate the policy first to modify its conditions.
• Q: What criteria can target an approval policy? — Campaign/Journey names, Tags, Channel types, Campaign types, and Requestors.
• Q: How do I stop users from approving their own work? — Enable the Block self-approval option when creating the policy.