Video Summary - Salesforce Admin Training For Beginners | Complete Salesforce Admin Course Free

Main ideas / lessons from the video

This is a project-based Salesforce Admin training for beginners.
The goal is to build a Task Assignment Management & Tracking application in Salesforce Lightning.
The trainer starts by explaining core concepts (especially CRM), then walks through the Salesforce Admin features needed to produce a complete working app, including:
- CRM basics → Salesforce overview
- Create a Lightning App
- Create custom objects + tabs
- Add objects to an app
- Create fields (text, picklist, date, long text, lookup)
- Create a formula field
- Build a validation rule
- Create record types
- Customize page layouts
- Create profiles and roles
- Apply security in stages:
  - App-level security
  - Object-level security
  - Tab visibility (tab-level security)
  - Record-level security using OWD (Organization-Wide Defaults)
- Use list views with filters (e.g., tasks from the “previous week”)
Final outcome:
- Admin users can see everything.
- Non-admin users (e.g., employees) see only what they’re allowed to via:
  - app visibility, object visibility, tab visibility, and
  - record access rules/OWD behavior.
- Task status “Completed” requires a completed date enforced by validation rules.

The key theme is building a real Lightning app while learning how Salesforce security layers work together.

Step-by-step methodology / instructions taught (detailed)

1) Project setup: define what you will build

Build a digital todo/task tracker with:

Employee records
Task Assignment records
Tasks assigned to employees and trackable daily

2) Learn CRM basics and Salesforce context (pre-work concept)

CRM stands for Customer Relationship Management.
Salesforce is a cloud CRM platform used for managing sales/marketing/service and customer/partner interactions.

3) Create a Lightning App: “Task Assignment Tracker”

App requirements:

Name: Task assignment tracker
Developer name: auto-generated
Primary hex color: optional (branding)
Navigation/settings concepts covered:
- App navigation type (standard vs console)
- Form factor (desktop/phone)
- Setup experience (full vs service-focused)
- Utility bar (optional)
- Select which tabs/items appear in the app navigation (initially later as objects are added)

Instruction sequence:

Go to Setup (via gear icon).
Search App Manager in Quick Find.
Click New Lightning App.
Fill app details (App name, Developer name; branding fields optional).
Configure App Options.
Choose Navigation Items (initially none).
Set profile access (example: grant to System Administrator).
Click Save and Finish.

4) Create custom objects + tabs

4.1 Create Object 1: Employee

Create custom object:
- Label: Employee
- Plural label: Employees
- Record name field: Employee ID
Record name configuration:
- Data type: Auto Number
- Example display format: TS-{000} (example uses TS-00X style)
- Starting number: set to 1
Optional features covered (left mostly default):
- reports, activities, field history, chatter
Classification and deployment:
- Enterprise/allow sharing + API permissions (defaults)
- Deployed (ready)
Search settings:
- global search left unchecked
After save:
- Launch new custom tab wizard

Create Employee tab

Tab style: example “People” style
Tab visibility:
- default on for all profiles in that step
Limit tab to a specific app:
- include only Task assignment tracker app

4.2 Create Object 2: Task Assignment

Create custom object:
- Label: Task Assignment
- Plural label: Task assignments
- Record name: Task Name (text)
Data type:
- Record name: Text (not auto-number)
After save:
- Launch tab wizard

Create Task Assignment tab

Tab style: example “Pencil”
Restrict tab to Task assignment tracker app only

5) Add objects (tabs) to the Lightning App

Go to App Manager → edit the app Task assignment tracker
In Navigation items, add:
- Employees
- Task assignments
Save changes

Result: these tabs appear in the app navigation.

6) Create fields on objects

6.1 Employee object fields

Create a Text field:
- Field label: Employee Name
- Length: 50
- Required
- Unique (case-insensitive)
Configure:
- Field-level security (trainer notes indicate required field auto grants visibility)
- Include on the page layout so it appears on record pages

6.2 Task Assignment object fields

A) Picklist fields

Task Status picklist
- Values:
  - Not started
  - In progress
  - Completed
- Required: yes
- Default: Not started
- Restrict picklist enabled (data integrity)
Technology picklist
- Example values included:
  - Python, SQL Server, MongoDB, Java, SharePoint, cloud-related entries, etc.
- Display alphabetically
- Required: yes

B) Date fields

Start Date (Date)
- Required: yes
- Default value: TODAY() (trainer description uses “two-day” context, but the setup is TODAY for current date)
Completed Date (Date)
- Not required
- No default

