What really profile and permission sets means in salesforce. It will be helpful for Salesforce beginners.

1. Presented By: Sunil Kumar
Email id: sunil02kumar@gmail.com
Twitter : @sunil02kumar
Blog: http://sunil02kumar.blogspot.in/
PROFILES AND
PERMISSION SETS IN
SALESFORCE

2. Module Agenda
 Overview of profiles.
 Profiles and Permissions.
 Profile and Access to Data.
 Profiles and the User Interface.
 Permission Sets

3. What is a Profile?
 Defines a user`s permissions to perform different functions.
 Determines how a user sees records to which s/he has access.
 Every user has a profile(only 1 profile).
 we can group the things that profiles control into three categories :
- Permission, Access to Data, and User Interface.
Permissions Access to Data User Interface
General User
Permissions
Field Level
Security
Page Layout
Administrative
Permissions
Object CRUD Record Type
Standard/Custom
Object CRUD
Login Hours and
IP Ranges
Tabs

4. What Do Profile Control?
 Tab setting determine which tabs users see when they log in.
 Permissions determine what users can do to record to which they
have access.

5. What Do Profile Control?(Cont.)
Login Hours and Login IP Ranges
 Sets the hours when users with a particular profile can use the
system
 Sets the IP addresses from which users with a particular profile can
log in.

6. Additional Information About Profiles
 Salesforce provides many standard profile.
- Permission on standard profile can not be customize.
 Developers can create custom profiles.
- when creating a new custom profile, developers need to select a
profile from which to copy over permission and settings.
 Typically, Organizations will have one profile for each actor.

7. Module Agenda
 Overview of profiles.
 Profiles and Permissions.
 Profile and Access to Data.
 Profiles and the User Interface.
 Permission Sets

8. Profile have set of permissions
 Profiles control Administrator Permissions.
 Profiles control General User Permissions.

9. A Few Permission to Note
• “ View All Data ”
• “ Modify All Data ”
• “ Customize Application ”
• “ API Only User ”
• “ Password Never Expires ”

10. Object Permissions
 Permissions determine what users can do to records to which their
have access.
 Lacking the “Read” permission for an object means that users will
not be able to access it at all.
- No access in the application or API.
- No access on Reports.
- No access through search.

11. Module Agenda
 Overview of profiles.
 Profiles and Permissions.
 Profile and Access to Data.
 Profiles and the User Interface.
 Permission Sets

12. What is Field-Level Security?
 Restricts users` access to view and edit fields.
 Overrides any less-restrictive field access setting in page layouts
and search layouts.
 Controls which fields users can access in related lists, list views,
reports, force.com connect offline, email and mail merge templates,
custom links, and when synchronizing data or importing data.

13. Module Agenda
 Overview of profiles.
 Profiles and Permissions.
 Profile and Access to Data.
 Profiles and the User Interface.
 Permission Sets

14. Record Types
Record types are used to tailor user interaction experience to specific
business needs.
Note: Record types only affect the way that data is displayed in the UI.
It is not a form of sub-classing.
 Record types can determine page layouts, in conjunction with
profiles.
 Or limit picklist options.

15. What does a page layout Control?
 How detail and edit pages are organized.
 Page section customizations.
 Which fields, related lists, and custom links a user sees.
 Field properties-visible, read-only and required.
Note: May establish unique layouts for different business scenarios.

16. Module Agenda
 Overview of profiles.
 Profiles and Permissions.
 Profile and Access to Data.
 Profiles and the User Interface.
 Permission Sets

17. 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 are assigned to users. You can assign permission to multiple users
using Apex data loader.
• Permission sets are very useful when you want to assign permission to users on
ad-hoc basis without doing any changes to user’s profile.

18. • Assigned apps
• Object settings, which include:
 Tab settings
 Record type settings
 Object permissions
 Field permissions
• App permissions
• Apex class access
• Visualforce page access
• System permissions
Permission Sets
Various permission which can be configured in permission sets
are: