1. Create a configuration and assign users
2. Define settings and add data sets
3. Activate the configuration and have users install plugin

1. Create users
2. Edit users
3. Reset passwords for users
4. create default sales teams
5. create personal groups
6. Unlock non-portal users
7. Assign users to specified profiles
8. Log in as a user
9. Manage custom objects created by an administrator

Check the user’s login history.

NOTE: Before resetting a user password, first check to see why the user was prevented from logging in by reviewing the user’s login history. The login history should explain why the user was prevented from logging in.

1. Users 
2. Queues

1. Folder Access can be set to Read Only or Read/Write. 
2. Folder access does not roll up based on role hierarchy.

What 3 things should the Administrator to make this happen?

1. Set Accounts as Private in the OWD.
2. Create two groups the High Wealth and Retirement groups.
3. Add sharing rules that allow High Wealth Group to be able to view any accounts owned by users in this group.

Or use Account Record type as the divide, and allow High Wealth group to see any accounts with this record type.

1. Articles
2. Article Management
3. Cases
4. Customer
5. Partner Portal

If user logs in before the restricted hours, the system ends the user’s session when the restricted hours begin.

Users will not be given the opportunity to save a record in progress.

1. Make sure the user has marketing user checked on their user record
2. Check that they have the ability to Create Campaigns on their profile.

The administrator needs to

1. enable mobile for the organization. 
2. Mobile Lite application must be installed on users mobile device

B: No

Note: The only customization that can be done on standard profiles is the Tab Settings, Custom App Settings, and the Desktop Integration Settings

Each “A” record must have at least one related “B” record

OR

“A” records may or may not have related “B” records

(1) Validation Rules

(2) Assignment Rules

(3) Workflow Rules

(4) Escalation Rules 

1. Revenue Schedules
2. Quantity Schedules

NOTE: A Quantity Schedule outlines the dates, number of units (i.e., quantity), and number of installments for billing or shipping a product.

A Revenue Schedule outlines the dates, revenue amounts, and number of installments for billing or recognizing revenue from a product. Your organization can decide exactly how to use revenue or quantity schedules.

1. Standard Payment
2. Delivery cycles for a product

B. No Note: Whenever you see the words “restrict” and “Sharing Rules” together assume that this is not the answer.

Sharing Rules are used to reduce security not increase it.

Sharing rules can be used to make automatic exceptions to the organization-wide default for defined sets of users (groups, roles, roles and subordinates).

C. Deactivate the user and maintain the data

NOTE: Users can never be deleted from Salesforce. Why? Think about data tracking. It's possible for inactive users to be listed as “Created By” users even though they are no longer active in an organization.

• The validation rule execution sequence is

1. first standard validation rules like required, unique, data type;
2. followed by custom validation rules.