I’m new to this…I guess, I will talk briefly on what I’ve been working on as of late, high level.
Today, I will share my experience on permission sets and their intended usage.
Permission sets are designed to be leveraged as an additive for access at the [Object Settings] and [System Permissions] level that aren’t enabled at the profile level in Salesforce. If you’re looking to enforce security in your organization at the object level. Permission sets might be a good idea to consider. You’re able to determine who has administrative rights at the object level.
Note: You will want to assign record types accordingly. Furthermore, you will want to first review the Organization Wide Default sharing settings located at the following: Setup -> Administer -> Security Controls -> Sharing Settings.
There is much to learn when considering the security and appropriate provisioning of administer rights in Salesforce. Permission sets will be the more effective route, as modifying multiple profiles can be quite the daunting task. Depending on the size of your organization, managing profiles via permission sets is an approach you’ll find yields value-add to your organization.
Permission sets are assigned to a users record and as mentioned earlier work as an extension or additive of the already assigned (defined) profile in the users record.
Note: Permission sets do NOT remove access/rights from the profile. A permission set will always defer to what is already defined at the profile level.
If you have additional questions and/or feedback. Please feel free to contact me directly at email@example.com (or comment in response) and continue to follow my blog for future posts. I will try my best at updating frequently.