---
schema_version: "1"
id: 218e6339e436a484357dad68fce98a885cedc58f6611880c5c760f703f9e7f39
title: Add the Field Service Scheduling Console to an Experience Builder Site
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/pfs_scheduling_console_community.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.pfs_scheduling_console_community.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e9fcfe98af0a09669c16d00b833328815270e12c9c80e0d12f038885606a6928
description: Add the Scheduling Console to an Aura site to give Experience Cloud site users access to its scheduling capabilities.
products:
  - Field Service
release: "264"
---
# Add the Field Service Scheduling Console to an Experience Builder Site

Add the Scheduling Console to an Aura site to give Experience Cloud site users access to its scheduling capabilities.

### 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: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">The Field Service core features, managed package, and mobile app are available in <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:left;vertical-align:top;" id="d21583e74">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d21583e74 ">To use the Scheduling Console in a site:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d21583e74 ">Field Service Community Dispatcher License permission set AND Field Service Community
              Dispatcher Permissions permission set</td>

          </tr>
        </tbody>
      </table>

![Package icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_field_service-264-0-0-production-enus/3f7dceb9-dd70-454a-b49e-bbb4526a158d/support_field_service/images/fs_package.png) _This is a Field Service managed package feature._

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_field_service-264-0-0-production-enus/3f7dceb9-dd70-454a-b49e-bbb4526a158d/images/icon_important.png)

Important The Scheduling Console doesn't support [LWR sites](https://help.salesforce.com/s/articleView?id=experience.exp_cloud_basics_glossary.htm&type=5&language=en_US).

Add the Scheduling Console component using Experience Builder.

1. From Setup, enter Digital Experiences in the Quick Find box, then select **All Sites**.
    
    **If you're creating a new site**:
    
    1. Click **New**. The creation wizard opens with several templates to choose from.
    2. Select the **Build Your Own (Aura)** template.
    3. Follow the prompts to create your page. Give it a meaningful name, such as Scheduling Console.
    4. In [Experience Workspaces](https://help.salesforce.com/s/articleView?id=experience.networks_workspaces.htm&type=5&language=en_US), select **Builder**.
    
    **If you already have an existing Aura site that you created for the Classic Dispatch Console**:
    
    1. Click **Builder**.
    2. Click **Home** and select the page where you want the Scheduling Console to appear. You can also create a new page.
2. From the **Components** menu under **Other Components**, drag the Scheduling Console component to the Content section of the page.
3. Set the component's height property. The default recommended height is 720 pixels, which works well for most desktop layouts. You can set higher or lower height values.
    
    - Higher values (for example, 900–1200 pixels): Use when the Scheduling Console is the main content on the page and you want it to fill the viewport.
    - Lower values (for example, 400–600 pixels): Use when the Scheduling Console shares the page with other significant content above or below it.
    
    The Scheduling Console component resizes automatically when the browser window is resized.
    
    ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_field_service-264-0-0-production-enus/3f7dceb9-dd70-454a-b49e-bbb4526a158d/images/icon_tip.png)
    
    Tip
    
    - Place the Scheduling Console component in a full-width region for the best experience. The Gantt and map benefit from horizontal space.
    - If the Scheduling Console appears cut off at the bottom, increase the minimum height or check that the parent section doesn't have a fixed height constraint.
4. Publish your changes and [activate](https://help.salesforce.com/s/articleView?id=experience.networks_publish.htm&type=5&language=en_US) the site.

To let users open the map in a separate tab from the Scheduling Console, create a new page called Field Service Map and drag the Scheduling Console Map component to its Content section. The process is the same as adding the Scheduling Console component described in this topic. See [Map Views and Routes in the Scheduling Console](https://help.salesforce.com/s/articleView?id=service.fs_scheduling_console_map_views.htm&type=5&language=en_US).

#### See Also

- [Work in the Scheduling Console](https://help.salesforce.com/s/articleView?id=service.fs_scheduling_console_parent.htm&language=en_US)
- [Experience Cloud](https://help.salesforce.com/s/articleView?id=experience.networks_overview.htm&language=en_US)
- [Create an Experience Cloud Site](https://help.salesforce.com/s/articleView?id=experience.networks_creating.htm&language=en_US)