Admin Bootcamp 3 Flashcards
(30 cards)
Standard Objects
Accounts, Contacts, Opportunities, Cases, Campaigns, Leads (campaign and leads are Marketing)
Company Profile
Collection of information about your org, mostly captured during signup: Company information (name, address, primary contact, default locale, default currency, storage used, license avail). Financial information (fiscal year, currencies), Support Information (business hours, holidays)
Local Settings
allow you to personalize display of data for different uses based on their geographical location.
Fiscal Year
default standard fiscal year follows the gregorian calendar
Currency
SF orgs are single currency by default. you set the required currency locale in the company profile. all currency values on records will display in appropriate currency. However, you can activate additional currencies. if you do this, new users will inherit the corp currency but can set their own. new records will inherit a user’s personal currency.
Advanced Currency Management
allows you to “lock” the converted amount on closed opportunities based on the closeed date.
Profile
collection of settings and permissions that determines what users can see in the UI and what they can do. Settings are what they see (apps, tabs, record types, page layouts, fields) and permissions (app permissions, system permissions, standard object, custom object)
Standard Profiles
can’t be deleted and permissions can’t be edited.
sys admin - view and modify all data, customize app.
standard user - view, edit, and delete records they can access
solution manager - standard user + manage published solutions
marketing user - standard user + import leads
contract manager - standard user + manage contracts
read only - only view records they can access
Tab Settings
Users can access tabs set to Default Off through the App Launcher in All Items
User
someone with login access to your SF org who has a license and a user record containing personal, security, and locale information.
Login Issues
Login History related list on a user record displays when, where, and how a user attempts to login. Status column diagnoses any login issues
Restricting Login Hours and IP Ranges
Setup/Admin/Users/Profiles
Object Permissions
Object Permissions only determine the KINDS of records users can view, create, edit, or delete, not the individual records themselves
Permission Sets
Permission sets can be assigned to users from the permission set itself or through the Permission Set Assignments related list on a user’s record. The user’s total access will be determined by the user’s profile, plus any permission sets assigned to the user’s record
Record Access
Determines which individual records users can view and edit in each object they have access to on their profile
Org Wide Defaults (OWD)
Use OWD to set the default level of access users have to records they do not own, in each object.
Access levels determine what a user can do with records they do not own
Role Hierarchy
in a private or hybrid model, role hierarchy lets you open up record access to managers, team leaders, and operations people, who may have been denied access via the OWD
Sharing Rules
Create sharing rules to grant additional record access to groups of users on an object by object basis. Sharing rules are:
- exceptions to OWD
- irrelevant for public data access models
- comprising 3 components (Share which records, with which users, what level of access)
Account Teams and Opportunity Teams
enable account/opportunity teams to allow users to grant additional access to their accounts and related records/opportunities.
Standard Fields
All objects have a predefined set of fields to capture common business information. You can’t delete them, but you can use field-level security to hide them, or remoo
Controlling/Dependent Picklists
Users select a value in a controlling picklist, which filters the values available in a second, dependent picklist
Picklists
Fields that allow users to select either single or multiple values from a predefined list during data entry.
Lookups
Lookups are fields that allow users to select a record from another object, including the User object, during data entry. In this way, they can link two records together to create a parent-child relationship.
Formula fields
Custom formula fields allow you to define calculations that reference other fields to display new numeric, text, date, or checkbox values specifc to your business requirements.
Formula fields:
1. read-only, don’t display on record edit pages
2. can reference fields on the same object, or a parent or lookup object.
3. can’t reference encrypted, description, or customer long text area fields
4. are not searchable, or available for lead conversion or the weekly export service.
