MutingPermissionSet (Beta)

Represents a set of disabled permissions and is used in conjunction with PermissionSetGroup (Beta). This object is available in API version 46.0 and later.

As a beta feature, MutingPermissionSet is a preview and isn’t part of the “Services” under your master subscription agreement with Salesforce. Use this feature at your sole discretion, and make your purchase decisions only on the basis of generally available products and features. Salesforce doesn’t guarantee general availability of this feature within any particular time frame or at all, and we can discontinue it at any time. This feature is for evaluation purposes only, not for production use. It’s offered as is and isn’t supported, and Salesforce has no liability for any harm or damage arising out of or in connection with it. All restrictions, Salesforce reservation of rights, obligations concerning the Services, and terms for related Non-Salesforce Applications and Content apply equally to your use of this feature. You can provide feedback and suggestions for MutingPermissionSet in the Trailblazer Community.

Note

Use a muting permission set with a permission set group to mute certain permissions. For instance, you have a subscriber org using a managed package that contains a permission set group. To use the existing permission set group, the subscriber org can disable specific permissions with a muting permission set. Or, perhaps you have a permission set group that contains several permission sets managed by different departments. Use a muting permission set to disable specific permissions based on your organization's needs.

Supported Calls

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

Fields

Field Name	Details
DeveloperName	Type string Properties Create, Filter, Group, Sort, Update Description 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. When creating large sets of data, always specify a unique DeveloperName for each record. If no DeveloperName is specified, performance may slow while Salesforce generates one for each record. Note
Language	Type string Properties Create, Defaulted on create, Filter, Group, Nillable, Restricted picklist, Sort, Update Description The language of the muting permission set. Possible values are: `da` (Danish) `de` (German) `en_US` (English) `es` (Spanish) `es_MX` (Spanish - Mexican) `fi` (Finnish) `fr` (French) `it` (Italian) `ja` (Japanese) `ko` (Korean) `nl_NL` (Dutch) `no` (Norwegian) `pt_BR` (Portuguese - Brazilian) `ru` (Russian) `sv` (Swedish) `th` (Thai) `zh_CN` (Chinese - Simplified) `zh_TW` (Chinese - Traditional)
MasterLabel	Type string Properties Create, Filter, Group, Sort, Update Description The muting permission set label for the aggregated, disabled permissions.

Usage

Use MutingPermissionSet to disable specified permissions within a permission set group.

Object Reference for Salesforce and Lightning Platform

MutingPermissionSet (Beta)

Supported Calls

Fields

Usage