Blackberry isn’t down and out quite yet. it would seem the former competitor in the cellular industry is making one last run at becoming a comparable option for mobile devices. Blackberry’s stock (BBRY) has grown over 45% since 2013. Since taking over; Blackberry’s CEO John Chen has played a pivotal role in aiding the companies stock growth.Their biggest change came in their announcement of the Blackberry Z10 device.Their first handheld device to take on the iPhone form factor. Could this be indicative on a nearing end for Blackberry? A company once known for their unrivaled security and encryption in the realm of corporate e-mail.
Currently, a company that doesn’t have much to bring to the table in 2014, going into 2015. Blackberry now must consider their real competition with the viable options (MobileIron and Airwatch) in the industry for enabling corporate mail on the iOS and Android platform. The Blackberry Enterprise Server (BES) is no longer the selling point when deciding on a mobile device for corporate use.
Take it from me. As a satisfied owner of an iPhone 5 with corporate e-mail setup and configured on my iPhone. It’s apparent that the advantages of being a Blackberry owner with the use of corporate e-mail managed on the BES; no longer yields a benefit over an iOS or Android device.
Mobile Iron! A company that enables and ensures the security and compliance requirements of important corporate data. The combination of mobile device management capabilities, comprehensive security, mobile application management and mobile content management capabilities.
Blackberry is going to have to bring more to the table, if they want to remain relevant for years to come.
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 firstname.lastname@example.org (or comment in response) and continue to follow my blog for future posts. I will try my best at updating frequently.