The Salesforce Partner Console is the publishing back office every ISV uses to take a managed package from built to listed. In one place you connect your orgs and packages and set default licenses. You also run the security review, publish the listing and read Marketplace Analytics. Salesforce's ISVforce Guide now calls it the AgentExchange Partner Console, "the complete business management site for ISV partners and consultants with AgentExchange listings." Most SaaS teams still search for it under its older AppExchange name.
For a SaaS company deciding how to get a native Salesforce app built, listed and maintained, the console is where the work turns into a business. It decides how quickly a new customer can install, which installs become licenses, and which listing visits reach your sales team as leads. Appnigma builds native apps for SaaS teams. Its marketplace apps projects include the app itself plus "marketplace listing preparation, and review support." The console itself stays in your company's partner account, so this guide covers what your team owns there. If you want the marketplace itself explained for buyers, read what the Salesforce AppExchange is instead.
Updated October 2026. Checked against the current ISVforce Guide, which names the console and marketplace AgentExchange. The earlier version described a "Publisher Notification Queue" and a "Self-Review Wizard" that auto-approves new versions, which no current Salesforce page describes. It also treated the Partner Business Org and License Management Org as two separate orgs and printed review fees and marketplace percentages without a source. This update replaces those with Salesforce's own wording and adds access rules, the setup order, post-review upkeep and the analytics traps that cost leads.
Where the console sits next to your Partner Business Org
Three Salesforce surfaces run an ISV business, and teams lose days confusing them. The Partner Community is where people log in and get permissions. The Partner Console is the publishing site you open from the Partner Community by clicking Publishing. The Partner Business Org (PBO) is a real Salesforce production org, provisioned when you join, that holds your business tools.
| Surface | What it is | What your team does there |
|---|---|---|
| Partner Community | The partner login site at partners.salesforce.com | Manage users, assign the Manage Listings permission, log cases, open the console |
| Partner Console | The publishing site behind the Publishing tab | Connect orgs and packages, register licensing, run security review, build listings, read analytics |
| Partner Business Org | An internal-use production org with "two Sales & Service Cloud Enterprise Edition licenses and pre installed tools" | Receive leads and licenses in the License Management App, report orders, manage environments, host your Dev Hub |
The License Management Org is not a third org you request. Salesforce's PBO reference lists the License Management App (LMA) among the PBO's preinstalled tools, and the org holding the LMA is called the LMO. So for most ISVs the PBO and the LMO are the same org. The connect-your-PBO page says to connect whichever org holds the LMA, Channel Order App and Environment Hub "if those tools are installed in an org other than your PBO."
Who on your team needs Partner Console access?
Access takes two things. Each person needs a Salesforce Partner Community login and the Manage Listings permission, according to Access the AgentExchange Partner Console. A Partner Community user with Manage Users assigns it from the Manage Users page. The permission lives in the Partner Community, not in your PBO's Setup, and a person without it can't open the console at all.
The permission is all or nothing. Salesforce's analytics access FAQ answers the question of analytics-only access with a plain "No," because Manage Listings "provides access to all Partner Console features." A marketer you add to watch tile views can also edit, submit and publish listings. Most SaaS teams give it to two or three owners of the listing and share analytics through the CSV export instead.
Contacts matter as much as logins. In Company Info you set a business, marketing, technical and security review contact, and Salesforce recommends group addresses so a departure doesn't break the chain. The security review contact is the one that gets re-review notices, so a personal inbox there is a real risk to your listing.
What each area of the Partner Console does
Salesforce documents the console by task, not as a tab tour, so the table below maps each documented task to where it lives. Every row links to the page it comes from.
| Area | What you do there | Source |
|---|---|---|
| Home, Analytics | Marketplace Analytics per listing, with tile views, tile hovers, visitors, lead events and installs over the past 30 days by default | Navigate to Marketplace Analytics, Activity Summary |
| Company Info | The public company profile shown in Provider Details, plus the internal contacts only Salesforce sees | Company profile |
| Technologies (Solutions, Orgs, Trial Templates) | Connect your PBO and the Dev Hub or packaging org, register a package for licensing, check Listing Readiness, start a security review | Connect your solution, Start a review |
| Listings | The Listing Builder, where you pick a listing type, write the listing, set pricing, link the solution, set up lead collection and submit for approval | Listing Builder |
Two recent additions change the work in the Listings area. LLM-Assisted Authoring reads a connected managed package and drafts the listing copy, including the SEO title. Salesforce adds that "you're responsible for reviewing and approving the accuracy" of the result. Listing types now include an Agentforce Solution option alongside Salesforce App, Flow Solution, Bolt Solution and Lightning Component, per Select a Listing Type.
The order SaaS teams work through the console
Getting a managed package listed takes seven Partner Console steps, and Salesforce documents each one on a separate page without showing how they depend on each other. Working in this order avoids the usual stall, where a listing waits on a security review that is itself waiting on a company profile.
| Step | What it needs first | Why the order matters |
|---|---|---|
| 1. Company profile and contacts | Partner Community login, Manage Listings | The security review page lists a provider profile as a precondition |
| 2. Connect the PBO (or the org with the LMA) | PBO credentials | Default licensing can't be set until the LMA org is connected |
| 3. Connect the Dev Hub or packaging org | A managed-released package version | The version must be visible in Solutions before review or licensing |
| 4. Register the package and set default licenses | Steps 2 and 3 | Sets each install to Free Trial (up to 90 days) or Active, per seat or site-wide, per default licensing |
| 5. Start the security review | Steps 1 and 3, a Lightning Ready solution | Runs in the security review wizard from the Solutions page (our security review guide covers what it tests) |
| 6. Build the listing | A listing type you can't change later | You can link a solution "undergoing security review, but you can't publish" until it passes |
| 7. Get approved and sign the PADA | Pricing set | Checkout listings sign a clickthrough Partner Application Distribution Agreement, other paid listings sign it offline, per listing approval |
Steps 5 and 6 can run in parallel, and that is where most calendar time is won. Your marketing lead writes and gets approval on the listing while the package sits in the review queue. When the review passes, the solution's Listing Readiness value changes to Ready to List and the listing can go live without another round of edits.
One practical detail trips teams up at step 4. When you register the package, the console asks for the LMA org's password with the security token appended, so "ABC" plus token "123" becomes "ABC123." Have an admin with that token on hand before you start.
What happens in the console after your first version passes review?
Once a managed package passes the AgentExchange security review, new versions of it don't need the full review again. Salesforce's periodic re-review page says that when you upgrade a version that passed, "you don't go through the full review process again," and you can associate the new version with the listing straight away. There is no separate approval wizard for this. The listing readiness rules say an unreviewed 2GP version inherits readiness from its ancestor, which must be the highest managed-released version. A version you created before the earlier one passed gets "Your new version isn't ready to list." Check the Listing Readiness value in Technologies, Solutions before you promise a customer a release date.
Version numbering decides how far that inheritance reaches. The review overview warns that "with patches, security review inheritance is limited" and advises submitting major and minor versions such as 1.0.0 and 1.1.0. For a SaaS team shipping customer fixes every few weeks, that is a release-planning rule, not a packaging detail. Batch fixes into minor versions you intend to list.
Salesforce also runs periodic re-reviews based on risk and time since listing, and fees apply. When one is due, the security review contact gets an email and the version's status changes to Start Review. If a re-review fails, Salesforce gives "typically 60 days" to fix the issues before it may pull the listing. A failed initial review leads to a follow-up review, which "takes up to 4 weeks" after verification and carries a retest fee. Check the wizard for the current amount rather than relying on a figure from an older blog post.
How to read Marketplace Analytics without misreading your funnel
Lead events and leads are different numbers, and the gap is where SaaS teams lose pipeline without noticing. Salesforce's lead events FAQ counts a lead event when a visitor watches a demo or takes a test drive. Chat, a Get It Now click and an install count too. Only some of those become lead records in your org.
Three causes explain most of the gap. Custom lead routing rules can drop or merge them, customer contact preferences can suppress them, and Web-to-Lead reCAPTCHA can block them. The lead collection setup requires a standard org rather than a Developer Edition org, with Web-to-Lead enabled and "Require reCAPTCHA Verification" turned off. If lead events run well ahead of leads, check those three settings before you blame the listing copy. Even a well-run listing is a discovery channel, and as Appnigma's own marketplace page puts it, "not a promise of inbound leads."
Installs tell a second story. A lead event from an install should match a license record in your LMA, because license records generate "only when a customer installs your solution." If installs climb but licenses don't, the package version probably isn't registered. Read tile views against visitors to judge the listing title and tile copy, and read visitors against lead events to judge the listing page itself.
Plan reporting around three limits. Marketplace Analytics data "is updated one time per day," so a launch-day spike shows up tomorrow, per the refresh FAQ. There is no API, only a CSV export of six files, so a weekly pull into your own BI tool is the usual workaround. Top searches show only the 10 AgentExchange search terms that drive the most activity, and "search terms from external search engines aren't available," per the top searches page.
Did the Partner Console change when AppExchange became AgentExchange?
The name changed and the login path didn't. Salesforce launched AgentExchange in March 2025 as a marketplace for Agentforce. In April 2026 it became one storefront for AppExchange apps, Slack apps and agents. Salesforce's docs now title the pages "AgentExchange Partner Console," and you still reach it by logging in to the Partner Community and clicking Publishing. Listings, Solutions, security review and Company Info work the same way under the new name.
What did change for ISVs sits inside the Listing Builder. Agentforce Solution is now a listing type, LLM-Assisted Authoring drafts listing copy from your package, and the docs refer to the marketplace and Checkout as AgentExchange throughout. If your listing has no agents, nothing about your console workflow has to change. Our AgentExchange explainer covers the marketplace side of the rename.
Partner Console mistakes that delay a listing
- Picking the wrong listing type. The type "can't change" after creation, so an Agentforce app listed as a Salesforce App needs a new listing.
- Receiving leads in a Developer Edition org. Lead collection requires a standard org, and Salesforce recommends the PBO so leads and licenses live together.
- Leaving reCAPTCHA on for Web-to-Lead. Lead events show in analytics while no leads reach your sales team.
- Submitting patch versions for review. Inheritance is limited for patches, so plan listed releases as minor versions.
- Using a personal inbox as the security review contact. Re-review notices and status changes go there, and a missed one can put the listing at risk.
- Forgetting the PADA. An approved listing still can't publish until the agreement is signed, and non-Checkout paid listings sign it offline through your account manager.
Frequently Asked Questions
How do I access the Salesforce Partner Console?
Log in to the Salesforce Partner Community at partners.salesforce.com and click Publishing. Your user needs the Manage Listings permission, which a Partner Community user with Manage Users can assign.
Can I give someone analytics access without publishing rights?
No. Manage Listings is the only permission for Marketplace Analytics, and it grants every Partner Console feature, including publishing listings.
Do new package versions need another security review?
Not a full one. A new major or minor version of a solution that passed can be associated with the listing right away, though patch versions inherit less and Salesforce runs periodic re-reviews.
Is the AppExchange Partner Console now the AgentExchange Partner Console?
Yes. Salesforce's ISVforce Guide uses "AgentExchange Partner Console," and access still runs through the Partner Community's Publishing tab.
Can Appnigma handle the listing and review work for us?
Yes. Appnigma's marketplace apps projects cover the native app, listing preparation and review support, while the Partner Console account, licensing and leads stay with your company.
About the author
Sunny Chauhan is the co-founder and CEO of Appnigma AI, which builds and maintains customer integrations and native Salesforce and HubSpot apps for B2B SaaS teams. Before Appnigma, he was on Salesforce's AppExchange team, where he worked with more than 300 SaaS partners. He has spent close to a decade on the Salesforce platform, including work at Zennify, and holds Salesforce certifications including Platform Developer II, Platform App Builder, Administrator, Data Cloud Consultant, and AI Associate.
Related Articles
- License Management Org vs License Management App
- Requirements to publish a paid app on AgentExchange
- How to get your app listed
- What AgentExchange is
- What the Salesforce AppExchange is
Sources
- Access the AgentExchange Partner Console, ISVforce Guide
- Salesforce Partner Business Org and Connect Your Partner Business Org, ISVforce Guide
- Can I Grant Access to Marketplace Analytics but Not Other Publishing Features?, ISVforce Guide
- Designate Contacts and Create a Company Profile, ISVforce Guide
- Get To Know the Listing Builder, Select a Listing Type and LLM-Assisted Authoring, ISVforce Guide
- Connect Your Solution and Set Default Licensing, ISVforce Guide
- How the Security Review Works, Start a Security Review and Follow-Up Security Review, ISVforce Guide
- Periodic Security Re-Reviews and Listing Readiness, ISVforce Guide
- Get Your Listing Approved, ISVforce Guide
- Activity Summary in Marketplace Analytics and Lead Events vs Leads, ISVforce Guide
- Marketplace Analytics refresh FAQ, Export Data and Top Searches, ISVforce Guide
- Enable Lead Collection and Leads and License Activities, ISVforce Guide
- Salesforce Launches AgentExchange, Salesforce newsroom, and the new AgentExchange
- Listing Readiness for Managed Packages, ISVforce Guide
