• Write code in the wrong language
• Ignore Salesforce naming conventions
• Miss metadata files
• Generate incorrect SOQL field API names
• Skip documentation standards

To make GitHub Copilot truly useful for Salesforce development, we need to train it with project-level instructions.

In this guide, you’ll learn how to:

• Configure GitHub Copilot for Salesforce development
• Create reusable AI rules
• Force naming conventions
• Auto-generate Apex metadata files
• Improve SOQL accuracy using SObject definitions
• Generate documented Apex classes
• Build a working LWC + Apex example

This creates a highly optimized Salesforce AI development workflow inside VS Code.

Understanding the Difference Between Free and Pro GitHub Copilot

When using GitHub Copilot Free, you may only see limited model options such as:

• Claude 3.5 Sonnet
• GPT-4…& newly available

However, with GitHub Copilot Pro, additional premium models become available, such as:

• OpenAI o1 Preview
• OpenAI o1 Mini Preview

These models generally provide:

• Better reasoning
• Improved code generation
• Better architecture suggestions
• More accurate debugging assistance

This becomes especially valuable for enterprise Salesforce development.

Step 1: Create a Salesforce DX Project

Start by creating a Salesforce DX project inside VS Code.

Typical project structure:

force-app/
manifest/
sfdx-project.json

After creating the project:

1. Open VS Code
2. Create a new Salesforce project with Manifest
3. Authorize a Salesforce Org
4. Connect the org successfully

Once the org is connected, we can begin configuring GitHub Copilot.

Step 2: Enable GitHub Copilot Project Instructions

GitHub Copilot supports project-level AI instructions using a special markdown file.

To enable it:

Navigate to VS Code Settings

Search for:

Copilot Instructions

Enable the setting:

Use github.copilot-instructions.md

This allows Copilot to automatically read project instructions before generating responses.

Step 3: Create the GitHub Copilot Instructions File

Inside your project root, create the following structure:

.github/
    copilot-instructions.md

The filename must be exact.

Step 4: Define Salesforce AI Rules

Now we start training Copilot specifically for Salesforce development.

Initial Instructions

Add the following rules:

You need to act as a Salesforce developer.

While creating Apex classes or Lightning Web Components,
always follow Salesforce best practices.

Whenever creating Apex classes,
also create the corresponding meta.xml file.

While creating Apex classes or components,
always use prefix coder_.

Why These Rules Matter

Without instructions:

• Copilot may generate Java or Python logic
• Metadata files may be skipped
• Naming conventions may break
• Salesforce deployment may fail

With instructions:

• Copilot becomes Salesforce-aware
• Generated code becomes deployment-ready
• Naming standards remain consistent

Step 5: Generate an LWC + Apex Controller Using Copilot

Now let’s test the setup.

Open:

Edit with Copilot

Use the following prompt:

Help me create a Lightning Web Component
which displays Contact records in a data table.

Use an Apex class to retrieve contacts.

What GitHub Copilot Generates

GitHub Copilot now generates:

Apex Controller

public with sharing class coder_ContactController {
    
    @AuraEnabled(cacheable=true)
    public static List<Contact> getContacts() {
        return [
            SELECT Id, Name, Email, Phone
            FROM Contact
            LIMIT 10
        ];
    }
}

Apex Meta File

<?xml version="1.0" encoding="UTF-8"?>
<ApexClass xmlns="http://soap.sforce.com/2006/04/metadata">
    <apiVersion>61.0</apiVersion>
    <status>Active</status>
</ApexClass>

Lightning Web Component HTML

<template>
    <lightning-card title="Contacts">
        <lightning-datatable
            key-field="Id"
            data={contacts}
            columns={columns}>
        </lightning-datatable>
    </lightning-card>
</template>

JavaScript Controller

import { LightningElement, wire } from 'lwc';
import getContacts from '@salesforce/apex/coder_ContactController.getContacts';

export default class CoderContactTable extends LightningElement {

    contacts = [];

    columns = [
        { label: 'Name', fieldName: 'Name' },
        { label: 'Email', fieldName: 'Email' },
        { label: 'Phone', fieldName: 'Phone' }
    ];

    @wire(getContacts)
    wiredContacts({ error, data }) {
        if(data) {
            this.contacts = data;
        } else if(error) {
            console.error(error);
        }
    }
}

Important Observation

Notice how GitHub Copilot automatically:

• Added the coder_ prefix
• Created the meta.xml file
• Generated Apex code
• Generated the LWC
• Wired Apex correctly

This happened because of the AI instructions.

Step 6: Improving SOQL Accuracy Using SObject Definitions

One of the biggest AI problems in Salesforce development is:

Incorrect API Names

AI models do not inherently know:

• Your custom object names
• Your field API names
• Managed package metadata
• Custom namespace structure

This often causes incorrect SOQL generation.

Example problem:

SELECT Price__c, Tags__c FROM Br__c

But actual field API might be:

coder_Tags__c

Step 7: Refresh SObject Definitions

To solve this, refresh Salesforce object definitions.

Run:

SFDX: Refresh SObject Definitions

This generates local metadata references for all objects and fields.

GitHub Copilot can now use these files for context.

Step 8: Add SOQL Intelligence Instructions

Add another instruction to:

Whenever writing SOQL queries
or creating Salesforce records,
refer SObject definition files
to get correct object and field API names.

Step 9: Attach the SObject File to Copilot

Before generating SOQL:

1. Open the object definition file
2. Or attach it manually in chat

Example:

objects/Br__c.object-meta.xml

Now Copilot gains field awareness.

Example: Correct SOQL Generation

Prompt:

Write a SOQL query to retrieve beer records
with price and tags.

Now GitHub Copilot generates:

SELECT Price__c,
       coder_Tags__c
