---
schema_version: "1"
id: 4c671096187854024aca62520c6d6c6aca1752c07ee72f080accdf6a038f20f9
title: Salesforce Sites Considerations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/sites_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.sites_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 551c9ddc3d9660d16d7641210ef5daa4c674a93a542dbdb5166ca88da42eb81c
description: Before you create and use Salesforce Sites, review considerations around App Exchange packaging, access and authentication, and potential URL conflicts between sites.
products:
  - Salesforce Platform
  - Security
release: "264"
---
# Salesforce Sites Considerations

Before you create and use Salesforce Sites, review considerations around App Exchange packaging, access and authentication, and potential URL conflicts between sites.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Developer</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong> Editions</td></tr></tbody></table>

## Packaging

Sites aren’t packageable. However, you can package sample code, Visualforce pages, Apex classes, or components for a site using a managed package.

To install unmanaged packages that contain Visualforce pages or Apex classes that refer to a site, Salesforce Sites must be enabled.

## Access and Authentication

You can grant Read and Create permissions on all standard objects except products, price books, and ideas. Also, you can grant Read, Create, Edit, and Delete permissions on all custom objects. For additional access, you must authenticate site visitors as portal users.

Custom authentication isn’t supported. Only these methods are supported for Salesforce Site authentication.

- Customer Portals—[enable public login and registration](https://help.salesforce.com/s/articleView?id=platform.sites_login_and_registration_settings.htm&release=264.0.0&type=5 "Let users register for and log in to your portal from your public Salesforce Site. For example, users browsing through an ideas site can register and login directly from that site. Then, as authenticated users, those users can vote, add comments, and participate in the ideas community. When users successfully log in, they leave the public site and enter the associated portal seamlessly.")
- Partner portals—create partner users

![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_tip.png)

Tip You can also enable single sign-on for portals, as well as Sites.

## URL Conflicts Between Sites

If you host multiple sites on the same Salesforce-managed domain, be sure to review your site URLs for conflicts, as it’s possible to configure the same URL for pages on two different sites.

Let’s say you use https://SitesSubdomain.force.com for Site A’s homepage, and https://SitesSubdomain.force.com/products for Site B’s homepage. If you create a page on Site A that uses the subpath /products, that page and Site B’s homepage both use the URL https://SitesSubdomain.force.com/products.

In this scenario, a site visitor can only access the Site A page through a navigation menu on Site A. If a site visitor navigates to https://SitesSubdomain.force.com/products any other way, they’re directed to Site B’s home page.

#### See Also

- [Salesforce Sites](https://help.salesforce.com/s/articleView?id=platform.sites_overview.htm&release=264.0.0&type=5 "Salesforce Sites enables you to create public websites and applications that are directly integrated with your Salesforce organization—without requiring users to log in with a username and password. You can publicly expose any information stored in your organization through a branded URL of your choice. And you can make the site's pages match the look and feel of your company’s brand.")