Permission Sets: Allow standard object permissions to be packaged - Ideas - Salesforce Trailblazer Community
Trailblazer Community

All Ideas

Idea Details

Post an Idea
1,480  Points
Idea has been posted. Give it an upvote or downvote.

Permission Sets: Allow standard object permissions to be packaged

Operational Reporting

Our company is an ISV partner that sells a product on the platform.  We use Accounts and Contacts so that we can take advantage of the nice integrations that Salesforce provides out of the box.  We also have a few custom objects that have master-detail relationshipts with these objects.

We like to user permission sets to give people access to fields and objects.  Our product is simple and our customers don't required the field level security or object level security that the platform offers, so we use permission sets and assign the same one to each user.  This lets us also upgrade the permission sets with new releases and the end customers don't have to do anything.

Unfortunately, we cannot package up the 'Contact' or 'Account' permission sets, nor any of the child objects.  If we decide to change permissions on these objects (which we might do if we deprecate a field so it doesn't show up in reports and views), we have to either login and change the permissions on their profiles or else give them instructions, which is somewhat painful.  If we miss giving a field read permission, it sometimes causes our new features to break or just not be there.

If we could package these up, it would resolve issues and permission sets would be perfect for what we are trying to do and help us make sure our product works correctly without manual intervention.

Merge Idea · Flag

Latest Comment from Salesforce

  • Adam Torman - 4 years ago

    @Robert Kraynak - Belinda Wong owns the backlog for Permission Sets now. She'll need to comment on where this is on the backlog. 

    Two workaround options that I've seen:
    1. package lookup relationships to standard objects (it's master detail that aren't supported AFAIK)
    2. run post install script to enable the permissions via Apex
  • Upvotes
  • Downvotes



from AppExchange

Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.



Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.

Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.


Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.