---
schema_version: "1"
id: 4acc9dcce732fb10a12c2617c8350f937c2e3edc17df88284f8d5a8a11a25e60
title: MutingPermissionSet
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_mutingpermissionset.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_mutingpermissionset.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 217e87489a9df316f3e75dc49adf8291beabea9efa4bb80e824e4b7bbadb9c2a
description: Represents a set of disabled permissions and is used in conjunction with PermissionSetGroup.
---
# MutingPermissionSet

Represents a set of disabled permissions and is used in conjunction with [PermissionSetGroup](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_permissionsetgroup.htm "Represents a group of permission sets and the permissions within them. Use permission set groups to organize permissions based on job functions or tasks. Then, you can package the groups as needed.").

This type extends the [PermissionSet](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_permissionset.htm "Represents a set of permissions that's used to grant more access to one or more users without changing their profile or reassigning profiles. You can use permission sets to grant access but not to deny access.") metadata type.

## Declarative Metadata File Suffix and Directory Location

Muting permission sets are stored in the mutingpermissionsets directory. The file name matches the muting permission set API name and the extension is .mutingpermissionset. For example, a mutingpermissionsets with the name Finance\_Mgmt\_MutingPermSet is stored in mutingpermissionsets/Finance\_Mgmt\_MutingPermSet.mutingpermissionset.

## Version

This object is available in API version 46.0 and later.

## Special Access Rules

As of Summer ’20 and later, only users who have one of these permissions can access this type:

- View Setup and Configuration
- Manage Session Permission Set Activations
- Assign Permission Sets
- Manage Profiles and Permission Sets

To view the following settings, assignments, and permissions for standard and custom objects in a specified muting permission set, the View Setup and Configuration permission is required.

- Client settings
- Field permissions
- Layout assignments
- Object permissions
- Permission dependencies
- Permission set tab settings
- Permission set group components
- Record types

## Fields

MutingPermissionSet has the same fields as [PermissionSet](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_permissionset.htm "Represents a set of permissions that's used to grant more access to one or more users without changing their profile or reassigning profiles. You can use permission sets to grant access but not to deny access."), plus a single field, label, used to name a MutingPermissionSet. Unlike PermissionSet, settings enabled by MutingPermissionSet are turned off for the permission set group that it’s a component of.

| Field | Field Type | Description |
| --- | --- | --- |
| label | string | Required. The name of the muting permission set. |

## Declarative Metadata Sample Definition

The following example deploys a MutingPermissionSet used in a Permission Set Group intended for users submitting job applications for a custom application. The muting permission set has administrative permissions enabled to ensure that they’re muted in the Permission Set Group.

<?xml version="1.0" encoding="UTF-8"?>
<MutingPermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">
    <label\>Job Apps User Muted</label\>
    <description\>Mutes any administrative tasks for the Job Apps user</description\>
    <hasActivationRequired\>false</hasActivationRequired\>
    <license\>Salesforce</license\>
    <applicationVisibilities\>
        <application\>JobApps\_\_Approval</application\>
        <visible\>true</visible\>
    </applicationVisibilities\>
    <classAccesses\>
        <apexClass\>ApprovalUtility</apexClass\>
        <enabled\>true</enabled\>
    </classAccesses\>
    <customPermissions\>
        <enabled\>true</enabled\>
        <name\>JobAppApprover</name\>
    </customPermissions\>
    <fieldPermissions\>
        <editable\>false</editable\>
        <field\>Job\_Request\_\_c.Salary\_\_c</field\>
        <readable\>true</readable\>
    </fieldPermissions\>
    <objectPermissions\>
        <allowCreate\>true</allowCreate\>
        <allowDelete\>true</allowDelete\>
        <allowEdit\>true</allowEdit\>
        <allowRead\>true</allowRead\>
        <customizeSetup\>true</customizeSetup\>
        <deleteSetup\>true</deleteSetup\>
        <modifyAllRecords\>true</modifyAllRecords\>
        <object\>Approval\_Confirmation\_\_c</object\>
        <viewAllRecords\>true</viewAllRecords\>
        <viewSetup\>true</viewSetup\>
    </objectPermissions\>
    <pageAccesses\>
        <apexPage\>Job\_Approval\_Web\_Form</apexPage\>
        <enabled\>true</enabled\>
    </pageAccesses\>
    <recordTypeVisibilities\>
        <recordType\>Approval\_Confirmation\_\_c.DevManager</recordType\>
        <visible\>true</visible\>
    </recordTypeVisibilities\>
    <tabSettings\>
        <tab\>Approval\_Confirmation\_\_c</tab\>
        <visibility\>Visible</visibility\>
    </tabSettings\>
</MutingPermissionSet\>

The following is an example package.xml manifest used to retrieve the MutingPermissionSet metadata for an organization.

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types\>
        <members\>Job\_Apps\_User</members\>
        <name\>PermissionSetGroup</name\>
    </types\>
    <types\>
        <members\>Job\_Apps\_User\_Muted</members\>
        <name\>MutingPermissionSet</name\>
    </types\>
    <version\>49.0</version\>
</Package\>

## Wildcard Support in the Manifest File

This metadata type supports the wildcard character \* (asterisk) in the package.xml manifest file. For information about using the manifest file, see [Deploying and Retrieving Metadata with the Zip File](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_meta.meta/api_meta/file_based_zip_file.htm).

#### See Also

- [PermissionSet](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_permissionset.htm "Represents a set of permissions that's used to grant more access to one or more users without changing their profile or reassigning profiles. You can use permission sets to grant access but not to deny access.")