FROM Br__c

This dramatically improves AI-generated Salesforce code quality.

Step 10: Enforcing Documentation Standards

Most AI-generated Apex classes lack documentation.

To standardize this, add another rule.

Documentation Rule

Whenever creating Apex classes,
always add documentation
using the following format.

Description:
Author:
Last Modified:

Step 11: Generate a Batch Apex Class

Prompt:

Create a Batch Apex class
to delete Lead records
where Status = 'Bogus'

Generated Batch Apex Example

/**
 * Description: Batch class to delete bogus leads
 * Author: Sanskriti Joshi
 * Last Modified: May 2026
 */

public class coder_DeleteBogusLeadsBatch
implements Database.Batchable<SObject> {

    public Database.QueryLocator start(
        Database.BatchableContext bc
    ) {
        return Database.getQueryLocator(
            'SELECT Id FROM Lead WHERE Status = \'Bogus\''
        );
    }

    public void execute(
        Database.BatchableContext bc,
        List<Lead> scope
    ) {
        delete scope;
    }

    public void finish(
        Database.BatchableContext bc
    ) {
        System.debug('Batch completed');
    }
}

Why AI Instructions Are Extremely Important

Without instructions:

• AI behaves inconsistently
• Output quality varies
• Standards break
• Naming conventions fail
• Deployment issues increase

With project instructions:

• Code becomes predictable
• AI follows enterprise standards
• Reusability improves
• Teams stay aligned
• Development accelerates

Best Practices for Copilot Instructions

Keep instructions:

• Short
• Specific
• Action-oriented

Avoid:

• Long paragraphs
• Overly complex instructions
• Contradicting rules
• Excessive prompts

Because every instruction gets appended to the AI context window.

Too many instructions can:

• Reduce performance
• Reduce response quality
• Increase hallucinations

Recommended Salesforce Copilot Rules

A strong starting template:

Act as a Salesforce developer.

Always create Apex meta.xml files.

Use naming prefix coder_.

Follow Salesforce best practices.

Add Apex documentation.

Use SObject definitions
for SOQL field references.

Final Outcome

After implementing these configurations:

GitHub Copilot becomes:

• A Salesforce-aware AI assistant
• Metadata-aware
• Naming-convention aware
• SOQL-aware
• Documentation-aware

Instead of acting like a generic developer, it now behaves more like a trained Salesforce engineer working inside your project ecosystem.

That is the real power of AI-assisted Salesforce development.

1. Introduction to Git

Git may seem confusing initially, but once you understand:

• where the code is stored,
• how code moves,
• how collaboration works,
• and what each command does,

the workflow becomes much easier.

This blog focuses on:

• Git workflow
• Git storage locations
• Core Git commands
• Branching concepts
• Collaboration workflow

2. Common Misconception About Git

Misconception

Many developers think code exists only in:

Local Machine then GitHub/Gitlab, etc.

Reality

Git actually manages code across 4 important locations.

3. Four Main Locations in Git

A. Working Directory

Definition

The Working Directory is:

• your local project folder
• where you actively edit files

It is your:

• coding environment
• development playground

Activities Performed

You:

• create files
• modify code
• delete files
• test changes

Key Point

Changes here are NOT yet tracked permanently.

B. Staging Area

Definition

The Staging Area is:

• a temporary holding area
• where selected changes are prepared before commit

Purpose

It acts like:

• a checkpoint
• a preparation zone

You choose exactly what should go into the next commit.

Important Command

git add

This moves changes from:

• Working Directory → Staging Area

C. Local Repository

Definition

The Local Repository:

• stores committed snapshots locally
• contains Git history

Purpose

It keeps:

• permanent commit records
• version history
• rollback capability

Important Command

git commit

This moves changes from:

• Staging Area → Local Repository

D. Remote Repository

Definition

A Remote Repository is:

• a shared server repository
• hosted on platforms like GitHub or Bitbucket

Purpose

Used for:

• collaboration
• backup
• sharing code with teams

Important Command

git push

This moves changes from:

• Local Repository → Remote Repository

4. Complete Git Workflow

The Git workflow follows a step-by-step movement of code.

Step 1 — Clone Repository

Command

git clone <repository-url>

Purpose

Creates:

• a local copy of an existing repository
• including full history

Flow

Remote Repository → Local Machine

Step 2 — Modify Files

You work inside:

• Working Directory

Activities:

• writing code
• editing files
• fixing bugs

Step 3 — Stage Changes

Command

git add .

or

git add <filename>

Purpose

Moves selected changes into:

• Staging Area

Key Idea

Git prepares a snapshot of files.

Step 4 — Commit Changes

Command

git commit -m “Commit message”

Purpose

Creates:

• permanent snapshot
• version checkpoint

Flow

Staging Area → Local Repository

Step 5 — Push Changes

Command

git push

Purpose

Uploads commits to:

• Remote Repository

Flow

Local Repository → Remote Repository

5. Pulling Team Changes

Git collaboration is:

• two-way communication

Git Pull

Command

git pull

Purpose

Downloads teammates’ latest work.

What Happens Internally?

git pull combines:

1. Fetch

git fetch

Downloads latest updates from remote.

2. Merge

git merge

Integrates fetched updates into local code.

Flow

Remote Repository → Local Repository

6. Git Checkout / Git Switch

Sometimes developers need to:

• switch tasks
• move between features
• fix urgent bugs

Commands

Older Command

git checkout

Modern Command

git switch

Purpose

Switches between branches.

7. Understanding Git Branching

What is a Branch?

A branch is:

• an isolated line of development

It allows developers to:

• work independently
• avoid affecting main codebase

Why Branching Matters

Branching helps:

• feature development
• bug fixing
• experimentation
• team collaboration

without disturbing production code.

