UserAccessPolicy (Beta) | Tooling API

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.

Important

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.

This feature is a Beta Service. Customer may opt to try such Beta Service in its sole discretion. Any use of the Beta Service is subject to the applicable Beta Services Terms provided at Agreements and Terms.

Note

Fields

Field	Details
BooleanFilter	Type string Properties Create, Filter, Group, Nillable, Sort, Update 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`.
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. When creating large sets of data, always specify a unique DeveloperName for each record. Note
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.
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`.

Usage

For more information, see User Access Policies (Beta) in Salesforce Help.