Restricting Visibility of Component Using Custom Permission Not Working

Question

I am trying to restrict the visibility of a managed package component that is deployed as a tab on an Account record. I have created the permission set and included a custom permission in that permission set and in the App builder created a filter to restrict visibility to anyone that does not have that permission set assigned (ie I see the custom permission and set that it must equal true to view the component).

It works in my Dev Org and the tab is hidden if the user does not have the correct permission set assigned. Once packaged, I see all of these items (permission set, custom permission, and the custom permission assigned to the permission set) in a package installed in a Professional Edition test org abd set the filter just as I did in the Dev Org. But the result is different in that all users can see the tab where the component is deployed regardless of being assigned the permission set or not. Any ideas why this is occurring. Am I missing something that needs to be done once it is packaged?

Answer 1

I figured out the problem if not the solution. When the package is installed, all components are enabled for all Profiles, which defeats the purpose of Permission Sets since the proifiles grant permission that I am trying to limit to only certain users through the permission sets. In another post (Limiting Custom Component Access in Managed Package) it was suggested that this happens on install of the package when the installer chooses to "Install for All Users". I will test and update the other post with the results of testing this.