Declarative Sharing 1 of 3 Flashcards
List declarative settings found to control object and field level security
profiled and permsets to grant CRUD permissions to users
using profiles - defines how users access objects and data, what they can do w/in applications. One profile is assigned to each user in SF
FLS - specified in profiles or permsets allowing view or edit to standard or custom fields
PermSets - collection of settings and permissions that extend users functional access w/out changing their profiles
Access Restrictions - profile can be use to restrict users access to object and fields FLS used to restrict user access to fields
Limitations - permission in standard profiles cannot be edited. A permset can not be used to restrict users access.
Declarative Platform Security Features include:
Explicit Sharing:
OWD
Sharing Rules
Manual Sharing
Administrative settings in Roles and Profiles
Implicit Sharing:
between accounts and child records and for various groups of portal users
Data Encryption: Classic and Shield Platform are the 2 declarative options available for data encryption
Explicit Sharing includes
OWD
Sharing Rules
Manual Sharing
Administrative settings in Roles and Profiles
Implicit Sharing includes
between accounts and child records and for various groups of portal users
Data Encryption: Classic and Shield Platform are the 2 declarative options available for data encryption
List all Platform Security Features
OWD Role Hierarchy Sharing Rules Manual Sharing Profiles Permission Sets Implicit Sharing user & Admin Permissions Field level security shield platform encryption external data source custom permission
An Account Team …
allows a group of users to access and work together on an account record, make it easy to track collaboration on the record
An opportunity team …
allows user access to work together on an opp. give user access and makes it easier to track their roles
Team setup includes
team roles and access levels
What can be used to limit a users access who should not be able to delete the records of a particular object?
Profile
hint: Key work ‘delete’ ie ‘D’ in CRUD
What can be used to restrict users access to view and edit specific field?
Field Level Security
How does Salesforce provide implicit sharing between accounts and child records?
Access to an accounts child record grants implicit read only access to that account. Access to an account grants access to the child records, but the access level depends on the account’s owners role
Which type of team allows a group of sales users to work together on a particular opportunity record?
Opportunity Team
Which action allows account team members to view other members access level
team member access
What should a solution architect recommend if only one user in an organization requires access to a visualforce page?
permset can be created allowing access to the page and assigned to the user
Which declarative options are available to grant explicit record access to users with a specific role who are unable to access records due to OWD setting
Role hierarchy and sharing rules
While defining an account team, which access levels will be available for an account if the OWD default sharing setting for the object has been set to “private’?
Read Only and Read/Write
In order to allow a group of support reps and support manager to work together on certain cases, what should be created?
case team
Which object can be customized to allow users to specify custom information about account team members?
Account team member
Explain the difference between a Profile and a permission set?
Profiles can be used to allow or limit access to DATA, permission sets only grant additional access and do not restrict access access to specific users
Object and field-level security settings can be implemented in Salesforce through the use of ?
profiles and permission sets
Declarative feature used to assign multiple permission sets to a user?
Permission set group
Permission set groups provide the these additional features.
- ) multiple groups can be assigned to a user
- ) permissions can be disabled or muted via a muting permission set (only 1 allowed per permset group)
- ) within a user setting page on the object level settings there is Enable and Muted check boxes to set each CRUD setting to muted.
- ) Updates in a permission set propagate to all permission set groups that include the permission set.
What defines how users access objects and data, and what they can do within the application. When you create users, you assign a profile to each one.
Profiles
salesforce article on profiles:
https://help.salesforce.com/articleView?id=admin_userprofiles.htm&type=5
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.
Permission sets
Salesforce article on permsets:
https://help.salesforce.com/articleView?id=perm_sets_overview.htm&type=5
streamlines permissions assignment and management by bundling permission sets together based on user job functions. Users assigned the permission set group receive the combined permissions of all the permission sets in the group
permission set group
Salesforce article on permission set groups:
https://help.salesforce.com/articleView?id=perm_set_groups.htm&type=5
How can you remove individual permissions form a group
muting feature