click below
click below
Normal Size Small Size show me how
Salesforce Admin Cer
Training
| Term | Definition |
|---|---|
| Record | An item you are tracking in your database; if your data is like a spreadsheet, then a record is a row on the spreadsheet |
| Field | A place where you store a value, like a name or address; using our spreadsheet example, a field would be a column on the spreadsheet |
| Object | A table in the database; in that spreadsheet example, an object is a tab on the spreadsheet |
| Org | Short for "Organization", the place where all your data, configuration, and customization lives. You log in to access it. "Your instance of Salesforce" |
| App | A set of fields, objects, permissions, and functionality to support a business process |
| Account Object | Accounts are the companies you're doing business with. You can also do business with individual people (like solo contractors) using something called Person Accounts |
| Contact Object | Contacts are the people who work at an Account |
| Leads Object | Leads are potential prospects. You haven't yet qualified that they are ready to buy or what product they need. |
| Opportunities | Qualified leads that you've converted from a lead. Whn you convert a Lead, you create an Account and Contact along with the Opportunity |
| Multitenancy | Sharing resources (referencing Salesforce Architecture) |
| API's | Allow different pieces of software to connect to each other and exchange information |
| Setup: Company Information | Find Org ID See Licensing Info Monitor important limits like data and file usage |
| Setup: Users | Reset Passwords Create new users and deactivate or freeze existing users View informatiot about users |
| Setup: Profiles | Manage who can see what with user profiles Create custom profiles |
| Setup: View Setup Audit Tril | See 6 months of change history in your org Find out who made changes and when Tool for troubleshooting org configuration issues |
| Login History | See 6 months of login history for your org View date, time, user, IP address, and more login data Use for security tracking and adoption monitoring |
| Data Model | A way to model what database tables look like in a way that makes sense to humans |
| Standard Objects vs Custom Objects | Standard come included with Salesforce (Account, Contact, Lead and Opp) |
| Usernames | Username must be formatted like an email address and must be UNIQUE across all SF organizations |
| User Licenses | This determines which features the user can access in SF. For example, you can allow users access to standard SF features and Chatter with the standard SF license. Chatter free license - free and chatter only |
| Profiles | Profiles determine what users can do in SF. Profiles come with a set of permissions which grant access to particular objects, fields, tabs and records. Each user can have only 1 profile. |
| Roles | Roles determine what users can see in SF based on where they are located in the role hierarchy. Each user can have only one role |
| Alias | a short name to identify the user on list pages, reports or other places where their entire name doesn't fit. By default, first letter of users first name, first four of last (STHOMS) |
| Levels of Data Access - Organization | Organization level access (the highest level) you can secure access to your organization by maintaining a list of authorized users, setting password policies, and limiting login access to certain hours and certain locations. |
| Object Level Security | Object-level security provides the simplest way to control which users have access to which data. |
| Field Level Security | You can use field-level security to restrict access to certain fields, even for objects a user has access to. For example, you can make the salary field in a position object invisible to interviewers but visible to hiring managers. |
| Organization Wide Defaults | Specify the default level of access users have to each others' records. You use OWD 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 user. |
| Role Hierarchies | Uses company hierarchy to open up records to those below them |
| Sharing rules | Sharing rules 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. Can only OPEN UP access, cannot restrict it. |
| Manual sharing | Manual sharing allows owners of particular records to share them with other users. |
| 6 Standard Objects | Accounts, Leads, Campaigns, Contacts, Sales, Cases |
| Permission Sets expand a users permissions, while profiles are used to... | Restrict access. |
| "Public Group" | A collection of individual users, other groups, individual roles or territories and/or roles or terrirtories with their subordinates that all have a function in Common. |
| Where do you find Organization Wide defaults? | Within the Sharing Settings tab |
| To Create, Edit, Delete Library Permissions need... | Manage Content Permissions OR Manage Salesforce CRM Content |
| To Create, Edit or Delete Page Layouts and record types... | Need Manage Record Types and Layouts for Files OR Manage Salesforce CRM Content |
| To Create Content Fields... | Need Manage Content Properties OR Manage Salesforce CRM Content |
| To Create Libraries... | Need Create Libraries OR Manage Salesforce CRM Content |
| To Edit or Delete Libraries... | Need Manage Salesforce CRM Content |
| Cases: Queues | Automatically prioritize your support team's load by creating lists from which specific agents can jump into solve certain cases |
| Assignment Rules | Automatically assign incoming cases to specific agents so that the right people work on the right cases |
| Escalation Rules | Automatically escalate cases to the right people when the cases aren't resolved by a certain time |
| Auto-Response Rules | Automatically send personalized email responses to customers based on each case's details. |
| Use Data Import Wizard when... | You need to load less than 50,000 records The objects you need to import are supported by the wizard You don't need the import process to be automated |
| Use Data Loader When... | You need to load 50K to 5 Mil records. You need to load into an object that is not supported by the DIW You want to schedule regular data loads, such as nightly imports |
| Lightning Flow... | The PRODUCT that encompasses building, managing, and running flows and processes |
| Flow Builder | A Point and Click tool for building flows |
| Flow | An application that automates a business process by collecting data and doing something in your Salesforce org or an external system |
| 3 Building Blocks of a Flow.... | Elements - Appear on the canvas (drag n drop) Connectors - Define the path that the flow takes at runtime. They tell the flow which element to execute. Resources - Containers that represent a given value, such as a field values or formula |
| Process Bulder Supports 3 Types of Processes ... | - A record CHange process starts when a record is created/updated - An event process starts whena platform event message is received -An invocable process starts when something else, like another process, invokes it |
| Each Process of a Process Builder consists of these two things: | - Criteria that determine when to execute an action group- - Action groups, which consist of immediate or scheduled actions. |
| Report Type | What objects are being shown |
| Report Format | What it looks like: Tabular, Modular, Matrix |
| 7 Standard Objects in Salesforce | Account, Contact, Lead, Opportunity, Case, Campaign, Solutions |
| A Master-Detail relationship is... | A strong relationship where the master records control sharing, ownership, and deletion of detail records |
| A Lookup relationship is.... | A loose relationship where child records have their own security settings (parent/child relationship) |