User Management Flashcards
It must be formatted like an email address and must be unique across all Salesforce organizations. It can be the user’s email address, so long as it is unique.
Usernames
It determines which features the user can access in Salesforce. You can allow users access to standard Salesforce features and Chatter with the standard Salesforce license.
User Licenses
They determine what users can do in Salesforce. They come with a set of permissions which grant access to particular objects, fields, tabs, and records.
Profiles
(True or False) Each user can have only one profile.
True
They determine what users can see in Salesforce based on where they are located in the hierarchy. Users at the top of the hierarchy can see all the data owned by users below them. Users at lower levels can’t see data owned by users above them, or in other branches, unless sharing rules grant them access.
Roles
(True or False) Roles are mandatory and only 1 role per user.
False. (Roles are optional)
It is a short name to identify the user on list pages, reports, or other places where their entire name doesn’t fit.
Alias
(True or False)By default, the alias is the first letter of the user’s first name and the first four letters of their last name.
True
(True or False) Add multiple users up to 20 users at a time.
False (10 users)
Fill the blank: If a user follows the link and does not set a password, ________.
the admin have to reset their password before they can log in.
At the highest level of data access, you can secure access to this by maintaining a list of authorized users, setting password policies, and limiting login access to certain hours and certain locations.
Organisation / Org-Level Security
This level of Data Access provides the simplest way to control which users have access to which data. By setting permissions on a particular type of this level, you can prevent a group of users from creating, viewing, editing, or deleting any records.
Object/Object-Level Security
You can use this to restrict access to certain fields, even for objects a user has access to.
Field-level Security
This level of Data Access can allow particular users to view an object, but then restrict the individual object ___ they’re allowed to see.
Records
Four types of Record-level Security
- Org-wide defaults
- Role Hierarchies
- Sharing Rules
- Manual Sharing
These specify the default level of access users have to each others’ records. You use these sharing settings to lock down your data to the most restrictive level, and then use the other sharing tools to selectively give access to other users.
Org-wide defaults
These open up access to those higher in the hierarchy so they inherit access to all records owned by users below them in the hierarchy.
Role Hierarchies
These enable you to make automatic exceptions to organization–wide defaults for particular groups of users, to give them access to records they don’t own or can’t normally see.
Sharing Rules
It allows owners of particular records to share them with other users.
Manual Sharing
You can control data access with greater precision by allowing particular users to view an object, but then restricting the individual records within the object they’re allowed to see.
Record-Level Security
When object– versus record–level permissions conflict, which one win?
Record-level permissions (the one that is most restrictive)
(Org-wide Sharing Defaults) Only the record owner, and users above that role in the hierarchy, can view, edit, and report on those records.
Private
(Org-wide Sharing Defaults) 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.
Public Read Only
(Org-wide Sharing Defaults) All users can view, edit, and report on all records.
Public Read/Write
(Org-wide Sharing Defaults) A user can perform an action (such as view, edit, or delete) on a contact based on whether he or she can perform that same action on the record associated with it.
Controlled by Parent
If you want to enable access to records for users above the record owner in the hierarchy for custom objects, use the Grant Access Using Hierarchies checkbox. If you deselect this checkbox for a custom object, _______.
you restrict record access to only the record owner and users granted access by the organization–wide defaults.