8. Important Branching Commands

A. Create Branch

Command

git branch <branch-name>

Purpose

Creates a new branch.

B. Switch Branch

Command

git switch <branch-name>

Purpose

Moves you to another branch.

C. Merge Branches

Command

git merge <branch-name>

Purpose

Combines code from one branch into another.

9. Merge Conflicts

What is a Merge Conflict?

Occurs when:

• two developers modify the same code section

Git cannot decide:

• which version to keep

Resolution

Developer must:

• manually review
• choose correct changes
• resolve conflict

10. Git Collaboration Flow

Typical collaboration cycle:

Clone Repository

↓

Create Branch

↓

Write Code

↓

git add

↓

git commit

↓

git push

↓

Create Pull Request

↓

Code Review

↓

Merge into Main Branch

11. Git Merge vs Rebase (Mentioned Briefly)

The:

• merging
• rebasing

These are advanced workflows used when:

• integrating team changes
• keeping commit history clean

Merge

Combines histories together.

Rebase

Rewrites commit history for cleaner timeline.

12. GUI-Based Git Tools

Not all developers use command line.

Popular Git GUI Tools

1. GitHub Desktop

Visual Git interface by GitHub.

2. SourceTree

Popular Git GUI tool by Atlassian.

Benefits of GUI Tools

They provide:

• visual branch management
• simplified workflows
• beginner-friendly experience

13. Final Git Data Flow Visualization

Working Directory

↓ (git add)

Staging Area

↓ (git commit)

Local Repository

↓ (git push)

Remote Repository

Reverse Collaboration Flow

Remote Repository

↓ (git pull)

Local Repository

↓

Working Directory

14. Key Git Concepts Summary

15. Important Beginner Insights

Git is NOT GitHub

• Git = Version control system
• GitHub = Hosting platform

Commits are Local First

Your commits:

• stay local
• until pushed

Staging Area is Critical

It allows selective commits.

Branches Enable Safe Development

Develop features independently.

16. Best Practices Mentioned Implicitly

Commit Frequently

Small commits are easier to track.

Pull Before Push

Always sync latest team changes.

Use Branches for Features

Avoid working directly on main branch.

Resolve Conflicts Carefully

Never rush conflict resolution.

17. Final Conclusion

Git manages code through:

1. Working Directory
2. Staging Area
3. Local Repository
4. Remote Repository

Understanding how code moves between these locations makes Git much easier.

The core workflow is:

Clone → Edit → Add → Commit → Push → Pull → Merge

Git branching allows:

• isolated development
• safer collaboration
• efficient teamwork

Mastering these basics builds a strong foundation for advanced Git workflows.

Thanks, Subscribe if you like my content, I post frequently for community!

• What
• Why
• Syntax
• Real-life thinking
• Common beginner mistakes
• Shortcut

1. What is Terminal?

Terminal (also called Command Line) is a text-based way to control your computer.

Instead of:

• clicking folders
• dragging files
• using GUI buttons

…you type commands directly.

Think:

Why Developers Use It

Because terminal is:

• Faster
• Automatable
• Powerful
• Universal across servers/cloud/devops
• Needed for Git, Docker, Salesforce CLI, Terraform, Node, etc.

Without terminal skills:

• you become dependent on UI
• automation becomes difficult
• debugging servers/cloud systems becomes harder

2. Understanding the Prompt

Example:

Sanskriti-MacBook:~ user$

This is called the prompt.

It tells:

• who you are
• where you are
• terminal is waiting for command

The $ symbol DOES NOT need to be typed.

3. pwd → Print Working Directory

Purpose

Shows:

“Where am I currently?”

Syntax

pwd

Example

pwd

Output:

/Users/sanskriti

Terminal always works relative to a location.

Before doing anything:

• know current directory
• avoid accidental file operations

Like checking:

“Which room am I currently standing in?”

before searching for an object.

4. ls → List Files/Folders

Purpose

Shows files/folders inside current directory.

Syntax

ls

Example

ls

Output:

Desktop
Documents
Downloads
Movies
Pictures

Editorial Insight

pwd = WHERE you are
ls = WHAT exists there

These two are your survival commands.

5. cd → Change Directory

Purpose

Move between folders.

Syntax

cd folderName

Example

cd Movies

Now terminal enters Movies folder.

Verify

pwd

Output:

/Users/sanskriti/Movies

Editorial Concept

Terminal navigation is hierarchical.

Like:

Users
 └── Sanskriti
      └── Movies

You move deeper using cd.

6. cd .. → Go Back

Purpose

Move to parent folder.

Syntax

cd ..

Why .. ?

.. means:

parent directory

Example

Current:

/Users/sanskriti/Movies

Run:

cd ..

Now:

/Users/sanskriti

Editorial Memory Trick

SymbolMeaning.Current folder..Parent folder

7. clear → Clean Terminal

Purpose

Clears screen clutter.

Syntax

clear

Shortcut:

Command + K

Important

It DOES NOT delete history.

Just visually clears screen.

8. ~ (Tilde)

Purpose

Represents:

Home directory

Syntax

cd ~

Example

No matter where you are:

cd ~

takes you to:

/Users/yourname

This is a shortcut developers constantly use.

Especially in:

• scripts
• configuration files
• Git setup

9. touch → Create File

Purpose

Creates empty file.

Syntax

touch filename.txt

Example

touch notes.txt

Creates:

notes.txt

Important Insight

touch originally updates timestamps.

But commonly used to create files.

10. Tab Completion (SUPER IMPORTANT)

Purpose

Autocomplete names.

Example

Type:

open tes

Press:

Tab

Terminal auto-completes.

Why It Matters

Faster
Avoids spelling mistakes
Essential in long paths

Developers heavily depend on:

