Hi All,
We are facing an issue with a managed package related to custom permissions assignment.
We have included a custom permission in our managed package. When the package is installed using the “Install for All Users” option, we observe that the custom permission becomes available across all profiles/users in the org.
However, our requirement is that this custom permission should not be assigned to all profiles by default.
We would like to understand:
- Can managed packages update profiles to include custom permissions during installation?
- Could this behavior be caused by profile metadata being included in the package?
- What is the recommended approach to ensure custom permissions are not automatically assigned to all users?
Any guidance or best practices would be really helpful.
Thanks in advance!
Divya Chauhan (Kcloud Technologies) Forum Ambassador
Yes, this can happen because managed package profile settings are applied during install, and custom permissions can be included in those profile settings. Salesforce also recommends using permission sets instead of profiles for access control.