As part of your site design, you might want to control what content is public and
private to your site visitors. New sites are initially set so that all site resources, such as
folders and pages, are public. You can change the default setting from the Authorization view
found under Site Configuration.
Required Editions
Available in: Salesforce Classic
Available in: Enterprise, Performance, Unlimited, and
Developer Editions
The global site authorization options are:
No Authorization (default)—All resources are public.
Requires Authorization—All resources are private.
Custom—All resources are public by default, but can be made private.
The No Authorization and Requires Authorization options let you quickly make your site either
all public or all private. But, if you want to control access to individual pages, folders, and
other resources, use the Custom option. Selecting Custom enables a Requires
Authorization checkbox on the Actions menu for all resources throughout the
site. You can define authorization at the site, folder, page, and individual resource level. As
you mark items for authorization, a lock icon appears on them. After a resource,
like a page, is marked as private, users who aren’t logged into Salesforce are asked to log in
when they try to access it.
Resources can inherit their privacy setting from folders. For example, when a resource, such as
a site folder, is marked for authorization, anything placed in that folder inherits the folder’s
authorization setting and becomes private. If you drag that resource into a public folder, it
becomes public again. But, if you explicitly mark a resource as private using the Actions menu,
and then drag it into a public folder, it still remains private because the privacy setting at
the resource level dominates.
When you use the Custom option, an authorization table appears in the Authorization view that
lets you manage your private resources/items marked as private. You can remove authorization from
a resource by either deleting it from the authorization table, or by deselecting the Requires
Authorization box on the item itself.
Setting Custom Authorization When you select Custom authorization, you get a great deal of flexibility in controlling access to your site. Not only can you control who has access to top level resources, like folders and pages, but you can also set access at the individual resource level.
Remove Site.com Authorization You can remove authorization for a resource by either deleting it from the authorization table under Site Configuration, or by deselecting Requires Authorization from the Actions menu.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.