Skip to main content

Hello Early Adopters of Permission Set Group!

 

You might have already heard that Permission Set Group is rolling out Beta in Winter'20 release! Beta features will be available to orgs with Enterprise, Performance, Unlimited, and Developer editions without additional enablement need.

  • Enablement for pre-release orgs and early upgraded sandboxes are delayed to Sep 20th due to some release issues. 
    • Production orgs have access to the feature without additional enablement.
    • Majority of sandbox orgs require a refresh from upgraded production orgs to activate the feature 
    • Pre-release orgs sign up after Sep 20th have access to the feature without additional enablement. Pre-release orgs sign up before Sep 20th does not and will not have access to the feature. 

While we are excited that UI will better assist your admin testing and adopting the feature, please still keep in mind that it is Beta so things are not perfect! Here are highlights of functionalities not supported in Beta but we are looking to include in GA (safe harbor) 

  • UI to fully support managing permission muting (only system permissions and app permission is available in Beta)
  • Ensure "enabled" and "muted" status on muting page reflect the correct value
  • Auto assign required permission set license when assigning a group if the the group has a license-constrained permission set.
  • Fix issues with group list view (unstable routing and page loading has been observed) 

An important validation is added in Beta compared to Pilot 

  • Group requires unique muting permission set. If a muting permission set belongs to an existing group, it can not be assigned to a new group 

Your Salesforce Support program does not cover this Beta. However, this community will remain active to help you troubleshoot if any issues occurs. And your feedback about the Beta is always valuable to us for driving better future enhancement! 

14 件のコメント
  1. 2019年11月8日 21:20
    @Charles Troster This answer is long overdue but I can confirm now that when we GA the feature (safe harbor Spring'20), we will ensure all orgs with eligible editions get it enabled.
0/9000