Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
9 Cards in this Set
- Front
- Back
|
how can you manage record–level access? |
types include; Organization–wide defaults, Role hierarchies, Sharing rules, Manual sharing. The permissions on a record are always evaluated according to a combination of object–, field–, and record–level permissions. When object– versus record–level permissions conflict, the most restrictive settings win. |
|
|
what are organization–wide defaults? |
the defaults that specify the baseline level of access that users have to records that they don’t own. |
|
|
Field type; Controlled by Parent |
A user can perform an action (such as view, edit, or delete) on a record based on whether he or she can perform that same action on the record associated with it. |
|
|
field type; Public Read/Write |
All users can view, edit, and report on all records. |
|
|
field type; Public Read Only |
All users can view and report on records but not edit them. Only the owner, and users above that role in the hierarchy, can edit those records. |
|
|
field type; Private |
Only the record owner, and users above that role in the hierarchy, can view, edit, and report on those records. |
|
|
Dependent picklists |
.help users enter accurate and consistent data. .is a custom or multi-select picklist for which the valid values depend on the value of another field, called the controlling field. |
|
|
Controlling fields |
can be any picklist (with at least one and fewer than 300 values) or checkbox field on the same record. |
|
|
Assignment rules |
define conditions that determine how leads or cases are processed. |
