Publisher
Publisher in Salesforce has two distinct meanings depending on context.
Definition
Publisher in Salesforce has two distinct meanings depending on context. In Chatter and Experience Cloud, the Publisher is the user (or system) that creates and shares a feed post, a Knowledge Article, a Question, or any other piece of content in a feed or community. The Publisher record is the author identity attached to the content, and the Publisher permissions, profile, and role determine what content they can create and how it gets surfaced to readers.
In the AppExchange and managed packaging context, a Publisher is the Independent Software Vendor (ISV) that builds and ships a managed package to Subscriber organizations. The Publisher maintains the source-of-truth Salesforce org (the License Management Org or LMO), owns the package metadata, controls the release cadence, and provides support to Subscribers. Both meanings show up on Salesforce certification exams; understanding which one is in play depends on the surrounding context.
Publisher in Salesforce: two meanings, both worth knowing
Publisher in Chatter and Experience Cloud
The Chatter Publisher is the user who creates a feed post, a comment, a Question, an Answer, or an attached file. Every feed item has a CreatedById that points to the Publisher User record. The Publisher permissions determine what they can post and where; feed-level sharing rules determine who can see what they post. Experience Cloud extends the concept to external users (Customer Community, Partner Community licenses) who publish into the community feeds and articles. Knowledge Articles also have a Publisher identity, with the Publishing Status field tracking the workflow from Draft to Published to Archived. The Publisher of a Knowledge Article is the user with the Publish Articles permission who promoted it to Published status; that user identity is preserved on the article record.
Publisher in AppExchange managed packaging
The AppExchange Publisher is the ISV that owns a managed package. The Publisher operates the License Management Org (LMO), which is a separate Salesforce org where the License Management Application (LMA) lives. From the LMO, the Publisher tracks every Subscriber Organization that has installed the package, every License record per Subscriber, and every active version of the package. The Publisher controls the release cadence: new package versions are uploaded from the LMO, propagated to AppExchange, and pulled (or pushed) into Subscriber orgs. The Publisher also provides support through the Subscriber Support Console, where a Publisher engineer can log into a Subscriber Org with the customer explicit consent. Becoming a Publisher requires registering with the Salesforce Partner Program and passing a security review for each managed package listed publicly.
The Chatter Publisher component and feed posting
Beyond the user identity, Chatter Publisher also refers to the UI component that lets a user compose a post. The Chatter Publisher (component) appears at the top of any feed and lets the user write text, attach files, mention other users, add Topics, and select the audience (a group, a record, the company feed). Lightning App Builder exposes the Chatter Publisher component, so admins can place it on record pages, home pages, or Experience Cloud sites. The component is customizable through Publisher Actions, which let admins add custom Quick Actions (Create a Task, Log a Call, Create a Case) that appear in the Publisher alongside the post button. The component is the way most users interact with the feed.
Publisher Actions and the Quick Action toolkit
Publisher Actions extend what the Chatter Publisher component can do. Standard Publisher Actions include Post, File, Link, Poll, Question, Thanks, and Announcement. Custom Publisher Actions let admins add object-specific shortcuts: Create a Task on this Account, Log a Call on this Opportunity, Create a Case on this Contact. Each Publisher Action is a Quick Action under Setup, with field defaults, target object, and visibility rules per profile. Lightning Experience and the Salesforce Mobile App use the same Publisher Actions framework, so an action defined once appears on the Chatter Publisher component everywhere it is enabled. Mature orgs curate the Publisher Action set carefully; cluttering it with too many actions degrades the user experience and slows down the most common task (posting to the feed).
Publisher Permissions and the publish workflow
Different content types require different permissions. Posting to a feed requires Read access to the feed location (an Account record, a Chatter group, the company feed). Publishing a Knowledge Article requires the Publish Articles permission plus access to the Article Type. Publishing content in Experience Cloud may require role-based community access and specific record-level sharing. Each publish action is logged with the Publisher identity, the timestamp, and the action type. Audit logs in the org show the full publish history per Publisher, which compliance teams use for content reviews. Train Publishers on the publish workflow at onboarding; users who do not understand the visibility model often publish content to the wrong audience and have to recall it manually later.
Why the two Publisher meanings matter and when to disambiguate
The two meanings of Publisher (Chatter user, AppExchange ISV) overlap rarely but cause confusion in cert prep, documentation, and conversations between teams. The platform documentation usually disambiguates with explicit context (Chatter Publisher versus AppExchange Publisher), but informal references just say Publisher and assume the listener gets it. The cleanest way to handle this in your own documentation is to use the full form on first mention in a section, then the short form thereafter. In Salesforce certification questions, the surrounding context (Sales Cloud topics versus ISV Partner topics) makes the meaning obvious. When you encounter Publisher in a Salesforce context for the first time, check which world you are in: ISV managed packaging, or end-user content collaboration.
Configuring Publisher functionality across Chatter, Knowledge, and Experience Cloud
Configuring Publisher functionality depends on which Publisher you mean. For the Chatter Publisher component (the most common case), the four-step routine covers: enable Chatter and the Publisher component, curate the Publisher Actions, customize the Publisher per record type, and govern Publisher Permissions for Knowledge and Experience Cloud. For the AppExchange Publisher (ISV) role, the work is a separate multi-month project involving Partner Program registration, LMA setup, and security review. This guide covers the Chatter Publisher path; ISV setup is documented separately in the Salesforce ISV Architecture Decision Guide.
- Enable Chatter and the Publisher component
From Setup, search Chatter Settings, and confirm Chatter is enabled at the org level. Open Lightning App Builder and add the Chatter Publisher component to the relevant record pages and home pages. The component is small but loads dynamically based on the user posting permissions, so a user who cannot post sees a read-only version. For Experience Cloud sites, add the Chatter Publisher component through Experience Builder. Test the component as a target user on each page to confirm it appears and accepts posts as expected.
- Curate the Publisher Action set per object
For each object that has a Chatter feed (Account, Contact, Opportunity, Case, custom objects), review the Publisher Actions enabled on the object. Open Setup, Object Manager, the object, Publisher Layout. Add Quick Actions that match the user most common follow-up tasks on that record (Create Task, Log Call, Create Case). Remove actions that clutter the Publisher without adding value. Order the actions by frequency. Test as a target user before saving. Document the Publisher Action set per object in the user-experience runbook so future changes do not regress.
- Customize the Publisher per record type
For objects with multiple record types (Account with Customer, Partner, Prospect; Opportunity with New Business, Renewal, Upsell), configure separate Publisher layouts per record type. The user sees different Publisher Actions depending on the record type they are looking at. This lets a Renewal Opportunity show different actions (Send Renewal Quote) than a New Business Opportunity (Create Proposal). Configure each layout from the Object Manager Page Layout assignment matrix. Validate by switching record types and confirming the Publisher Action set changes accordingly.
- Govern Publisher Permissions for Knowledge and Experience Cloud
For Knowledge Articles, configure the Publish Articles permission carefully. Grant it only to users who own the article quality (Knowledge managers, technical writers, content leads). Build an article publication workflow that includes peer review before publish. For Experience Cloud, configure community member roles so external publishers (partners, customers) can post content within the limits of their license and sharing rules. Audit Publisher activity quarterly through the org Activity History reports. Adjust permissions or training based on what the audit reveals.
- Publisher in Chatter and Publisher on AppExchange are different concepts entirely. Cert exam questions sometimes leverage the ambiguity; read each question surrounding context to identify which world is in play.
- Publisher Actions are layout-driven. Adding a Quick Action to the org does not make it visible in the Publisher unless you also add it to the relevant Publisher Layout per object and record type.
- Knowledge Article Publishing requires the Publish Articles permission. Standard System Administrators have it by default; rank-and-file users may not. Without it, articles stay in Draft status indefinitely.
- Experience Cloud Publishers operate under license-specific limits. Customer Community licenses restrict what external Publishers can do; check the license entitlements before promising external publishing capability.
- AppExchange Publisher (ISV) status requires Partner Program registration and a per-package security review. Becoming an ISV is a months-long project, not a quick configuration.
Trust & references
Straight from the source - Salesforce's reference material on Publisher.
- Chatter OverviewSalesforce Help
- Quick Actions OverviewSalesforce Help
- License Management Application OverviewSalesforce Developer Docs
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. Who is a Publisher in Chatter?
Q2. Why track publishers?
Q3. What can publisher data reveal?
Discussion
Loading discussion…