Skip to main content
小组

Permission Set Group Product Feedback

This is a feature group for Permission Set Group, which allows you group permission sets based on user tasks for easier assignment. Join the group to 1. post your feedback about Permission Set Group 2. stay tuned for the latest update about the feature

I built my first Permission Set Group with a Muting Permission Set (woohoo!), but now my team is having trouble deploying it. We have a few deployment tools at our disposal, but none seem to pick up the field-level muting permissions that I put in place. According to Salesforce support, Muting Permission Sets are not deployable with changesets, either. Does anyone have any tricks for getting a Permission Set Group with a Muting Permission Set and all of the included permissions deployed?

8 个回答
  1. 3月13日 20:36

    I deployed the Muted Permission Set on it's own with Gearset, but I agree if you're not moving through deployment stages with different sandboxes then recreating in prod is probably the fastest.

0/9000

We have recently started making use of permission set groups for a new implementation and we did a bit of work around them. 

 

However  we realized that if you have a new permission set group along with corresponding test classes which test those permission set groups, being passed as part of same deployment package, the test classes fail with the below error : 

 

INVALID_CROSS_REFERENCE_KEY, You can only assign users to permission set groups that have the "Updated" status

 

This error comes when the permission set group doesn't exist in the target Org, which is exactly how it is going to be for us in production.

 

When we reached out to Salesforce support, they said it was by design & we would need to breakdown the package into 2 parts, one containing the permission set group and another containing the actual test class and remaining code. In todays, day and age, everything is automated. Just for the sake of using PSG, we cant take such a big and tedious job of breaking the package.

 

I cant digest the fact, test classes being so core to what salesforce does have been ignored and we have been presented with a functionality which cant be pushed to production without breaking the package because test classes don't support it ? Has anyone else had a similar issue with PSG ? 

3 个回答
  1. 2025年2月14日 15:51

    Was there any resolution to this issue?  

     

    We are going live next week and all our code is being validated against multiple mock sandboxes.  

     

    We did not face this in mock1  sandbox where we deployed the code with test class run. We ran the test classes after the code was deployed and they passed successfully. 

     

    However, I am facing the exact same issue when I try to validate our package in our mock sandbox2.  

     

    Please share your insights on how you tackled this situation. Splitting into two packages would be a nightmare for us. 

     

     

0/9000

We have some customer-specific requirements from our Experience users regarding page layouts, fields, etc. The dev team is saying we have to create separate Profiles for each company because Dynamic Forms doesn't work with Communities.

But that sounds like moving backwards so I have to assume some provision has been made for this use case.  @Cheryl Feldman, do you confirm that we can't use the dependencies of Dynamic page layouts for Experience users? If so, where should we begin this approach?

1 个回答
  1. Sushil Kumar (UKG) Forum Ambassador
    2024年9月21日 03:09
    You can vote for this idea - https://ideas.salesforce.com/s/idea/a0B8W00000GdbhOUAR/enable-dynamic-forms-dynamic-actions-for-the-communities-interface. Only other idea is building UI using LWC where you can conditionally hide/show fields. Having separate profiles per company would be too much overhead.
0/9000

Muting Permission Sets are currently unavailable for deployment with Change Sets or metadata deployment tools. This is core to the functionality of the permission set group and needs to be deployable to prevent inevitable human error. I created this idea.

 

Please upvote! Thanks so much!

https://ideas.salesforce.com/s/idea/a0B8W00000QNkD1UAL/deploying-muting-permissions-sets

0/9000

When looking at a permission set, there is currently no way to see the Permission Set Groups that have that permission set assigned to it. This seems like a very basic need for PSG functionality, so I've created an idea for this and wanted to share in case others feel the same and can help get traction for it. As it stands now, we have to rely on SOQL queries to get this information, unless anyone else has a magic way that I haven't found yet? 

 

Please upvote! Thank you!

https://ideas.salesforce.com/s/idea/a0B8W00000PIvVmUAL/show-the-permission-set-groups-that-a-permission-set-is-assigned-to

0/9000

When assigning a specific Perm Set Group to users, 2 x Permission Set Licenses are automatically assigned. However, when the same Perm Set Group is unassigned from the users, the system doesn't automatically remove the Permission Set Licenses from the user records.  

 

Is this a known limitation and how do we automate the removal of Permission Set Licenses that are part of a Perm Set Group? Appreciate any advice. Thank you.

4 个回答
  1. Andrew Russo (BACA Systems) Forum Ambassador
    2023年7月3日 14:12

    What if PSG A was assigned and granted the PSL and then PSG B was assigned which would have granted the psi however it didnt because the user already had one. Then PSG A was removed. Should the PSL be removed?

    (This is a hypothetical just showing some of the inner complexity of why it is functioning like it is)

0/9000

I have created a permission set group with a number of permission sets and would like to mute field level permissions for an object. I am able to create the muted perm, and the muted perm displays the muted field permissions, but the muted perm has no affect. I can mute at the object level and it takes affect, but it does not seem to be working at the field level. And the assigned profile I am testing with does not have access to the objects in the perm group. Any recommendation on this? Thank you!

3 个回答
  1. 2023年6月20日 21:37

    @Belinda Wong Thank you so much for asking that question and reaching out! Prior to this post, I checked the profile to make sure it did not have access. The profile did not have CRUD object access but had field level access. I removed all field level access and the muting perm for FLS worked!!!!! So I can mute at the object and field level.  

0/9000

I have created couple of permission sets and added them to a group. One of those permission set is added as a community member and permission set group is assigned to a user.

But it gives an error when user with permission set group is trying to login. It says, "No community access". It works well when a permission set is directly assigned to a user rather group.

 

Any idea, if permission set groups are working with communities. 

12 个回答
  1. 2023年5月5日 06:48
    @Geoff Saxby yes. Turns out this is working as expected. The user does not get the permission set and is thus not considered a member. For experience sites permission set groups will not work to provide membership at this time. I do not know if that is on the roadmap. We also had to revert back to using a permission set.
0/9000

Don't know if this is the right place for reporting bugs for new "Field-Level Security for Permission Sets During Field Creation (beta)" feature.

I found out that when you assign field permissions via object managers "Set Field-Level Security" button to a permission set, this permission is correctly set within the permission set. But when the permission set is used within a permission set group, the field permission is not rolled up to permission set groups combined permissions and therefore the user whom the permission set group is assigned has no access to the field

 

Case #43699969

4 个回答
  1. 2023年2月8日 08:55

    @Marcel Harinck nope still having the same issues. The only good thing is that when you assign field permissions in sandbox and they are not rolled up to permission set group and you deploy it, they will roll up. 

    Support Case ended up that Salesforce was happy that I opened one but nothing happened after that.

0/9000