Configure Sites Settings

You can specify who can create, share, and use sites functionality, which lets users design, build, publish, and manage websites that are hosted in Oracle Cloud.

Sites functionality in Oracle Content and Experience unites content, collaboration, and creativity in one user interface. You can seamlessly grab and reuse content to build sites, your site content is kept under control, and shared content makes collaboration between and among groups easier than ever.

  1. After you sign in to the Oracle Content and Experience web application as an administrator, click Settings in the Administration area of the navigation menu.

  2. In the Settings drop-down menu, choose Sites and Assets.
  3. You can select settings for the following options:
    • Allow sites to be created: Select Enabled to allow your service users to create sites. When you enable the ability to create sites, you allow all users to create templates and sites.

      If you disable site creation, users can still see and work with templates and other folders in the hierarchy. Users can also still work with an existing site if the site is shared with them. They can view, edit, and manage the site, depending on their role.

      When you enable sites functionality, users have the ability to publish any content they have access to, including confidential information. You might want to limit your users to creating only secured sites, so that users have to sign in before they can see the site content. For even more security, you can limit site creation to administrators.

    • Enable governance for sites: Select Enabled to simplify and accelerate site delivery for business users, who are not site administrators, while giving site administrators an easy way to control and track sites from a centralized location.

      With Governance enabled:

      • Developers can populate a template catalog with a set of site templates for the needs of different lines of business. They can apply policies regarding the type of security new sites must adhere to as well as whether new sites require approval.
      • Business users have the ability to rapidly request new sites with required approvals and automated provisioning,
      • Site administrators can manage all sites from one place regardless of who created and deployed the site. They can monitor site status and change status for any deployed site.
      See Understand Site Governance in Creating Experiences with Oracle Content and Experience.
    • Minimum security for online sites: Choose one of the following options from the drop-down list:
      • Specific service users—Only selected service users (the default setting)

        Only authenticated users who are explicitly selected as members can access the published site. You can further limit the selected users to only Oracle Content and Experience users.

      • Specific cloud users—Only selected cloud users
      • Service users—All service users

        Only authenticated service users, standard users, or enterprise users can access secure sites. This excludes authenticated visitors. See Application Roles.

      • Cloud users—All cloud users who can sign in to your domain.
      • Everyone—Anyone without signing in

      For information about specifying who can access public sites, see Changing Site Security in Creating Experiences with Oracle Content and Experience.

    • Allow sharing of sites and themes from UI: Select Enabled to allow users to share sites and themes with other Oracle Content and Experience users.

      If you disable sharing, users can still create and publish themes and sites. Users with the manager role for the theme or site (the owner or an administrator) can edit or publish the theme or site.

      If you disable sharing, users won't be able to share sites and themes through the user interface. It’s still possible to implement sharing of theme and site folders using the Oracle Cloud REST API for Content Management. See Developing for Oracle Content and Experience.

    • Only site administrators can create sites: Select Enabled to restrict the ability to create sites to users with the site administrator application role.
    • Only site administrators can create templates: Select Enabled to restrict the ability to create templates to users with the site administrator application role.
    • Only site administrators can create components: Select Enabled to restrict the ability to create components to users with the site administrator application role.
  4. Optionally, add JavaScript tracking code to sites for web analytics tracking, making it easier to integrate with external analytics providers like Google, Adobe, or Oracle Infinity. Adding a snippet here will propagate it to all new sites and pages. You can also add the snippet to directly to individual sites or pages or customize the propagated snippet as necessary.

    Click Edit, then add a web analytics tracking snippet like the following one for Google Analytics:

    <!--Global site tag (gtag.js - Google Analytics -->
    <script async src=""></script>
    window.dataLayer = window.dataLayer || O:
    function gtag0{dataLayer.push(arguments);}
    gtag('js', new Date0;
    gtag('config', 'UA-85172963-3'):

    Click Done, and then click Save.

    The tracking snippet here will be available in a site's settings, but a site manager must enable the snippet on the site, publish the change, and, if necessary, bring the site online before analytics are collected for that site. Site managers can also customize the snippet in the site settings or page settings.

    After the site manager publishes the site and brings it online, you can view the tracked analytics data on the vendor’s site, such as Google Analytics. If you used a snippet for Oracle Infinity analytics tracking, go to the Oracle Infinity home page and click Analytics to view the data and select or create reports.

  5. If you want to install a set of default site templates to help your users get started building their own sites, click Install default site templates.

    This option installs the templates shipped with Oracle Content and Experience. If this is the first time you have installed the templates, new folders are created for the template, its associated theme, and any custom components included in the template. If these templates were installed previously, installing them again will overwrite the associated template, theme, and custom component files, including any sharing settings you have set. After you install the templates, share the templates with the intended users.

    Until you share a template, it can’t be used by anyone else. When you share a template with users for the first time, the associated theme and any associated custom components are automatically shared with the identified users, who are given the Downloader role for the theme and components to ensure that they are available if the users create sites from the template. Subsequent changes in the template to the role for one or more users do not update the sharing information for the associated theme or custom components.

  6. Under Assets, configure the Maximum number of custom renditions per asset. The default is 20.

See Use Site Governance and Creating and Managing Sites in Creating Experiences with Oracle Content and Experience.