• tab completion
• command history
• shortcuts

These save HOURS.

11. open

Purpose

Open file/folder using default app.

Syntax

open filename.txt

Example

open notes.txt

Opens TextEdit.

12. Nano Editor

Purpose

Edit files directly in terminal.

Syntax

nano filename.txt

Example

nano notes.txt

Important Nano Controls

Nano is useful for:

• server configs
• quick edits
• cloud VMs
• Linux systems

When GUI is unavailable.

13. Command History

Purpose

Reuse previous commands.

Shortcuts

See Full History

history

14. rm → Remove File

Purpose

Delete file.

Syntax

rm filename.txt

Example

rm notes.txt

WARNING ⚠️

Unlike Trash:

• terminal deletion is immediate
• usually unrecoverable

15. mkdir → Make Directory

Purpose

Create folder.

Syntax

mkdir folderName

Example

mkdir project

16. Working With Paths

Example:

touch project/file.txt

This creates:

• file.txt
• inside project

WITHOUT entering folder.

Editorial Insight

This is called:

path-based operations

Extremely important concept.

You don’t always need:

cd

17. Recursive Delete

Deleting folders requires:

rm -r folderName

Why -r ?

-r means:

recursive

Delete:

• folder
• files inside
• subfolders inside

Example

rm -r project

VERY IMPORTANT WARNING ⚠️

This command can destroy systems if used carelessly.

Example dangerous command:

rm -rf /

Never run random terminal commands from internet.

Let’s Breakdown this command:

rm

Means:

remove (delete)

Used to delete files/folders.

-r

Means:

recursive

Delete:

• folders
• subfolders
• files inside them

Without -r, folders usually won’t delete.

-f

Means:

force

Terminal will:

• NOT ask confirmation
• ignore warnings
• aggressively delete

/

This symbol means:

ROOT DIRECTORY

The absolute top-level of the operating system.

18. Absolute vs Relative Paths

Relative Path

Relative to current location.

Example:

Documents/file.txt

Absolute Path

Starts from root.

Example:

/Users/sanskriti/Documents/file.txt

Editorial Concept

Most terminal mastery comes from:

• understanding paths
• navigation
• file hierarchy

Mental Model

Think of terminal as:

You are standing somewhere
↓
You inspect surroundings
↓
Then you create/edit/delete things accordingly

MOST IMPORTANT COMMANDS TO MEMORIZE

Terminal Learning Progression

Stage 1

Navigation

• pwd
• ls
• cd

Stage 2

File management

• touch
• mkdir
• rm

Stage 3

Editing

• nano

Stage 4

Productivity

• tab completion
• history
• shortcuts

Stage 5

Advanced DevOps

• grep
• pipes
• permissions
• shell scripting
• git
• docker
• ssh

Real Developer Usage

Terminal is heavily used in:

• Salesforce CLI
• GitHub Copilot workflows
• Terraform
• Kubernetes
• Linux servers
• AI engineering
• Docker
• CI/CD pipelines

Quick Practice Challenge

Try this sequence:

pwd
ls
mkdir demo
cd demo
touch hello.txt
nano hello.txt
ls
cd ..
rm -r demo

If you can execute this confidently, you’ve understood the fundamentals.Mac Terminal, A Quick Editorial

• nano

Stage 4

Productivity

• tab completion
• history
• shortcuts

Stage 5

Advanced DevOps

• grep
• pipes
• permissions
• shell scripting
• git
• docker
• ssh

Real Developer Usage

Terminal is heavily used in:

• Salesforce CLI
• GitHub Copilot workflows
• Terraform
• Kubernetes
• Linux servers
• AI engineering
• Docker
• CI/CD pipelines

Quick Practice Challenge

Try this sequence:

pwd
ls
mkdir demo
cd demo
touch hello.txt
nano hello.txt
ls
cd ..
rm -r demo

If you can execute this confidently, you’ve understood the fundamentals.

Practice Guide:

Terminal gives:

• massive power
• very little protection

GUI apps usually ask:

“Are you sure?”

Terminal assumes:

“You know what you’re doing.”

That’s why professional engineers:

• verify commands
• understand paths
• test carefully
• avoid random internet scripts

Safer Alternative for Beginners

Instead of immediately deleting:

Use:

ls

first to inspect.

Or safer delete:

rm -i file.txt

-i means interactive:

• asks before deleting

Real DevOps Importance

In:

• cloud servers
• Kubernetes
• Terraform
• production Linux machines

One wrong terminal command can:

• bring down infrastructure
• delete databases
• impact customers

That’s why terminal discipline is considered a core engineering skill.

Golden Rule

Before pressing Enter on a terminal command:

Ask:

1. What does this command do?
2. Which path will it affect?
3. Is it recursive?
4. Is it force deleting?
5. Can I recover this?

The Salesforce Spring ’26 Release marks a significant leap toward the vision of an Agentic Enterprise an ecosystem where human expertise and AI agents work together seamlessly. This release is not just an upgrade; it’s a strategic shift designed to empower organizations with intelligent automation, deeper insights, and enhanced customer engagement capabilities.

The Vision: From Automation to Agentic Enterprises

At the core of Spring ’26 lies the concept of Agentforce, Salesforce’s AI-driven evolution. Instead of merely automating processes, Salesforce now focuses on enabling intelligent agents that assist, predict, and act across workflows.

This means:

• Teams make faster, data driven decisions
• Routine work is handled by AI agents
• Human effort is redirected toward strategic outcomes

The result is a smarter, more adaptive enterprise that delivers better customer experiences with confidence.

Key Highlights of the Release

1. Agentforce Platform Expansion

Agentforce is deeply embedded across Salesforce products, enhancing:

• Predictive intelligence
• Generative AI capabilities
• Workflow automation

