Editorial policy

Who writes this site

Last updated: May 14, 2026

Salesforce Dictionary is written and edited by Dipojjal Chakrabarti, an Enterprise Solution Architect at Accordion with 13+ years of hands-on Salesforce experience and 29 Salesforce certifications spanning Admin, Developer, Consultant, Architect, and Marketing tracks. Every term you read here has been touched by someone who has shipped that feature in a real org.

Contributing experts and reviewers are credited on the pages they help shape. We do not accept paid placements, sponsored definitions, or vendor-written content.

Source hierarchy

Every definition follows a clear order of reference:

1. Official Salesforce documentation. Salesforce Help, the Architect Centre, developer guides, and the trust documentation are authoritative. When official docs and a community post disagree, we follow the docs.
2. Trailhead modules. Used for foundational concepts and learning paths.
3. Salesforce release notes. Used to confirm which release a feature shipped in and to flag deprecations or retirements.
4. Hands-on testing in a sandbox. Whenever behaviour can be tested directly, we test it before publishing.
5. Reputable community sources. Salesforce Stack Exchange, Salesforce Ben, official partner blogs, and well-known practitioner accounts on LinkedIn and X. We cite where relevant.

External sources are linked on every term page under “Sources” or “Learning resources” so you can verify what we’ve written and dig deeper.

Review and quality bar

• Every term page is written by, or reviewed by, a Salesforce-certified author before publishing.
• Code samples are syntactically valid Apex, SOQL, LWC, or whichever language the term covers, and follow current best practices.
• Worked examples use plausible business scenarios, not templates copied across terms. We periodically audit for repetition and rewrite any definition that reads as generic.
• Each page carries a “Last reviewed” date that reflects the most recent verification against Salesforce’s current behaviour.
• When a feature is renamed, deprecated, or retired, we mark the affected pages and link to the replacement.

Updates and release coverage

Salesforce ships three major releases a year (Spring, Summer, Winter) plus interim feature drops. Within two to four weeks of each release, we revisit affected definitions and update them. New features get their own term pages as soon as they reach general availability, and beta features are tagged as “beta” in our status field so you know to verify.

Corrections

We get things wrong sometimes. When we do, we want to know.

• Use the feedback widget on any term page to flag an issue.
• Or email support@salesforcedictionary.com with the URL and the specific issue.

We aim to triage within 5 business days. Significant factual corrections (not typos) are noted in the page’s revision metadata so readers can see what changed.

Independence and conflicts

Salesforce Dictionary is an independent reference site. It is not affiliated with Salesforce, Inc. We do not accept money to feature, rank, or favourably review any product or vendor. Advertising on the site (where present) is served programmatically by Google AdSense; ad placement does not influence editorial choices. See our Disclaimer for the full statement.

AI in our workflow

We use AI tools to speed up drafting, brainstorming, and cross-checking. We do not auto-publish AI output. Every page passes through a certified human editor before going live. The full policy is on the AI Policy page.