--- title: "Set Up Advanced Search in the End User Portal" slug: "set-up-advanced-search-in-the-end-user-portal" updated: 2026-08-16T08:39:13Z published: 2026-08-16T08:39:13Z canonical: "kb.ctera.com/set-up-advanced-search-in-the-end-user-portal" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.ctera.com/llms.txt > Use this file to discover all available pages before exploring further. # Set Up Advanced Search in the End User Portal To set up CTERA Content Services to provide advanced search in the CTERA Portal from version 8.4.x, the following requirements are necessary: - CTERA Content Services is installed on a VM that is reachable from the portal over HTTPS. - The storage used by the portal must be a storage node with [Direct Mode](/v1/docs/what-is-ctera-direct-mode) enabled. That is, either an S3 compatible storage node or Microsoft Azure Blob Storage. ## Configuring Content Services **To add the portal as a source:** 1. Select **Sources** in the navigation pane. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-ZBL3GWFW.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A29%3A11Z&se=2026-11-11T05%3A29%3A11Z&sr=c&sp=r&sig=hd7Pt3bkxLJ7W2KCUOo3IssJvuXdbCCrgPDvqy%2F%2B3Dw%3D) 2. Click **New Source**. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-X8E4UZCI.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A29%3A11Z&se=2026-11-11T05%3A29%3A11Z&sr=c&sp=r&sig=hd7Pt3bkxLJ7W2KCUOo3IssJvuXdbCCrgPDvqy%2F%2B3Dw%3D) 3. Enter the source details: **Name** – A name to identify the source. **Type** – Keep the default **CTERA**. **Host** – The URL to access the portal. 4. Change the **Authentication Method** to **Basic Auth**. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-PI9XZ9S3.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A29%3A11Z&se=2026-11-11T05%3A29%3A11Z&sr=c&sp=r&sig=hd7Pt3bkxLJ7W2KCUOo3IssJvuXdbCCrgPDvqy%2F%2B3Dw%3D) 5. Enter the team read/write administrator credentials including the **Access Key ID** and **Secret Key**. **Note** If you are using a global administrator, including API keys for the global administrator, you need to slide **Tenant Auth** off. 6. Make sure the source status is `Enabled` and click **Save Changes**. 7. Select **Datasets** in the navigation pane. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-JEBJJ4ZB.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A29%3A11Z&se=2026-11-11T05%3A29%3A11Z&sr=c&sp=r&sig=hd7Pt3bkxLJ7W2KCUOo3IssJvuXdbCCrgPDvqy%2F%2B3Dw%3D) 8. Select **Collectors** in the navigation pane. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-8E3D24N2.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A29%3A11Z&se=2026-11-11T05%3A29%3A11Z&sr=c&sp=r&sig=hd7Pt3bkxLJ7W2KCUOo3IssJvuXdbCCrgPDvqy%2F%2B3Dw%3D) 9. Click **New Collector**. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-DZIRX1TK.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A29%3A11Z&se=2026-11-11T05%3A29%3A11Z&sr=c&sp=r&sig=hd7Pt3bkxLJ7W2KCUOo3IssJvuXdbCCrgPDvqy%2F%2B3Dw%3D) 10. Enter the following details in the **General** tab: **Name** – A name to identify the collector. **URI** – The URI to access the collector. **Default Collector** – Slide on to make this collector the default collector. **Collector Status** – Select whether you want the status to be `Enabled` or `Disabled` 11. Click **Connect** in the URI field to connect to the collector and retrieve file type mappings. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-ULR0U9VV.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A29%3A11Z&se=2026-11-11T05%3A29%3A11Z&sr=c&sp=r&sig=hd7Pt3bkxLJ7W2KCUOo3IssJvuXdbCCrgPDvqy%2F%2B3Dw%3D) 12. For each file type, select the **Reader** if you don't want the default. 13. Click **Save Changes**. 14. Click **New Dataset**. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-TJRMC4WS.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A29%3A11Z&se=2026-11-11T05%3A29%3A11Z&sr=c&sp=r&sig=hd7Pt3bkxLJ7W2KCUOo3IssJvuXdbCCrgPDvqy%2F%2B3Dw%3D) 15. Enter the dataset details: **Name** – A name to identify the dataset. **Source** – Select the portal source from the list. **Capabilities** – Slide **Enable Text Search** on. **Collector** – The type of collector to use. **Selected Content** – The cloud drive folders to include, described in the next step. **Collectors** – The users who can collaborate on the dataset. 16. The selected content section is dependent on the source. For example, when the source is a CTERA Portal, the content includes cloud drive folders that belong to a specific owner or without any owner. 1. Click ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-9HJ7BSYJ.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A29%3A11Z&se=2026-11-11T05%3A29%3A11Z&sr=c&sp=r&sig=hd7Pt3bkxLJ7W2KCUOo3IssJvuXdbCCrgPDvqy%2F%2B3Dw%3D) to add a folder. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-XVNBO12L.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A29%3A11Z&se=2026-11-11T05%3A29%3A11Z&sr=c&sp=r&sig=hd7Pt3bkxLJ7W2KCUOo3IssJvuXdbCCrgPDvqy%2F%2B3Dw%3D) 2. Click **Users** to expand the users and then select a user and from the list of cloud folders, select a folder. The folder content is displayed. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-KU8N86G8.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A29%3A11Z&se=2026-11-11T05%3A29%3A11Z&sr=c&sp=r&sig=hd7Pt3bkxLJ7W2KCUOo3IssJvuXdbCCrgPDvqy%2F%2B3Dw%3D) 3. Click **Add Folder** 17. Enter the schema details and then the indexing actions required. 18. Click **Save Changes**. The content needs to be ingested into content services. ## Configuring the Portal The portal team read/write administrator needs to generate API keys which are used by Content Services, described in [Creating Access Key IDs and Secret Access Keys](/v1/docs/using-an-s3-browser-to-access-your-data-1#creating-access-key-ids-and-secret-access-keys). The following commands must be run on the portal: ``` set /settings/enterpriseSearchSettings/baseUrl https:// ``` For example, `https://api.<url_to_access_content_services>` ``` set /settings/enterpriseSearchSettings/clientId set /settings/enterpriseSearchSettings/jwtSecret ``` The client Id and jwtSecret are the values provided to Content Services when the portal was set as the source, as described in [Configuring Content Services](/v1/docs/set-up-advanced-search-in-the-end-user-portal#configuring-content-services). ``` set /settings/enterpriseSearchSettings/enabled true set /settings/enterpriseSearchSettings/trustAllCertificates true ``` **Note** You can verify the settings are correct by executing the following command: `show /settings/enterpriseSearchSettings`