From Sales (now Agentforce Sales) to Service (Agentforce Service), AI is becoming a built-in collaborator rather than an add-on.

2. AI-Powered Customization & Setup

Admins now benefit from Setup with Agentforce (beta):

• AI-assisted configuration
• Faster setup processes
• Reduced manual effort

This lowers the barrier for complex customizations and accelerates implementation timelines.

3. Enhanced Analytics Ecosystem

Salesforce strengthens its analytics stack across:

• Tableau Next
• CRM Analytics
• Data 360

Organizations can now:

• Generate deeper insights
• Build smarter dashboards
• Enable real-time decision-making

4. Automation Gets Smarter

Automation tools like Flow Builder and Flow Orchestration are enhanced with AI support:

• Intelligent workflow recommendations
• Cross-system integrations
• Supply chain automation via Agentforce

This transforms automation from rule-based to context-aware execution.

5. Experience Cloud & AI Search Optimization

Experience Cloud now introduces:

• AI-powered search optimization
• Improved content discoverability
• Flexible design with expanded components

This ensures better digital experiences for customers and partners.

6. Developer & Deployment Enhancements

Developers gain improvements across:

• Apex, APIs, and Lightning components
• Deployment tools
• Integration capabilities via MuleSoft

The focus is on scalability, performance, and seamless delivery of applications.

7. Hyperforce & Infrastructure Evolution

Salesforce continues expanding Hyperforce:

• Availability in more regions
• IPv6 readiness
• Enhanced IP management

This ensures better compliance, scalability, and global reach.

8. Security & Privacy Advancements

Security remains a priority with updates like:

• Native Backup & Recover
• Privacy Request automation (Right to Be Forgotten)
• Stricter app and API controls

These features help organizations stay compliant and secure in an evolving digital landscape.

Release Readiness: A Strategic Approach

Salesforce emphasizes release preparedness through:

• Pre-release org access
• Release Readiness Trailblazers community
• Sandbox preview tools
• Release in a Box kits

Organizations are encouraged to:

• Test features early
• Train users proactively
• Align release updates with business goals

Why This Release Matters

Spring ’26 is not just about new features, it’s about redefining how businesses operate:

Traditional ApproachAgentic ApproachManual processesAI-assisted workflowsReactive decisionsPredictive insightsTool-based workAgent-driven execution

This shift enables organizations to:

• Scale faster
• Reduce operational overhead
• Deliver hyper-personalized customer experiences

Final Thoughts

The Salesforce Spring ’26 Release represents a pivotal moment in enterprise technology. By combining AI agents with human intelligence, Salesforce is setting a new standard for productivity, innovation, and customer success.

For professionals: especially those in consulting, development, and training, this release demands not just adoption, but strategic understanding. The future of Salesforce is no longer just cloud-based, it is agent-driven, intelligent, and autonomous.

In this Salesforce tutorial, we will learn to manage territories and territory models for opportunities in Salesforce Lightning and Salesforce Classic Edition.

What is Salesforce territory management

In Salesforce, Territory Management is a feature that enables businesses to manage and organize their sales territory effectively. For example, a sales team’s designated geographic region for managing customer accounts and records like opportunity and leads is a sales territory. Salesforce’s Territory Management feature enhances sales processes and ensures managed sales.

Manage Territories and Territory Models for Opportunities in Salesforce Lightning

This section will discuss the territory management of the opportunities for the Salesforce Lightning edition.

Enabling Territory Management in Salesforce Lightning

To enable Territory Management in Salesforce, navigate to Lightning’s Setup page and follow the steps below.

1. On the Setup page of Salesforce Lightning, go to the Quick Find box and search territory, and from the options in the dropdown, select Territory Settings.

In the territory settings window, click Enable Enterprise Territory Management.

2. In this step, select the default access levels for the users in the territory who can access the opportunity.

In this example, I have given all users the view and edit access, irrespective of who owns the opportunity.

3. On the same page, scroll down to the section Opportunity Territory Assignment and select the access for the parent territories. After this activate checkbox, Enable Filter-Based Opportunity Territory Assignment to apply filters during the assignment of territories.

Now, we have successfully enabled the territory management for the org.

How to create Territory Types and Territory Models in Salesforce Lightning

As we enable territory management in the Salesforce environment, Territory Types, and Territory Models will be activated.

1. Go to the Quick Find box and search, then select Territory Types. In the territory types setup window, click the New Territory Type button.

2. In this step, go to the information section and enter the field Label, and the Territory type name will be auto-filled according to the entered label.

After this, you have to enter the priority of the territory type, like 001, 002, 005, 009, and so on. You don’t have to enter the priority in a serial number.

For example, if the company has more sales in Texas, it will be at priority 001, and out of 5 territories, if Colorado has the lowest sales, then we can assign the priority for it as 005, and in between, the sales increased for territory North Carolina then we can assign it as 002.

At last, click on the Save button.

Till now, we have created the Territory types with the relevant priorities. In the further steps, we will create the Territory models and assign the created territory types to them.

3. To create the Territory models, go to the Quick Find box on the setup page, then search and select Territory Models.

In the setup window of territory models, click on the button New Territory Model.

4. Enter the Label for the new territory model, and the Territory Model Name will be auto-filled according to the entered Label field. As of now, the State field will appear as Planning.

At last, click on the Save button.

5. The territory model will be created; click the Activate button to activate it.

As we click on the Activate button, activating will take a while; after activation, the State field will change to Active.

6. After activation, the territory model is ready to use. Here, we will assign hierarchy models to this territory model, and for that, click on View Hierarchy.

7. In the Territory model hierarchy chart, click Create Territory.

8. In this step, enter the below details to create a child territory of the territory model.

