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


---

# Segment policies

# Segment policies {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Segment policies enable broad access patterns across one or more Application Runtime Policy segment without requiring granular policy records for each access. If your application requires segment policies, you must create them
manually.

Segment policies provide a declarative way to enable broad categories of access. For example, rather than creating individual policy records for every external network call, you can create a single segment policy. This segment policy covers a certain type of access that will be allowed without a granular policy record.

When you activate a segment policy with one or more wildcard policies, ARP doesn't create individual policy records for access attempts covered by those wildcard policies. Access is granted without requiring per-resource
approval.

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. For more information about activating segment policies, see [Create a segment policy](https://www.servicenow.com/docs/uiOreGUMxF555rbLXrj~Hw "Create a segment policy to enable broad access to one or more policy categories without requiring individual policy records for each access attempt.").