A portal in Salesforce was the earlier framework for giving external users — customers, partners, self-service users — login access to a curated slice of your Salesforce org. There were three portal flavors: Self-Service Portal, Customer Portal, and Partner Portal. As of 2013, portals were superseded by Communities (now Experience Cloud), and Salesforce has been gradually retiring portal capabilities ever since. For interview purposes, the safe summary is “portals were the predecessor to Communities.”
The three portal types
| Portal | What it did | Status |
|---|---|---|
| Self-Service Portal | Basic customer self-service for case logging | Retired |
| Customer Portal | Branded portal for customers to view/update their cases, accounts, contacts | Superseded by Customer Community / Experience Cloud |
| Partner Portal | Branded portal for partner sales reps to manage leads and opportunities | Superseded by Partner Community / Experience Cloud |
Customer and Partner Portals are mostly deprecated — Salesforce no longer creates new portals in modern orgs, and existing portal-licensed users have been migrated to corresponding community licenses.
Why portals were replaced
Portals had real limitations Communities solved:
- No Lightning Experience — portals were Visualforce + Classic only.
- Limited responsive design — mobile was an afterthought.
- Restricted feature set — many objects and features weren’t available to portal users.
- Difficult to brand — heavy CSS work to make portals match a corporate look.
- No declarative builder — admins couldn’t easily lay out portal pages without code.
Communities addressed all of these with templates, Lightning Bolt themes, mobile-first rendering, and a visual builder.
Why the interview question still exists
Two practical reasons:
- Legacy orgs. Many large enterprise orgs still have portal-licensed users from the pre-2013 era. Knowing the portal heritage helps you read old metadata, old documentation, and old user licenses.
- License naming. Portal-era license names still appear in modern Salesforce admin screens — “Customer Portal Manager”, “High Volume Customer Portal”, “Gold Partner” — even though new orgs use community license names. Recognizing them avoids confusion.
Quick interview answer
“A portal was Salesforce’s pre-Communities framework for external users. There were Customer Portals and Partner Portals (plus the Self-Service Portal). Communities replaced them in 2013, and Communities themselves were rebranded as Experience Cloud. For new builds you use Experience Cloud; portals only matter when reading old orgs or old documentation.”
Verified against: Salesforce Help — Communities and Experience Cloud and historical Salesforce release notes. Last reviewed 2026-05-17.