salesforce_security_impl_guide

More documents

Recommendations

Info

Securing and Sharing Data Permission Sets Overview Permission Sets Overview Watch a Video Tutorial: Who Sees What: Permission Sets A permission set is a collection of settings and permissions that give users access to various tools and functions. The settings and permissions in permission sets are also found in profiles, but permission sets extend users’ functional access without changing their profiles. For example, to give users access to a custom object, create a permission set, enable the required permissions for the object, and assign the permission set to the users. You never have to change profiles, or create a profile for a single use case. While users can have only one profile, they can have multiple permission sets. Permission sets include settings for: • Assigned apps • Object settings, which include: – Tab settings – Record type settings – Object permissions – Field permissions EDITIONS Available in: Enterprise, Performance, Unlimited, Developer, and Database.com Editions Visualforce is not available in Database.com • App permissions • Apex class access • Visualforce page access • System permissions • Service providers (only if you've enabled Salesforce as an identity provider) • External data source access • Custom permissions Note: • Some user licenses restrict the number of custom apps or tabs a user can access. Salesforce calculates the total allowed number of custom tabs and assigned apps from settings in a user’s assigned profile plus any assigned permission sets. For users with a license that restricts the number of apps or tabs, you can't assign more than the allotted limit through their assigned profile and permission sets. For example, a user with the Force.com App Subscription user license with access to one Force.com Light App can access only that app’s custom tabs. • In Group and Professional Editions, permission sets may be included in installed packages, where they can be viewed and assigned to users but not edited. 24
Securing and Sharing Data Creating Permission Sets Creating Permission Sets You can either clone an existing permission set or create a new one. A cloned permission set starts with the same user license and enabled permissions as the permission set it is cloned from, while a new permission set starts with no user license selected and no permissions enabled. You can create up to 1,000 permission sets. 1. From Setup, click Manage Users > Permission Sets. 2. Do one of the following: • To create a permission set with no permissions enabled, click New. • To create a permission set based on an existing set, click Clone next to the set you want to copy. You can also select the permission set and click Clone in the overview page or one of the settings pages. Note: Clone a permission set only if the new one should have the same user license as the original. In a cloned permission set, you can't select a different license. EDITIONS Available in: • Enterprise • Performance • Unlimited • Developer • Database.com USER PERMISSIONS To create permission sets: • “Manage Profiles and Permission Sets” 3. Enter a label, API name, and description. The API name is a unique name used by the Force.com API and managed packages. It must begin with a letter and use only alphanumeric characters and underscores. It can't include spaces, end with an underscore, or have two consecutive underscores. 4. If this is a new permission set, select a user license option. If you plan to assign this permission set to multiple users with different licenses, select --None-- . If only users with one type of license will use this permission set, select the user license that’s associated with them. If you’re cloning a permission set, you can’t select a user license. If the User License field is blank, no user license is associated with the permission set. 5. Click Save. The permission set overview page appears. From here, you can navigate to the permissions you want to add or change. About User Licenses in Permission Sets When creating a permission set, you can select a specific user license or --None-- . If you’re selecting a specific license, select the license that matches the users who will use the permission set. For example, if you plan to assign this permission set to users with the Salesforce license, select Salesforce. If you plan to assign this permission set to multiple users with different licenses, select --None-- , for no user license. With this option, you can assign the permission set to any users whose license allows the enabled permissions. For example, if you plan to assign the permission set to users with the Salesforce license as well as users with the Salesforce Platform license, select --None-- . EDITIONS Available in: • Enterprise • Performance • Unlimited • Developer • Database.com Note: • Permission sets with no user license don’t include all possible permissions and settings. • You can only assign a permission set with no license to users whose licenses allow the enabled permissions and settings. For example, if you create a permission set with no user license and enable “Author Apex,” you can’t assign that permission set to users with the Salesforce Platform user license because the license doesn’t allow that permission. 25
Page 1 and 2: Security Implementation Guide Versi
Page 3 and 4: CONTENTS Chapter 1: Security Overvi
Page 5 and 6: Contents Editing Lead Sharing Rules
Page 7 and 8: CHAPTER 1 Security Overview Salesfo
Page 9 and 10: Security Overview User Security Ove
Page 11 and 12: Security Overview Custom Permission
Page 13 and 14: Security Overview CAPTCHA Security
Page 15 and 16: Security Overview Auditing • Role
Page 17 and 18: Securing and Sharing Data Revoking
Page 19 and 20: Securing and Sharing Data Viewing P
Page 21 and 22: Securing and Sharing Data Cloning P
Page 23 and 24: Securing and Sharing Data App and S
Page 25 and 26: Securing and Sharing Data Working w
Page 27 and 28: Securing and Sharing Data Enable Cu
Page 29: Securing and Sharing Data Assigning
Page 33 and 34: Securing and Sharing Data Editing P
Page 35 and 36: Securing and Sharing Data Searching
Page 37 and 38: Securing and Sharing Data Enable Cu
Page 39 and 40: Securing and Sharing Data Object Pe
Page 41 and 42: Securing and Sharing Data Comparing
Page 43 and 44: Securing and Sharing Data Setting F
Page 45 and 46: Securing and Sharing Data Working w
Page 47 and 48: Securing and Sharing Data Setting L
Page 49 and 50: Securing and Sharing Data Restricti
Page 51 and 52: Securing and Sharing Data Managing
Page 53 and 54: Securing and Sharing Data External
Page 55 and 56: Securing and Sharing Data Disabling
Page 57 and 58: Securing and Sharing Data Creating
Page 67 and 68: Securing and Sharing Data Editing L
Page 69 and 70: Securing and Sharing Data Editing C
Page 71 and 72: Securing and Sharing Data Editing C
Page 73 and 74: Securing and Sharing Data Sharing R
Page 75 and 76: Securing and Sharing Data User Shar
Page 77 and 78: Securing and Sharing Data Sharing U
Page 81 and 82:
Securing and Sharing Data Viewing A
Page 83 and 84:
Securing and Sharing Data Granting
Page 85 and 86:
Configuring Salesforce Security Fea
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
CHAPTER 4 Enabling Single Sign-On S
Page 97 and 98:
Enabling Single Sign-On • Before
Page 99 and 100:
Monitoring Your Organization's Secu
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Security Tips for Apex and Visualfo
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
INDEX A Access about 10 revoking 11
Page 115 and 116:
Index Profiles (continued) object p
show all

salesforce_security_impl_guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?