• Enter the Territory Label field. For example, I labeled it Opportunity Florida State.
• The Territory Name will be auto-filled according to the entered label.
• In the field Territory type, select the type of territory from the lookup list.
• In the Territory Access Levels section, select the access level for the Opportunity. In this example, I have selected view ads view and edit for the associated accounts of the opportunity.

9. Similarly, we have to create child territories for all the available territory types to have a lookup list of the territories.

After creating territories for all territory types, the hierarchy chart of the Territory model will appear as shown in the image below.

Now that we have created the Territory models, we need to customize the Opportunity Page layout to make the territory field appear in the Opportunity record page.

Add the Territory field to the page layout in Salesforce Lightning

To Add the Territory field to the page layout, navigate to the setup page of Salesforce Lightning and follow the below steps.

1. On the setup page of Lightning, click on the Object Manager tab.

2. Search and select the Opportunity object in the object manager window.

3. In the setup window of the Opportunity object, click on the option Page Layout in the left sidebar. In the next window, click on Opportunity Layout.

4. In the page layout setup, select Fields from the scroll bar at the top, then drag the Territory field to the Opportunity information section and click the Save button to apply changes.

The territory field will be added to the record page layout on applying changes.

5. To view the territory field and assign territory to an opportunity, navigate to an Opportunity record. There, you will see the territory field in the edit window, and from here, you can assign territory to the opportunity.

Now, we have successfully added the Territory field to the page layout of the Opportunity record page.

In this way, We can Manage Territories and Territory models for opportunities in Salesforce Lightning by following the above steps.

Manage Territories and Territory Models for Opportunities in Salesforce Classic

This section will discuss the territory management of the opportunities for the Salesforce Classic edition.

Enabling Territory Management in Salesforce Classic

1. Navigate to the setup page of Salesforce Classic, and in the Quick box, search for Manage Territories, then select Settings under the heading Manage Territories.

2. In the settings window, click on the button Enable Enterprise Territory Management

3. After enabling the enterprise territory management, select the default opportunity access for users in a territory. After that, select the access for the users of the parent territory.

At last, click on the Save button to apply the changes.

Now, we have successfully enabled the territory management for the org. As we enable territory management, two additional fields will be visible: Territory types and Territory models.

How to create Territory Types and Territory Models in Salesforce Classic

To create Territory Types and Models, navigate to Salesforce Classic’s setup page and follow the steps below.

1. On the Setup page, go to the Administrator section in the left sidebar and select Manage territories -> Territory types. We can also access this field from the quick find box.

2. In this window, click on the New Territory type button.

3. To create a territory type, enter the Label for territory; this label can be any geographical division like city, state, or region. In this example, I have entered the label as Arizona State, and the Territory Type Name will be auto-filled according to the entered label.

After this, we have to set the priority of the territory type. For this territory type, I have set it as 3. At last, click on the Save button.

The priority in the territory is defined according to the performance ranking in any aspect. For example, if the company has the highest sales in Michigan, it will be at priority 001. In the same way, out of all territories, if Colorado has the lowest sales, we can assign the priority as 005 or any lowest number according to the number of territories in the org.

In the further steps, we will create the Territory models and assign the created territory types to them.

4. To create the Territory models, go to the left sidebar on setup, and in the section Administrator, select Manage territories -> Territory Models.

In the setup window of territory models, click on the button New Territory Model.

5. In this step, enter the label for the territory model, and the Territory Model Name field will be auto-filled according to the entered Label.

At last, click on the Save button.

6. Now, the territory model is created, and to add child territory to the territory model, click on View Hierarchy.

7. To add territories in the territory model, we first need to activate the territory model, and for that, click on the Activate button.

It might take some time to activate, and after activation, click Create Territory.

8. Enter the following fields to create the territory for the territory model.

• Enter the Territory Label field. For example, I labeled it Colorado Opportunity.
• The Territory Name will be auto-filled according to the entered label.
• In the field Territory type, select the type of territory from the lookup list.
• In the Territory Access Levels section, select the access level for the Opportunity. In this example, I have selected view ads view and edit for the associated accounts of the opportunity.

In the same way, you have to create child territories for the territory types available in your organization.

9. The hierarchy chart will look as shown below after adding child territories to the territory model.

We have created the Territory models, now we need to customize the Opportunity Page layout to make the territory field appear in the Opportunity record page.

Add the Territory field to the page layout in Salesforce Classic

To add the Territory field to the page layout of the opportunity, navigate to the setup page of Salesforce Classic and follow the below steps.

1. On the setup page of Salesforce Classic, go to the build section in the left sidebar and select Customize -> Opportunites -> Page Layouts.

2. In the page layouts, select the default opportunity page layout.

3. In the Opportunity page layout setup, select Fields from the scroll bar at the top, then drag the Territory field to the Opportunity information section and click the Save button to apply changes.

4. To view the territory field and assign territory to an opportunity, open the Opportunity tab and edit or create an opportunity record. There, you will see the territory field in the form, and from here, you can assign territory to the opportunity.

Now, we have successfully added the Territory field to the page layout of the Opportunity record page.

In this way, We can Manage Territories and Territory models for opportunities in Salesforce Classic by following the above steps.

Conclusion

In Salesforce, territory management is very crucial when it comes to managing sales in the organization. We can enhance our sales process by assigning territories to opportunities, leads, and accounts.

In the above steps, we have learned about managing territories and territory models for Opportunities in Salesforce. In that process, we learned to enable territory management, creating Territory models and Types. After that, we added the territory field to the page layout of the Opportunity object.

If your feed is flooded with updates on a post you no longer want to follow, muting is your best friend.
Let’s explore how it works and test your knowledge with a quick MCQ!

The Concept💡

The Mute Post feature in Chatter lets users stop receiving updates or notifications about specific posts in their feed.

