---
schema_version: "1"
id: 4a5d9cdc5e491e06ef0ac32871b4230626057f37492d82af201941646ee8e4a4
title: UserAccessPolicy
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_tooling/tooling_api_objects_useraccesspolicy.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/tooling_api_objects_useraccesspolicy.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 769158768348a6aeb0a622c78ea3284f6357ed4ea518cdbf9a12c8d41dbacc2e
description: Represents a user access policy. This object is available in API version 57.0 and later.
---
# UserAccessPolicy

Represents a user access policy. This object is available in API version 57.0 and later.

![Important](https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/images/icon_note_important.png)

#### Important

Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.

## Supported SOAP API Calls

create(), delete(), describeSObjects(), query(), retrieve(), update() , upsert()

## Supported REST API Methods

GET, POST, PATCH, DELETE, HEAD, Query

## Special Access Rules

To create or modify user access policies, users must have the Manage User Access Policies permission.

## Fields

| Field | Details |
| --- | --- |
| BooleanFilter | 
Type

string

Properties

Filter, Group, Nillable, Sort

Description

Required. The logic that determines how your user criteria filters are applied in the user access policy. For instance, if you have two user access policy filters with the SortOrder equal to 1 and 2, respectively, the BooleanFilter can be 1 AND 2 or 1 OR 2.



 |
| Description | 

Type

textarea

Properties

Filter, Group, Nillable, Sort

Description

Description of the user access policy.



 |
| DeveloperName | 

Type

string

Properties

Filter, Group, Sort

Description

The unique name for the user access policy.

The unique name of the object in the API. This name can contain only underscores and alphanumeric characters, and must be unique in your org. It must begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores. In managed packages, this field prevents naming conflicts on package installations. With this field, a developer can change the object’s name in a managed package and the changes are reflected in a subscriber’s organization. Label is **Name**.

![Note](https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/images/icon_note.png)

#### Note

When creating large sets of data, always specify a unique DeveloperName for each record.















 |
| Language | 

Type

picklist

Properties

Filter, Group, Restricted picklist, Sort

Description

The language of the user access policy.



 |
| ManageableState | 

Type

ManageableState enumerated list

Properties

Filter, Group, Nillable, Restricted picklist, Sort

Description

Indicates the manageable state of the specified component that is contained in a package:

- beta
- deleted
- deprecated
- deprecatedEditable
- installed
- installedEditable
- released
- unmanaged





 |
| MasterLabel | 

Type

string

Properties

Filter, Group, Sort

Description

Label for the user access policy. In the UI, this field is Label.



 |
| NamespacePrefix | 

Type

string

Properties

Filter, Group, Nillable, Sort

Description

The namespace prefix associated with this object. Each Developer Edition organization that creates a managed package has a unique namespace prefix. Limit: 15 characters. You can refer to a component in a managed package by using the namespacePrefix\_\_componentName notation.

The namespace prefix can have one of the following values:

- In Developer Edition organizations, the namespace prefix is set to the namespace prefix of the organization for all objects that support it. There is an exception if an object is in an installed managed package. In that case, the object has the namespace prefix of the installed managed package. This field’s value is the namespace prefix of the Developer Edition organization of the package developer.
- In organizations that are not Developer Edition organizations, NamespacePrefix is only set for objects that are part of an installed managed package. There is no namespace prefix for all other objects.





 |
| Order | 

Type

int

Properties

Create, Filter, Group, Nillable, Sort, Update

Description

Indicates the order for which active policy is applied when a user meets the criteria for multiple policies. Must be an integer from 0 to 10,000. Only the active policy with the lowest Order value is applied. This field is required only if the Status field is set to Active.

Available in API version 61.0 and later.



 |
| Status | 

Type

picklist

Properties

Defaulted on create, Filter, Group, Nillable, Restricted picklist, Sort

Description

The status of the user access policy.

Possible values are:

- Active
- Completed
- Design
- Failed
- Migrate
- Testing
- Updating

The default value is Design. If you deploy a policy with a status of Active, the status is changed to Design. A Salesforce admin can then set the status to Active by automating the policy in Setup.



 |
| TriggerType | 

Type

picklist

Properties

Filter, Group, Nillable, Restricted picklist, Sort

Description

The type of user record trigger for which this user access policy runs.

Possible values are:

- Create—The user access policy runs when a user who matches the policy criteria is created.
- CreateAndUpdate—The user access policy runs when a user who matches the policy criteria is either created or updated.
- Update—The user access policy runs when a user who matches the policy criteria is updated.





 |

## Usage

For more information, see [User Access Policies](https://help.salesforce.com/s/articleView?id=platform.perm_user_access_policies.htm&type=5&language=en_US) in Salesforce Help.