<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Monitor Delivery and Withdrawal on</title><link>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/usage/delivery/</link><description>Recent content in Monitor Delivery and Withdrawal on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/usage/delivery/index.xml" rel="self" type="application/rss+xml"/><item><title>Verify Data Delivery Evidence</title><link>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/usage/delivery/verify_data/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/usage/delivery/verify_data/</guid><description>&lt;p>Verify Data protection after an authorized approver creates a governed revision.&lt;/p>
&lt;h2 id="before-you-begin">Before You Begin&lt;/h2>
&lt;p>Complete these prerequisites before verifying Data delivery:&lt;/p>
&lt;ul>
&lt;li>Confirm permitted policy visibility.&lt;/li>
&lt;li>Arrange an operator with &lt;code>policy:audit&lt;/code> to inspect restricted deployment diagnostics.&lt;/li>
&lt;li>Ask the Traverse integration administrator which tables or columns the approved policy should protect.&lt;/li>
&lt;/ul>
&lt;p>Expected locations are the data locations that compilation of the governed revision identifies for protection.
They are not every discovered location or the selections in a newer draft.&lt;/p></description></item><item><title>Verify Federated Guardrails Delivery Evidence</title><link>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/usage/delivery/verify_guardrails/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/usage/delivery/verify_guardrails/</guid><description>&lt;p>Verify Federated Guardrails delivery after approval.&lt;/p>
&lt;h2 id="before-you-begin">Before You Begin&lt;/h2>
&lt;p>Complete these prerequisites before verifying Guardrails delivery:&lt;/p>
&lt;ul>
&lt;li>Prepare the policy identifier and current governed revision.&lt;/li>
&lt;li>Ask the Guardrails administrator whether retrieval uses anonymous compatibility or a named consumer account.&lt;/li>
&lt;li>Confirm the deployment&amp;rsquo;s &lt;code>apiService.environment.GUARDRAILS_CONSUMER_USERNAME&lt;/code> value with its configuration owner.&lt;/li>
&lt;li>Arrange an operator with &lt;code>policy:audit&lt;/code> to inspect restricted Operations details.&lt;/li>
&lt;/ul>
&lt;p>A receipt records that consumer&amp;rsquo;s retrieval of the generated configuration.
It does not confirm that Guardrails has started applying the configuration to requests.&lt;/p></description></item><item><title>Inspect Delivery Issues and Verify Withdrawal</title><link>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/usage/delivery/issues_withdrawal/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/usage/delivery/issues_withdrawal/</guid><description>&lt;p>Use this task when publication fails or an archived policy remains Archiving.
Each delivery request has a &lt;code>generation&lt;/code> number. Retries reuse the configuration saved for that request.
Restricted operation inspection requires &lt;code>policy:audit&lt;/code>.&lt;/p>
&lt;h2 id="before-you-begin">Before You Begin&lt;/h2>
&lt;p>Complete these prerequisites before investigating delivery:&lt;/p>
&lt;ul>
&lt;li>Retain the policy identifier and visible error.&lt;/li>
&lt;li>Confirm audit capability before following Operations directions.
Otherwise, give this task to your Policy administrator.&lt;/li>
&lt;li>Confirm &lt;code>policy:approve&lt;/code> for publication retry or &lt;code>policy:archive&lt;/code> for withdrawal retry.
Audit access alone does not permit either command.&lt;/li>
&lt;/ul>
&lt;h2 id="inspect-before-retry">Inspect Before Retry&lt;/h2>
&lt;p>To inspect a failed delivery before retrying, follow these steps:&lt;/p></description></item></channel></rss>