When you mute a post:

• You won’t get updates when others comment or like it.
• The post still remains visible in the feed (it’s not deleted or hidden).
• If someone @mentions you in the same post, it automatically unmutes for you again, so you don’t miss anything relevant.

In short you’re not removing yourself from the post, just pausing notifications until it matters again.

Implementation

To mute a post:

1. Click the dropdown arrow (⋮) on the post.
2. Select Mute.
3. Done : you’ll no longer receive notifications for that thread.

If later someone @mentions you again, the post becomes unmuted automatically — ensuring you’re looped back in.

Purpose

The goal is to reduce feed noise while keeping control over important updates.

It helps users:

• Stay focused on relevant conversations.
• Avoid unnecessary alerts from highly active threads.
• Re-engage automatically if tagged again.

The MCQ

Question:
An inside sales rep doesn’t want to keep receiving updates on a busy Chatter post. The Salesforce Admin suggests muting it. What’s true about the Mute Post feature?

Options:
A. A muted post will be unmuted for a user who is @mentioned in the post
B. Muted posts cannot be viewed after they have been muted
C. Muting a post removes it from all feeds
D. Posts can only be muted from Setup

Correct Answer: A. Muted post will be unmuted for a user who is @mentioned in the post

Why it’s correct:
When a user is tagged or mentioned in a muted post, Salesforce automatically unmutes it for them to ensure they don’t miss key updates.

Why others are incorrect:

• B. Muted posts can’t be viewed: False — muted posts still appear in feeds.
• C. Removes from all feeds: False — it only stops updates, not visibility.
• D. Only from Setup: False — users mute posts directly from the post dropdown menu (⚙️ → Mute).

Objective Mapping

Exam Objective (Salesforce Admin Exam):
Collaboration and Productivity → Describe Chatter features, post visibility, and feed settings.

Practical Objective:
Enable users to manage feed clutter effectively while staying responsive to direct mentions.

⚙️ 🔗 Salesforce Reference

Salesforce Help: Mute a Post

Quick Takeaway

“Mute” doesn’t mean goodbye : it just means “Not now”!

Stay focused, reduce noise, and let @mentions pull you back when needed.

For more Salesforce productivity tips and admin insights — 
Follow me on LinkedIn ✨

Sometimes, the child doesn’t need its own access settings because it inherits everything from the parent.
That’s the magic of Controlled by Parent.

The Concept 💡

Organization-Wide Defaults (OWD) set the baseline access for all records in an org.

When you choose “Controlled by Parent” for a child object (like Contact under Account), Salesforce automatically applies the parent record’s sharing settings.

In short:
If a user has access to an Account, they’ll have the same access level (Read/Edit/Delete) to all Contacts linked to that Account.

No need to create additional sharing rules!

Purpose

This setting is ideal when:

• You want consistent sharing behavior between related objects.
• Contacts, Cases, or Orders are logically tied to their parent Accounts.
• You want Account owners to control all related records automatically.

It reduces complexity, prevents redundant sharing rules, and ensures that data security aligns with business hierarchy.

⚙️ Real-Life Implementation

To configure this:

Go to Setup → Sharing Settings → Under “Default Internal Access,” → set Contact = Controlled by Parent.

Click Save.

This ensures Account owners can view and edit all Contacts linked to their Accounts automatically and securely.

The MCQ

Question:
Users need edit access to all Contacts associated with Accounts they own. Which OWD sharing setting can meet this requirement?

Options:
A. Private
B. Controlled by Parent
C. Public Read/Write

Correct Answer: B. Controlled by Parent

Why it’s correct:
With Controlled by Parent, Account owners automatically gain the same access level to their related Contacts — no need for manual sharing.

Why others are incorrect:

• A. Private: Restricts access to record owners only — not suitable.
• C. Public Read/Write: Allows all users org-wide to edit Contacts — too permissive.

Objective Mapping

Exam Objective (Salesforce Admin Exam):
Security and Access → Explain how OWDs determine baseline record access and when to use “Controlled by Parent.”

Practical Objective:
Implement secure, scalable data-sharing models by leveraging parent-child access inheritance for related objects.

🔗 Salesforce Reference

• Salesforce Help: Define Organization-Wide Defaults
• Salesforce Help: About Sharing Settings

Quick Takeaway

“Controlled by Parent” = Access inheritance simplified.

“Let the Account decide — who sees and edits its Contacts.” 👑

For more Salesforce insights and exam prep stories — 
Follow me on LinkedIn ✨

Let’s unpack how list view sharing really works in Lightning Experience, followed by a quick test of your understanding.

The Concept 💡

List Views help users filter, organize, and display records that meet specific criteria.
When creating a list view, you see the “Who sees this list view?” section, which controls visibility.

The available sharing options depend on user permissions. specifically, whether the creator has the ability to make list views public.

If a user doesn’t have the Manage Public List Views permission, they can only create private list views visible to themselves.

Purpose

This design ensures that only authorized users (like admins or power users) can create or share list views across teams or roles maintaining control over org-wide data visibility.

It helps:

• Prevent unauthorized sharing of sensitive data
• Maintain clean and standardized views for all users
• Empower admins to manage data access efficiently

Admins can check or grant permissions via Setup:

(See image: This permission controls whether users can share list views publicly.)

The MCQ

Question:
A user created a new list view and wants to share it with a colleague. Which statement correctly describes list view sharing settings?

Options:
A. The user who created it always has the option to share it publicly
B. The option to share it to all users is always available
C. It depends on whether the creator has the required permission via profile or permission set
D. Only the creator can access it at any time

Correct Answer: C. It depends on whether the user creating the list view has the necessary permission via their profile or permission set

