---
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


---

# Create a segment policy

# Create a segment policy {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Create a segment policy to enable broad access to one or more policy categories without requiring individual policy records for each access attempt.

## Before you begin

* You must be in the scope of the application you want to create a segment policy for. For more information about changing application scope, see [Application picker](https://www.servicenow.com/docs/lOHlADMY5P4L9URiY5NlaA "The application picker enables application developers to view and select the application scope where their changes apply.").
* The application must be in development.
* Application Runtime Policy (ARP) must be activated in either Tracking or Enforcing mode for the selected application scope.
{#create-segment-policy-arp__ul_spf_k1g_wjc}

Role required: arp_admin or admin.

## About this task

Segment policies provide a way to enable broad categories of allowed access to an application in development. Activating a segment policy for an area suppresses the creation of individual policy records via ARP for that area. If
granular visibility into access patterns is needed for certification or review purposes, use individual policy records instead.

Because they provide such broad resource access, only use segment policies when out-of-scope resources called at runtime can't be known during application development.

## Procedure

1. Navigate to AllSystem PoliciesApplication Runtime PolicySegment Policies.
2. Verify that you're in the correct scope for the application you want to create a segment policy for.  
   For more information, see [Application picker](https://www.servicenow.com/docs/lOHlADMY5P4L9URiY5NlaA "The application picker enables application developers to view and select the application scope where their changes apply.").
3. Select New.
4. Select the Active option to enable segment policy at creation.
5. In the Short Description field, enter a description of the policy.
6. In the Wildcard Policies section, select the categories for which you want to enable broad access.

   | Option | Description |
   | Network | Covers external network access. |
   | Scripting | Covers cross-scope script access. |
   | ARL | Covers application resource limits, including transaction event and scheduled job quotas. |
   | Record | Covers cross-scope table access. There are no additional wildcard options for this category. |
   |-|-|

   {#create-segment-policy-arp__choicetable_twt_png_wjc}
7. Within each selected category, select the Unlock Wildcard icon ![]().
8. Select one or more wildcard options from the drop-down menu to specify sub-categories of unrestricted resource access.  
   Select individual wildcards or select all wildcards to cover all subcategories. For more information about wildcard options for each category, see [Wildcard Policies options](https://www.servicenow.com/docs/F4Dunr0MoRrwck7SkHmDbQ "When using a segment policy to enable broad access permissions by category, wildcard options for each category further specify which kinds of access are permitted.").
9. Select Submit.

## Result

The segment policy is created and activated. ARP no longer creates individual policy records for access attempts in the selected categories. Existing individual policy records for those categories can be deleted. Application
functionality that relies on the covered categories continues to work without per-resource policy approval.

## Creating a segment policy with wildcard options {#create-segment-policy-arp__example_kfd_ksw_bkc}

*[\>]: and then