All Sites

Platform 🔴 Advanced
📖 5 min read

Definition

All Sites is a Setup page that displays a consolidated list of every Salesforce site in the org, including Experience Cloud sites, Salesforce Sites, and Site.com pages. It provides administrators with a single view to manage site URLs, activation status, and configuration details for all web properties hosted on the Salesforce platform.

Real-World Example

The admin at GreenLeaf Organics navigates to All Sites in Setup to review the three sites running in their org: a customer self-service portal, a partner deal registration site, and a public knowledge base. From this page, she can quickly see which sites are active, check their URLs, and click through to each site's detailed configuration.

Why All Sites Matters

All Sites serves as the administrative command center for every web property your organization has deployed on the Salesforce platform. Rather than hunting through multiple Setup menus or different configuration areas to find and manage your sites, All Sites consolidates Experience Cloud sites, traditional Salesforce Sites, and Site.com pages into a single, centralized dashboard. This unified view is essential because modern Salesforce orgs often operate multiple digital properties simultaneously—customer portals, partner networks, community forums, and public-facing knowledge bases—each with distinct URLs, audiences, and configurations. Without All Sites, admins would waste time navigating between disparate setup locations, risking incomplete visibility into which sites are active, which are drafts, and what their public URLs actually are.

As an organization scales from a single site to multiple sites serving different constituencies, All Sites becomes critical for governance and maintenance. When an org has five or ten active sites running simultaneously, the risk of configuration drift, outdated URLs being shared internally, or accidentally deactivating the wrong site increases exponentially. All Sites prevents these scenarios by providing real-time status visibility and quick-access links to each site's detailed settings. Without this centralized view, support teams waste time explaining to users why a site is down, admins lose track of which sites have been migrated or deprecated, and stakeholders struggle to understand the complete digital footprint the organization maintains. The page becomes the single source of truth for all web properties, enabling confident decision-making about site lifecycle management and resource allocation.

How Organizations Use All Sites

  • TechFlow Solutions — TechFlow, a SaaS company, maintains three separate Experience Cloud sites from the All Sites dashboard: a customer success portal for active clients, a partner enablement community for resellers, and a public resource center for prospects. When they launched a fourth site for employee onboarding, the admin used All Sites to confirm all four were active and properly configured before communicating the new site's URL to HR. The consolidated view reduced their site management overhead by 40% and eliminated the previous practice of manually documenting site status in spreadsheets.
  • HealthCare Innovations Inc. — HealthCare Innovations uses All Sites to manage a patient portal, a physician network, and a regulatory compliance knowledge base—three sites with different security requirements and audiences. During their compliance audit, they used All Sites to generate a complete report of all active web properties for the auditor, demonstrating immediate visibility into their digital assets. Previously, they had to manually verify each site's existence and status across multiple configuration pages, which created audit delays and documentation gaps.
  • Global Distribution Networks — Global Distribution Networks manages sites across different regions and products from the All Sites page. When they were sunsetting an older Salesforce Site in favor of a new Experience Cloud site, they used All Sites to monitor both sites' statuses during the transition, confirm the new site's URL was properly configured, and deactivate the old site once traffic had migrated. The consolidated view gave them confidence in the migration timeline and prevented accidentally taking down the new site before it was fully operational.

🧠 Test Your Knowledge

See something that could be improved?

Suggest an Edit