C) Long text area

Comment field (Text Area Long)
- Large length (example sets to ~“thousand”)
- Visible lines: example 10
- Not required

D) Lookup relationship

Employee ID lookup on Task Assignment → Employee object
- Related object: Employee
- Field: Required
- Required behavior and deletion handling default as described

E) Formula field

Create a formula field to auto-display Employee Name
- Return type: Text
- Logic:
  - If Employee ID is blank → return blank
  - Else → fetch related Employee Name through the lookup relationship

7) Create a Validation Rule

Goal:

If Task Status = Completed, then Completed Date must be filled.

Validation setup:

Object: Task Assignment
Active: checked
Error condition formula:
- AND( ISPICKVAL(Task_Status__c, "Completed"), ISBLANK(Completed_Detail__c) )
Error message example:
- “Please provide a completed date when the status is set to completed”
Error location:
- displayed at the top of the page

Demonstrated behavior:

Saving a Completed task without Completed Date triggers the validation error.

8) Create Record Types (Technology-based behavior)

Purpose:

Different records (same object) show different picklist values based on record type.

Trainer approach:

Create multiple record types for Task Assignment, example categories:
- Cloud, Programming, Database, SharePoint

For each record type:

Assign active + available to profiles
Assign page layout (concept: apply one layout to all profiles)
Edit Technology picklist values so only relevant options appear

Result behavior:

When creating a new Task Assignment, the user selects a record type.
The Technology picklist then shows only allowed values for that record type.

9) Customize Page Layout

Edit the Task assignment layout
Rearrange fields using drag-and-drop
Example final layout arrangement:
- Left: Employee ID
- Right: Employee Name (formula), Task Name, Task Status
- Second section: Technology, Start Date, Completed Date, Comment, etc.
Verified by refreshing the record creation form.

10) Create a Profile

Definition explained:

Profiles control permissions/settings for what users can do.

Steps:

Setup → Profiles → New Profile
Clone an existing profile (example: Standard User)
Name: Prime job employee task tracker
Save

11) Create Roles

Definition explained:

Roles define a hierarchy used by sharing rules.

Steps:

Setup → Roles → Add Role
Create hierarchy:
- CEO (under Prime job)
- Manager (reports to CEO)
- Team Lead (reports to Manager)
- Associate (reports to Team Lead)

Used later to support record visibility expectations.

12) Create Users + set password notification

Setup → Users → Add Multiple Users

Example user:

Jack Brown

Set:

License (Salesforce edition)
Profile: Prime job employee task tracker
Role: example Manager

Ensure:

Generate new password and notify user immediately is checked so the user receives a reset link email.

13) Apply security layers

13.1 App-level security

Setup → Profiles → Edit profile → Custom App Settings
Make only Task assignment tracker visible and set it as default landing app

Result:

Users can’t see other apps; the app launcher won’t show it unless enabled.

13.2 Object-level security

Setup → Profiles → Edit profile → Object Settings (Custom Object Permissions)

Trainer configuration:

Employee object: Read only (no create/edit/delete)
Task Assignment object: Read + Create + Edit + Delete
No “view all/modify all” access

Standard objects: left unconfigured/unchecked as described.

13.3 Tab visibility (tab-level security)

Setup → Profiles → Edit profile → Tab settings

Trainer settings:

Employee tab: Tab Hidden
Task Assignment tab: Default On

Demonstrated difference:

“Default Off” allows user personalization.
“Tab Hidden” prevents users from enabling it.

13.4 Record-level security using OWD

Setup → Sharing settings → Organization-Wide Defaults for Task Assignment object
Set Task Assignment default to Private
Keep role-based sharing behavior as described (higher roles can access records based on sharing expectations)

Demonstrated effect:

Users can see records they created (and/or permitted by OWD/role hierarchy), but not records created by higher authority unless sharing rules grant access.

14) Create a List View filtered to “previous week”

Create list view from the Task Assignment tab:
- Object → Task Assignment tab → gear icon → New List View

List view configuration:

Name: Previous week
Who can see: All users
Filter:
- Field: Created Date
- Operator: equals
- Value: “Last week”

Demonstrated:

“Previous week” shows only tasks created in that time period.

Speakers / sources featured

Tanuri — Salesforce consultant from TS info Technologies (main presenter/trainer).

Salesforce Admin Training For Beginners | Complete Salesforce Admin Course Free

Key takeaways