---
sourceDocument: Brazil Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/application-development

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Test a ServiceNow Arc policy change

# Test a ServiceNow Arc policy change {#ariaid-title1}

Release version: Brazil  
Updated September 29, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Verify that a policy change works as intended before you apply it to all users.

## Before you begin

Create the policy with user criteria that cover only a test user.

Role required: sn_app_arc.admin

## About this task

The instance merges policies and sends only the result, so a mistake in a broadly scoped policy affects every user it covers at their next sync. Test with a scoped policy first.

## Procedure

1. Save the policy on the instance.
2. Sync the policy to the client.  
   Wait for the change to arrive, which happens in near real time, or ask the user to restart the sandbox from the Arc application on the client.
3. On the client, confirm the last policy sync time in SettingsAgent Sandbox.
4. Run the action you intended to control, and confirm that the policy handles it as expected.
5. Run an action that the change shouldn't affect, and confirm that it still works.  
   Testing both confirms that the rule is doing what you intend, not blocking actions for an unrelated reason.
6. Update the policy's user criteria to cover the users or groups it's meant for.
{#test-cowork-policy-change__steps-test-policy}

## Result

The policy change applies to its intended users at their next sync.

*[\>]: and then