User Management

Question 1

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.

Answer 1

Usernames

Question 2

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.

Answer 2

User Licenses

Question 3

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.

Answer 3

Profiles

Question 4

(True or False) Each user can have only one profile.

Answer 4

True

Question 5

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.

Answer 5

Roles

Question 6

(True or False) Roles are mandatory and only 1 role per user.

Answer 6

False. (Roles are optional)

Question 7

It is a short name to identify the user on list pages, reports, or other places where their entire name doesn’t fit.

Answer 7

Alias

Question 8

(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.

Answer 8

True

Question 9

(True or False) Add multiple users up to 20 users at a time.

Answer 9

False (10 users)

Question 10

Fill the blank: If a user follows the link and does not set a password, ________.

Answer 10

the admin have to reset their password before they can log in.

Question 11

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.

Answer 11

Organisation / Org-Level Security

Question 12

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.

Answer 12

Object/Object-Level Security

Question 13

You can use this to restrict access to certain fields, even for objects a user has access to.

Answer 13

Field-level Security

Question 14

This level of Data Access can allow particular users to view an object, but then restrict the individual object ___ they’re allowed to see.

Answer 14

Records

Question 15

Four types of Record-level Security

Answer 15

1. Org-wide defaults
2. Role Hierarchies
3. Sharing Rules
4. Manual Sharing

Question 16

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.

Answer 16

Org-wide defaults

Question 17

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.

Answer 17

Role Hierarchies

Question 18

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.

Answer 18

Sharing Rules

Question 19

It allows owners of particular records to share them with other users.

Answer 19

Manual Sharing

Question 20

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.

Answer 20

Record-Level Security

Question 21

When object– versus record–level permissions conflict, which one win?

Answer 21

Record-level permissions (the one that is most restrictive)

Question 22

(Org-wide Sharing Defaults) Only the record owner, and users above that role in the hierarchy, can view, edit, and report on those records.

Answer 22

Private

Question 23

(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.

Answer 23

Public Read Only

Question 24

(Org-wide Sharing Defaults) All users can view, edit, and report on all records.

Answer 24

Public Read/Write

Question 25

(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.

Answer 25

Controlled by Parent

Question 26

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, _______.

Answer 26

you restrict record access to only the record owner and users granted access by the organization–wide defaults.