---
title: Add a Confluence Cloud source
slug: '1530'
canonical_url: https://docs.coveo.com/en/1530/
collection: index-content
source_format: adoc
---
# Add a Confluence Cloud source

Confluence is a cloud-based knowledge sharing tool that enables users to create and share content.
Members of a [Coveo organization](https://docs.coveo.com/en/185/) with the [required privileges](#required-privileges) can add the [source](https://docs.coveo.com/en/246/) to [index](https://docs.coveo.com/en/204/) the content of their Confluence Cloud instance.

> **Leading practice**
>
> The number of [items](https://docs.coveo.com/en/210/) that a source processes per hour (crawling speed) depends on various factors, such as network bandwidth and source configuration.
> See [About crawling speed](https://docs.coveo.com/en/2078/) for information on what can impact crawling speed, as well as possible solutions.

## Source key characteristics

The following table presents the main characteristics of a Confluence Cloud source.

[%header,cols="2,2,2,4"]
|===
2+|Features
^|Supported
|Additional information

2+|Confluence Cloud version
^|Latest cloud version
|

2+|Indexable content
|Spaces, pages (such as Wiki pages), blog posts, pages and blog posts comments (indexed as [metadata](https://docs.coveo.com/en/218/)), and attachments (in pages, blog posts, and comments).
|

.3+|[Content update operations](https://docs.coveo.com/en/2039/)
|[refresh](https://docs.coveo.com/en/2710/)
^|[check]
|A refresh won't take account of deleted, restored, and moved items, and items with modified comments or permissions.
Therefore, a rescan or a rebuild is recommended.

|[rescan](https://docs.coveo.com/en/2711/)
^|[check]
|[Takes place every day by default](https://docs.coveo.com/en/1933/).
If you change the name of a space in Confluence Cloud, the rescan detects the change only for pages created or modified following the change.
You must therefore [rebuild](https://docs.coveo.com/en/3390#refresh-rescan-or-rebuild-sources) the source to get the space name changed on all space pages.

|[rebuild](https://docs.coveo.com/en/2712/)
^|[check]
|

.3+|[Content security](https://docs.coveo.com/en/1779/) options
|[Same users and groups as in your content system](https://docs.coveo.com/en/1779#same-users-and-groups-as-in-your-content-system)
^|[check]
|Requires installing the [Coveo User Sync app](https://marketplace.atlassian.com/search?query=Coveo%20User%20Sync%20app) in your instance.
See [About the Coveo User Sync App](#about-the-coveo-user-sync-app) for details.

|[Specific users and groups](https://docs.coveo.com/en/1779#specific-users-and-groups)
^|[check]
|

|[Everyone](https://docs.coveo.com/en/1779#everyone)
^|[check]
|

.4+|[Metadata indexing for search](#index-metadata)

|Automatic mapping of [metadata](https://docs.coveo.com/en/218/) to [fields](https://docs.coveo.com/en/200/) that have the same name
2+a|This setting is disabled by default and [not recommended for this source type](https://docs.coveo.com/en/1640#about-the-performfieldmappingusingallorigins-setting).

|Automatically indexed [metadata](https://docs.coveo.com/en/218/)
2+a|Examples of [auto-populated default fields](https://docs.coveo.com/en/1833#field-origin) (no user-defined metadata required):  
 

* `author`

* `clickableuri`

* `confcreateddate`

* `confspacename`

* `language` (auto-detected from item content)

* `objecttype`

* `title`  
 

After a content update, [inspect your item field values](https://docs.coveo.com/en/2053#inspect-search-results) in the **Content Browser**.

|Extracted but not indexed metadata
2+a|The Confluence Cloud source extracts some of the metadata that the Confluence API makes available.  
 

After a rebuild, review the [**View and map metadata**](https://docs.coveo.com/en/m9ti0339#view-and-map-metadata-subpage) subpage for the list of indexed metadata, and [index additional metadata](https://docs.coveo.com/en/m9ti0339#index-metadata).

|Custom metadata extraction
2+a|Confluence lets you add custom properties to pages, blog posts, attachments, and spaces using the Confluence API.
Then, you can use the `MetadataPropertiesToIndex` JSON configuration parameter to list the custom properties to extract as metadata.
|===

> **Note**
>
> Q&A in Confluence is an external plugin that must be installed on the instance.
> The Confluence source doesn't support indexing Q&A.
> To index Q&A, use a [REST API cloud source](https://docs.coveo.com/en/1896/) instead.

## Add a Confluence Cloud source

A Confluence Cloud source [indexes](https://docs.coveo.com/en/204/) cloud content.
To retrieve on-premises (server) content, see [Add a Confluence Data Center source](https://docs.coveo.com/en/1822/) instead.

> **Leading practice**
>
> It's best to create or edit your source in your sandbox organization first.
> Once you've confirmed that it indexes the desired content, you can copy your source configuration to your production organization, either [with a snapshot](https://docs.coveo.com/en/3239/) or manually.
> 
> See [About non-production organizations](https://docs.coveo.com/en/2959/) for more information and best practices regarding sandbox organizations.



. On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click **Add source**.

. In the **Add a source of content** panel, click the **Confluence Cloud Cloud** (icon:cloud-icon[alt=cloud-icon,width=16]) source tile.

. In the **Add a new Confluence Cloud source** panel, provide the following information:

** **Name**: The source name can't be modified once it's saved.
Therefore, make sure to use a short and descriptive name, using letters, numbers, hyphens, and underscores.
Avoid spaces and other special characters.

** **Confluence address**: The root URL of your Confluence instance.
It often ends with `/wiki/`.
Alternatively, you can enter the URL of a specific Confluence Cloud space, provided it matches one of the following patterns.
If it doesn't, see [Supporting other space URLs](#supporting-other-space-urls).

*** `[URL]/spaces/viewspaces.actions?key=[KEY]`

*** `[URL]/display/[KEY]`

*** `[URL]/spaces/[KEY]`

** **Authentication**: How Coveo should log in to your Confluence Cloud site to index your content.

**If you select **Atlassian account****
<details><summary>Details</summary>

.. Create an Atlassian account dedicated to the source.
This account must have access to all the content that you want to index.
See [Source credentials leading practices](https://docs.coveo.com/en/1920/) for other leading practices to follow.

.. With this account, [create an API token](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/?_ga=2.126505613.1817776130.1555381268-505570362.1555381268).
This token should also be dedicated to your source.

[NOTE]
**Note**

</details>
[Tokens with scopes](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/#Create-an-API-token-with-scopes) aren't supported.
##### .. Provide Coveo with the email address and API token corresponding to the source's Atlassian account.

.. Install the [Coveo User Sync app](#about-the-coveo-user-sync-app) in your Confluence Cloud site to synchronize users and groups with Coveo.

.. Click **Add source**.
####  
**If you select **No login****
<details><summary>Details</summary>

.. Click **Next**.

.. Select who will be able to access the source items through a Coveo-powered [search interface](https://docs.coveo.com/en/2741/).
For details on this parameter, see [Content security](https://docs.coveo.com/en/1779/).

.. Click **Add source**.

</details>

** **Project**: Use the **Project** selector to associate your source with one or more Coveo [projects](https://docs.coveo.com/en/n7ef0517/).

> **Note**
>
> After source creation, you can update your Coveo project selection under the [**Identification**](#identification-subtab) subtab.

### "Configuration" tab

When configuring or editing your Confluence Cloud source, the **Configuration** tab is selected by default.
It contains your source's general and authentication information, as well as other parameters that let you specify the content to index.

#### "Content to index" subtab

The **Content to index** subtab lets you define the content that you want to make available as search results.

##### Spaces

In the **Spaces** card, specify whether you want to index communal and/or personal spaces.
Then, specify whether you want to index active and/or archived spaces.

If you want to index specific pages only, enter a regex matching the desired space keys under **Space key**.
Alternatively, you can enter a regex to exclude specific spaces from the indexing process.
As a result, when crawling your Confluence instance, Coveo will target/ignore the spaces whose space key matches your regex.

For instance, if you want to index all spaces with keys starting with an uppercase letter followed by a number, you enter the following regex: `+^[A-Z][0-9].*$+`.
Conversely, enter `+^(?!Spacekey$).*$+` to exclude the space with the key `Spacekey`.

##### Additional content



Optionally, you can index the files attached to the indexed pages, blog posts, and comments.

You can also index comments posted on pages and blog posts.
These comments will be indexed as [metadata](https://docs.coveo.com/en/218/) of this content.


#### "Authentication" subtab


** **Confluence address**: The root URL of your Confluence instance.
It often ends with `/wiki/`.
Alternatively, you can enter the URL of a specific Confluence Cloud space, provided it matches one of the following patterns.
If it doesn't, see [Supporting other space URLs](#supporting-other-space-urls).

*** `[URL]/spaces/viewspaces.actions?key=[KEY]`

*** `[URL]/display/[KEY]`

*** `[URL]/spaces/[KEY]`

** **Authentication**: How Coveo should log in to your Confluence Cloud site to index your content.

**If you select **Atlassian account****
<details><summary>Details</summary>

.. Create an Atlassian account dedicated to the source.
This account must have access to all the content that you want to index.
See [Source credentials leading practices](https://docs.coveo.com/en/1920/) for other leading practices to follow.

.. With this account, [create an API token](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/?_ga=2.126505613.1817776130.1555381268-505570362.1555381268).
This token should also be dedicated to your source.

[NOTE]
**Note**

</details>
[Tokens with scopes](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/#Create-an-API-token-with-scopes) aren't supported.
##### .. Provide Coveo with the email address and API token corresponding to the source's Atlassian account.

.. Install the [Coveo User Sync app](#about-the-coveo-user-sync-app) in your Confluence Cloud site to synchronize users and groups with Coveo.

.. Click **Add source**.
####  
**If you select **No login****
<details><summary>Details</summary>

.. Click **Next**.

.. Select who will be able to access the source items through a Coveo-powered [search interface](https://docs.coveo.com/en/2741/).
For details on this parameter, see [Content security](https://docs.coveo.com/en/1779/).

.. Click **Add source**.

</details>
The **Authentication** subtab contains settings used by the source crawler to emulate the behavior of a user authenticating to access restricted Confluence Cloud content.

**Confluence address**: The root URL of your Confluence instance.
It often ends with `/wiki/`.
Alternatively, you can enter the URL of a specific Confluence Cloud space, provided it matches one of the following patterns.
If it doesn't, see [Supporting other space URLs](#supporting-other-space-urls).

*** `[URL]/spaces/viewspaces.actions?key=[KEY]`

*** `[URL]/display/[KEY]`

*** `[URL]/spaces/[KEY]`

**Authentication**: How Coveo should log in to your Confluence Cloud site to index your content.


**If you select **Atlassian account****
<details><summary>Details</summary>

. Create an Atlassian account dedicated to the source.
This account must have access to all the content that you want to index.
See [Source credentials leading practices](https://docs.coveo.com/en/1920/) for other leading practices to follow.

. With this account, [create an API token](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/?_ga=2.126505613.1817776130.1555381268-505570362.1555381268).
This token should also be dedicated to your source.

[NOTE]
**Note**

</details>
[Tokens with scopes](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/#Create-an-API-token-with-scopes) aren't supported.
##### . Provide Coveo with the email address and API token corresponding to the source's Atlassian account.

. Install the [Coveo User Sync app](#about-the-coveo-user-sync-app) in your Confluence Cloud site to synchronize users and groups with Coveo.
#### .If you select **No login**
<details><summary>Details</summary>

Go to the **Content security** tab, and then select who will be able to access the source items through a Coveo-powered [search interface](https://docs.coveo.com/en/2741/).
For details on this parameter, see [Content security](https://docs.coveo.com/en/1779/).

</details>

#### "Identification" subtab

The **Identification** subtab contains general information about the source.

## Name

The source name.
It can't be modified once it's saved.

:leveloffset!:

##### Project

Use the **Project** selector to associate your source with one or more Coveo [projects](https://docs.coveo.com/en/n7ef0517/).

### "Items" tab

On the **Items** tab, you can specify how the source handles items based on their file type or content type.

#### File types

File types let you define how the source handles [items](https://docs.coveo.com/en/210/) based on their file extension or content type.
For each file type, you can specify whether to index the item content and [metadata](https://docs.coveo.com/en/218/), only the item metadata, or neither.

You should fine-tune the file type configurations with the objective of indexing only the content that's relevant to your users.

**Example**

Your repository contains `.pdf` files, but you don't want them to appear in search results.
You click **Extensions** and then, for the `.pdf` extension, you change the **Default action** and **Action on error** values to `Ignore item`.

For more details about this feature, see [File type handling](https://docs.coveo.com/en/l3qg9275/).

#### Content and images

If you want Coveo to extract text from image files or PDF files containing images, enable the appropriate option.
The extracted text is processed as item data, meaning that it's fully searchable and will appear in the item [Quick view](https://docs.coveo.com/en/2760#search-result-quick-view).

> **Note**
>
> When OCR is enabled, ensure the source's relevant [file type configurations](https://docs.coveo.com/en/l3qg9275/) index the item content.
> Indexing the item's metadata only or ignoring the item will prevent OCR from being applied.

See [Enable optical character recognition](https://docs.coveo.com/en/2937/) for details on this feature.

### "Content security" tab

Select who will be able to access the source items through a Coveo-powered [search interface](https://docs.coveo.com/en/2741/).
For details on the content security options, see [Content security](https://docs.coveo.com/en/1779/).

> **Note**
>
> The **Same users and groups as in your content system** option requires you to install the [Coveo User Sync app](https://marketplace.atlassian.com/search?query=Coveo%20User%20Sync%20app) in your instance.
> Install the version of the app that corresponds to the [region](https://docs.coveo.com/en/2976/) of your Coveo organization, or install the [HIPAA](https://docs.coveo.com/en/1853/) version for Coveo HIPAA environments.
> See [About the Coveo User Sync App](#about-the-coveo-user-sync-app) for details.

### "Access" tab







. On the **Access** tab, specify whether each group (and API key, if applicable) in your [Coveo organization](https://docs.coveo.com/en/185/) can view or edit the current source.

For example, when creating a new source, you could decide that members of Group A can edit its configuration, while Group B can only view it.

For more information, see [Custom access level](https://docs.coveo.com/en/3151#custom-access-level).
On the **Access** tab, specify whether each group (and API key, if applicable) in your [Coveo organization](https://docs.coveo.com/en/185/) can view or edit the current source.

For example, when creating a new source, you could decide that members of Group A can edit its configuration, while Group B can only view it.

For more information, see [Custom access level](https://docs.coveo.com/en/3151#custom-access-level).

### Build the source

. Finish adding or editing your source:

** When you're done editing the source and want to make your changes effective, click **Add and build source**/**Save and rebuild source**.

** When you want to save your source configuration changes without starting a build/rebuild, such as when you know you want to make other changes soon, click **Add source**/**Save**.
On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click **Launch build** or **Start required rebuild** when you're ready to make your changes effective and index your content.

> **Leading practice**
>
> By default, a Jira Software source indexes the entire Jira Software instance content.
> To index only certain projects, click **Save**, and then specify the desired address patterns in your [source JSON configuration](https://docs.coveo.com/en/1685/) before launching the initial build.
> See [Add source filters](https://docs.coveo.com/en/2006#add-source-filters) for further information.

. On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, follow the progress of your source addition or modification.

. Once the source is built or rebuilt, [review its content in the Content Browser](https://docs.coveo.com/en/2053/).

. Optionally, consider [editing or adding mappings](https://docs.coveo.com/en/1640/).


> **Note**
>
> If you selected **Specific URLs** or **User profiles** in the [**Content**](https://docs.coveo.com/en/1739#content) section, some additional items will appear in the Content Browser.
> To retrieve user profiles, Coveo must crawl your SharePoint Online instance, including your host site collection and the documents it contains.
> Items encountered during this process are also retrieved and therefore appear in the Content Browser.

### Index metadata

To use [metadata](https://docs.coveo.com/en/218/) values in [search interface](https://docs.coveo.com/en/2741/) [facets](https://docs.coveo.com/en/198/) or result templates, the metadata must be [mapped](https://docs.coveo.com/en/217/) to [fields](https://docs.coveo.com/en/200/).
Coveo automatically [maps](https://docs.coveo.com/en/217/) only a subset of the metadata it extracts.
You must map any additional metadata to fields manually.

> **Note**
>
> Not clear on the purpose of indexing metadata?
> Watch [this video](https://www.youtube.com/watch?v=BmmmVJ3AWi0).

. On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click your source, and then click **More** > **View and map metadata** in the Action bar.

. Review the default [metadata](https://docs.coveo.com/en/218/) that your source is extracting from your content.

. Map any currently _not indexed_ metadata that you want to use in facets or result templates to fields.

.. Click the metadata and then, at the top right, click **Add to Index**.

.. In the **Apply a mapping on all item types of a source** panel, select the field you want to map the metadata to, or [add a new field](https://docs.coveo.com/en/1833#add-a-field) if none of the existing fields are appropriate.

> **Note**
>
> For advanced mapping configurations, like applying a mapping to a specific item type, see [Manage mappings](https://docs.coveo.com/en/1640#manage-mappings).

.. Click **Apply mapping**.

. Return to the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page.

. To reindex your source with your new mappings, click your source, and then click **More** > **Rebuild** in the Action bar.

. Once the source is rebuilt, review your item field values.
They should now include the values of the metadata you selected to index.

.. On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click your source, and then click **More** > **Open in Content Browser** in the Action bar.

.. Select the card of the item for which you want to inspect properties, and then click **Properties** in the Action bar.

.. In the panel that appears, select the **Fields** tab.

. If needed, extract and map additional metadata.

**More on custom metadata extraction**
<details><summary>Details</summary>

Confluence lets you add custom properties to pages, blog posts, attachments, and spaces using [Content Properties](https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-content-properties/#api-group-content-properties) and [Space Properties](https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-space-properties/#api-group-space-properties) POST requests.
You can then extract these custom properties.

. On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click your source, and then click **More** > **Edit configuration with JSON** in the Action bar.

. On the **Parameters** tab, locate the `MetadataPropertiesToIndex` parameter in the **JSON configuration** box.

. Add the desired custom property names in the `value` of the `MetadataPropertiesToIndex` parameter as a comma-separated list.
To refer to a property nested within another, concatenate their names with a dot (`.`) separator.

For example:

```json
"MetadataPropertiesToIndex": {
    "sensitive": false,
    "value": "categorization.department,categorization.team"
  }
```

. Rebuild and map each extracted custom metadata to a field, as you did for the default metadata.
In the **View and map metadata** page, the metadata names will have the `metadata.properties` prefix.
For example: `metadata.properties.categorization.department`.

</details>

### Ensuring correct time zone for incremental refreshes

To ensure that new items are indexed with the next refresh operation, [edit the JSON configuration of your source](https://docs.coveo.com/en/1685/) so that the source uses the same time zone as your Confluence Cloud instance:

. On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click your source, and then click **More** > **Edit configuration with JSON** in the Action bar.

. In the `parameters` object, add the following object:

```json
"LocalServerTimeOffsetForIncrementalRefresh": {
  "sensitive": false,
  "value": "<TIME_ZONE_OFFSET>"
}
```

. Replace `<TIME_ZONE_OFFSET>` with the time offset from UTC required to match the time zone of your Confluence Cloud instance.
For example, if your Confluence instance uses UTC-04:00 time, enter `-04:00`.

## Source update best practice

You can get the `CONFLUENCE_UNREACHABLE_SERVER` error message when your Confluence Cloud source rebuilds or is scheduled to perform a rescan during the daily Atlassian Cloud maintenance window (1 AM to 3 AM, in your server's time zone).
During this period, Atlassian may block access to the API while performing [maintenance tasks](https://confluence.atlassian.com/cloud/maintenance-windows-744721660.html).

If possible, [schedule](https://docs.coveo.com/en/1933/) your source's rescans so that they're completed outside of the daily maintenance window.
If not possible, ignore the errors.
The next scheduled rescan outside the maintenance window shall complete normally.

## About the Coveo User Sync app


Installing Coveo's User Sync app in your Atlassian instance is required to [replicate your instance's content access permissions in your search interface](https://docs.coveo.com/en/1779/).
This lets users see in their Coveo search results the content that their role allows them to see in your Atlassian instance.

To replicate your instance's permission system, Coveo must associate user email addresses with user roles.
Atlassian's API doesn't provide this information, but provides the roles assigned to each user account ID.
So, Coveo built the User Sync app to retrieve the email address corresponding to each user account ID.
It can then combine this information with the roles and account IDs provided by Atlassian's API.

Should you ever switch your source's [content security setting](#content-security-tab) from **Everyone** to **Same users and groups as in your content system**, you'll need to [refresh the security identity provider](https://docs.coveo.com/en/1905#refresh-all-security-identities) after installing the app.

For more information on [sources that index permissions](https://docs.coveo.com/en/1779#same-users-and-groups-as-in-your-content-system) and on how Coveo handles these permissions, see [Coveo management of security identities and item permissions](https://docs.coveo.com/en/1719/).

> **Note**
>
> Coveo doesn't support the global permission allowing Jira Service Management (JSM) users to use Confluence (**Settings** > **Global permissions** > **JSM access**).
> As a result, JSM users who have access to your Confluence content through this global permission can't access this content in their Coveo search results.

### Why isn't the app Cloud Fortified?

Atlassian's [Cloud Fortified Apps Program](https://developer.atlassian.com/platform/marketplace/cloud-fortified-apps-program/) designates apps that meet the highest standards for security, reliability, and support, making them suitable for enterprise customers with critical business needs.

The Coveo User Sync app isn't part of the Cloud Fortified Apps Program, but it meets all the requirements except for one: participation in Atlassian's [Marketplace Security Bug Bounty Program](https://developer.atlassian.com/platform/marketplace/marketplace-security-bug-bounty-program/).
Coveo isn't currently planning to join this program because it already has [its own bug bounty program](https://docs.coveo.com/en/2024#penetration-testing-and-bug-bounty-program) in place.

For more information about vulnerability management at Coveo, including penetration testing, see [Vulnerability management](https://docs.coveo.com/en/2024/).
You may also want to read on [other security-related topics](https://docs.coveo.com/en/1778/).

## Supporting other space URLs

In the [**Confluence address** box](#authentication-subtab), you can enter the URL of a specific Confluence space, provided it matches one of the following patterns:

* `[URL]/spaces/viewspaces.actions?key=[KEY]`

* `[URL]/display/[KEY]`

* `[URL]/spaces/[KEY]`

If your space address doesn't match any of these default patterns, you can still index it by following these steps:

. In the [**Confluence address** box](#authentication-subtab), enter the root URL of your Confluence instance.
This address often ends with `/wiki/`.

. Configure the source as you would to index your space, and then click **Add source**.

. In the Coveo Administration Console, click the source you just created, and then click **Edit configuration with JSON** in the **More** menu.

. In the **Edit configuration with JSON** panel that opens, locate the `RootSpaceRegex` object in the `parameters` object.

. Change the regex pattern to match your space URL.

. Scroll down to locate the `startingAddresses` array, and then, in place of your Confluence instance root URL, enter the URL of your space.

. Click **Save and rebuild source**.


## Required privileges

You can assign privileges to allow access to specific tools in the [Coveo Administration Console](https://docs.coveo.com/en/183/).
The following table indicates the privileges required to view or edit elements of the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page and associated panels.
See [Manage privileges](https://docs.coveo.com/en/3151/) and [Privilege reference](https://docs.coveo.com/en/1707/) for more information.

> **Note**
>
> The **Edit all** privilege isn't required to create sources.
> When granting privileges for the [Sources](https://docs.coveo.com/en/1707#sources-domain) domain, you can grant a group or API key the **View all** or [**Custom**](https://docs.coveo.com/en/3151#custom-access-level) access level, instead of **Edit all**, and then select the **Can Create** checkbox to allow users to create sources.
> See [Can Create ability dependence](https://docs.coveo.com/en/3151#can-create-ability-dependence) for more information.

## What's next?

* [Schedule source updates](https://docs.coveo.com/en/1933/).
[Schedule source updates](https://docs.coveo.com/en/1933/).