Recognising the anti-pattern: Permission-set strategy
Why this deserves attention
A scalable access model grants capability through composable permission sets rather than profile sprawl. This becomes more valuable as the platform, team and integration estate grow.
Duplicated profiles make access difficult to explain, review and remove when roles change. On 3 June 2025, this archive entry records the principle as a practical design concern rather than a product announcement.
Watch the warning signs
Look at permission-set strategy through the early signs that a convenient implementation is becoming long-term risk. The objective is not to introduce more process; it is to expose the few decisions that determine reliability, ownership and future change.
Define a minimal baseline, group permissions by business capability and automate assignment from approved role decisions. Record the decision close to the solution so that delivery, support and future architecture reviews work from the same intent.
What good looks like
Access becomes easier to audit and safer to evolve. The team can describe the expected behaviour, the owner, the evidence of success and the response when reality differs from the design.
A useful next step is to review one live implementation against this principle, identify the largest unowned assumption and turn it into a bounded improvement with a measurable outcome.
Official reference
Official Salesforce Release Notes