Why it’s correct:
Only users with the “Manage Public List Views” permission (from their Profile or Permission Set) can share a list view with all users, specific roles, or public groups.

Why others are incorrect:

• A. Always has option: Not true : depends on permissions.
• B. Always available: No, sharing options are restricted by security settings.
• D. Only the creator can access: Incorrect : list views can be shared if permissions allow.

Objective Mapping

Exam Objective (Salesforce Admin Exam):
Object Manager and Lightning App Builder → Describe how to create, modify, and share list views.

Practical Objective:
Understand the impact of administrative permissions on sharing and collaboration within Salesforce UI customization.

⚙️ Real-Life Implementation

In real-world orgs, this comes into play when:

• Sales managers want to share pipeline views with teams.
• Service leaders share open case lists with specific queues.
• Admins standardize common record filters across departments.

🔗 Salesforce Reference

Create or Edit List Views in Lightning Experience

Quick Takeaway

Not all users can share list views and that’s a good thing.

“If you can’t see the ‘Who sees this list view?’ option, check your permissions, not your patience.” 😉

For more quick Salesforce insights and admin prep tips — 
Follow me on LinkedIn ✨

That’s where Outlook Integration comes in. Let’s break it down, and then test your understanding with an MCQ.

The Concept 💡

Outlook Integration connects Salesforce with Microsoft Outlook and Exchange, letting users relate emails, events, and contacts directly to Salesforce records.

This integration adds a Salesforce side panel inside Outlook, showing contextual CRM data like Accounts, Contacts, Opportunities, and Cases, next to every email.

Admins can also pair it with Lightning Sync (now replaced by Einstein Activity Capture) to sync contacts and events automatically.

Purpose

The purpose is simple:

Empower reps to work smarter, not harder keeping Salesforce data updated straight from Outlook.

This integration helps:

• Reduce manual data entry
• Keep CRM data accurate in real-time
• Improve adoption by letting users stay in Outlook while keeping Salesforce records fresh

The MCQ

Question:
Global Technologies wants to let sales reps relate emails, contacts, and events in Outlook and Exchange with Salesforce records. What should the admin configure?

Options:
A. Lightning Sync
B. Outlook-Salesforce Extender
C. Salesforce for Outlook
D. Outlook Integration

Correct Answer: D. Outlook Integration

Why it’s correct:
Outlook Integration is Salesforce’s modern, Lightning-compatible solution that allows users to relate Outlook items (emails, events, contacts) directly to Salesforce records.

Why others are incorrect:

• A. Lightning Sync: Retired; replaced by Einstein Activity Capture.
• B. Outlook-Salesforce Extender: No such Salesforce feature exists.
• C. Salesforce for Outlook: Legacy product — retired and unsupported in Lightning Experience since Winter ’21.

Objective Mapping

Exam Objective: Productivity and Collaboration
Detailed Objective: Describe the capabilities of activity management and email integration in Salesforce.

Real-Life Implementation

Admins can set it up from:

Then, users simply install the Salesforce Add-In from the Microsoft AppSource store.
Once enabled, reps can:

• Relate Outlook emails or events to Accounts, Opportunities, or Cases.
• Log interactions to Salesforce with one click.
• Access CRM insights without switching tabs.

(Emails and events can be related to Salesforce records directly within Outlook.)

🔗 Salesforce Reference

• Salesforce Help: Set Up Outlook Integration
• Trailhead: Learn Outlook Integration

Quick Takeaway

With Outlook Integration, sales reps don’t just send emails they build relationships and keep Salesforce data accurate at the same time.

“One inbox. One CRM. Double productivity.”

For more Salesforce admin insights and certification prep — 
Follow me on LinkedIn 💬

Let’s explore this concept and test your understanding with a quick MCQ below.

The Concept 💡

When you delete a custom field in Salesforce, it’s not gone forever immediately.
Salesforce moves deleted fields to a “Deleted Fields” section in the object manager, where they remain recoverable for 15 days.

After that 15-day period, the field along with all its stored data is permanently erased.

Here’s what else happens when you delete a field:

• All dependent fields or field dependencies are removed.
• Any formulas, workflows, or rules referencing the field are impacted.
• You’ll see a warning message before confirming deletion.

Purpose

The goal behind this retention window is to provide admins a grace period to recover accidentally deleted fields, ensuring no critical business data is lost prematurely.

This safeguard allows you to undo mistakes before permanent loss.

The MCQ

Question:
An administrator deletes a custom text field on the Account object. What is true regarding a deleted field?

Options:
A. It can be recovered within 15 days of deletion
B. It can be recovered within 30 days of deletion
C. It can never be recovered
D. It can be recovered at any time

Correct Answer: A. It can be recovered within 15 days of deletion

Why it’s correct:
Salesforce retains deleted custom fields in the “Deleted Fields” list for 15 days, during which you can undelete them with all their data intact.

Why others are incorrect:

B. 30 days: The retention period is 15 days, not 30.

C. Never recovered: False — recovery is possible within the grace period.

D. Recovered any time: Once 15 days pass, both field and data are permanently deleted.

Objective Mapping

Practical Objective: Understand field management and recovery within the Object Manager.
Exam Objective (Salesforce Admin Exam):
Object Manager and Lightning App Builder → Explain how to create, delete, and restore fields and their implications.

Real-Life Implementation

In real-world orgs, this knowledge saves you from panic moments when someone deletes a critical field.
Admins can simply head to:

Always remember to perform a Data Export before deleting important fields to preserve historical data.

🔗 Salesforce Reference

Managing Deleted Fields in Salesforce

Quick Takeaway

Deleting a field isn’t always final: Salesforce gives you 15 days to change your mind.
Use that safety net wisely before making permanent changes.

For more Salesforce admin tips and certification insights — 
Follow me on LinkedIn ✨