Skip to main content
Back to Search AI connectors list Bigtincan is a cloud-based sales enablement and training platform used by organisations to deliver and manage learning content, including courses and presentations. You can configure Search AI to connect to Bigtincan to enable users to fetch query results using the content from training courses.

​
Specifications

​
Authorization Support

Search AI supports Username and Password-based authentication for communicating with Bigtincan. Authentication is established using a Login Directory, Username, and Password associated with your Bigtincan account.

​
Integration Steps

To configure Bigtincan as a content source, complete the following steps.
  • Configure the Bigtincan connector in Search AI
  • Set up Permissions
  • Configure Content Scope
  • Schedule Sync

​
Step 1: Configure the Bigtincan Connector in Search AI

Go to Connectors under the Sources page and select Bigtincan. On the Authorization tab, enter the following details and click Connect.
  • Name — Unique name for the connector.
  • Login Directory — The login directory associated with your Bigtincan account (for example, Citrix).
  • Username — The username used to log in to Bigtincan.
  • Password — The password associated with your Bigtincan account.
Once successfully authenticated, the status shows as Connected.

​
Step 2: Set Up Permissions

Go to the Permissions tab to configure access control for the ingested content. The following options are available.
  • Same users as in the source system (Restricted Access) — Automatically applies the same permissions from Bigtincan, ensuring secure and seamless access to ingested content.
  • Everyone (Public Access) — All users are granted full access to the ingested content, overriding any previous restrictions in the connector.
To enforce restrictions across all connectors in your workspace, contact support. Once enabled, these settings become locked and can only be changed via a support ticket.

​
Step 3: Configure Content Scope

Go to the Content Scope tab under Connector Setup to define the scope of content ingestion.
  • All content — Ingests all available content from the selected object types without applying any filters.

​
Step 4: Sync Content

After configuring the connector, go to Schedule Sync to initiate and manage content synchronization.
  • Use the Sync button for an immediate, on-demand sync.
  • Enable Schedule Sync to set up automated, recurring syncs.
The Schedule Sync table displays a log of all sync activity with the following details.

​
Content Ingestion

Once the sync is complete, go to the Content tab to review the ingested content. The tab displays the count of files that are Successful, Failed, and Skipped, along with the total number of Accessible Files. Each ingested course entry shows the following details.
  • Title — The name of the training course.
  • Size — File size of the ingested content.
  • Last Updated — The date and time the content was last updated.
Search AI ingests training courses from Bigtincan. The following key fields are extracted and indexed.
  • title — The name of the course or presentation, mapped from the course listing.
  • content — The textual body of the course, including slide or presentation text, made available for search operations.
  • doc_id — A unique identifier for the ingested course document, derived from the PresentationId field in the source payload.
  • doc_source_type — Identifies the source of the content; defaults to course if not specified in the source.
  • doc_created_on / doc_updated_on — Timestamps capturing when the course was created and last updated in Bigtincan.
  • url — The URL pointing to the course in Bigtincan, if available.
Key metadata fields such as ContentType, EnrollmentType, FolderId, and PresentationId are captured from the source payload.

​
RACL Support

Search AI provides access control support for courses ingested from Bigtincan. The sys_racl field is used to enforce access control by associating relevant identifiers — such as group identifiers or user email IDs — with the ingested content, ensuring that users can only access the content they are authorized to view. Since Bigtincan does not support automatic permission entity resolution, the Permission Entity APIs must be used to manually associate users with the appropriate permission entities after ingestion. For courses ingested from Bigtincan, the sys_racl field can include the following types of identifiers to manage content access:
  • Wildcard (*) — When a course is publicly accessible, the sys_racl field is set to *.
  • Group Identifier — When access is restricted to a specific group, such as “agents”, the sys_racl field contains the group name. This group is stored as a permission entity, and users must be manually associated with it using the Permission Entity APIs. Only users mapped to that group can find and access the course in Search AI results.
  • Course Owners — The owners of a course are also included in the sys_racl field, granting them access to the course in Search AI results.
  • User Email IDs — When access needs to be restricted to specific individuals, their email IDs are listed explicitly in the sys_racl field.