Skip to main content

Learning Path for Salesforce

About Us
Published by JET BI
06 September 2023
36

Learning Path - Salesforce function

 

Salesforce has a special function called Learning Path. This function is hardly frequently used in Salesforce CRM, and it appears that few people are aware of it. 

If you want to integrate a learning library within the Salesforce app, Learning Path is fantastic. Users or administrators have the option to assign to a specific user a Trailhead module and set a deadline for completion of the assignment.


Additionally, you may provide links to customised learning or private modules from your company's my trailhead self domain. Users get access to information on the modules that are suggested to them, necessary for them to complete, working on at the moment, and those that have already been completed.

Although it is not frequently utilised by Salesforce developers, this Salesforce function is crucial for helping to enlighten end users about Salesforce. Utilising the Learning Path only requires a few simple actions. Administrators can choose the Salesforce applications and object pages on which the trailhead module will appear as well as which user categories it will be shown for. It’s available for Standard and custom Salesforce Apps. But keep in mind that Salesforce Administrators can only assign modules with quizzes; no practical exercises are allowed. Administrators have the option of assigning the module to all users, a certain subset of users, or none at all. 

After assignment, users can see modules that have been assigned to them  on the Learning Home page. Some screenshots have been attached to this article to give you more insight.



 

Details are available here in Salesforce Documentation.

Interested in Salesforce implementation or Salesforce Development? 
Please contact us for a quote.


Mary Osobe
Salesforce Certified Administrator
image
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026