Find your content:

Search form

You are here

Deploying Profiles / Permission Sets that include object & field permissions for Managed Objects


Anyone know if it's possible to deploy profiles/permission sets via Eclipse or an Unmanaged Package that contain object & field permissions for 3rd party managed objects?

I'm trying to deploy a profile from one org that contains object/field permissions for objects that are part of a managed package (not a package that I have access to, but that is from a 3rd party vendor).

The problem that I'm running into is that the profile/permission set XML files in eclipse don't even contain the object/field permissions for these managed objects, they only contain the object/field permissions for standard Salesforce objects & custom unmanaged objects.

I'm able to deploy the profiles/permissions sets to another org but only the premissions for standard & custom unmanaged objects get migrated... none of the permissions for the 3rd party managed objects move.

Attribution to: DallasDeuce

Possible Suggestion/Solution #1

This is possible, provided your package.xml is configured correctly. From the directions at

Using Field Trip as an example, in my package.xml:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="">

In the profile XML retrieved I see:


Attribution to: Mike Chale

Possible Suggestion/Solution #2

This is absolutely possible. What is not possible is to retrieve or deploy managed components like a managed permission set. These components are considered protected and immutable.

However, by retrieving the managed CustomObject member metadata along with your own custom profile/permission set metadata, as in @Mike Chale's example, you will have access to set permissions on your custom profile/permission set metadata.

Just go into your .Profile settings file in eclipse and modify the permissions. There should be no reason why this isn't possible deploying by eclipse but if you want to test this, try it out deploying using the utility - just go to migration >> deploy to deploy your custom zip file.

One way to think of it is: managed components are owned by the ISV/package publisher, but since custom profiles and permission sets in your org are owned by you, you can always modify them (as long as you include the publisher namespace prefix in your deployment) including managed component permissions.

Attribution to: Adam Torman
This content is remixed from stackoverflow or stackexchange. Please visit

My Block Status

My Block Content