Selecting datasource category

Choosing the appropriate type enables enhanced ranking. Please contact us if you are unsure of how to categorize your datasource. If a datasource has multiple objectTypes which belong to different categories (such as Zendesk articles and Zendesk tickets), please set each category using objectDefinitions.docCategory. The category definitions below still apply.

KNOWLEDGE_HUB Reference documentation that may be continually updated as a source of truth, such as Github READMEs, Confluence documents, or ServiceNow knowledge articles

PUBLISHED_CONTENT Blog posts published at a point in time, such as Brightspot posts or Confluence blog posts. Note that Confluence blog posts are different from other Confluence documents, which should be classified as KNOWLEDGE_HUB.

COLLABORATIVE_CONTENT Documents that can be edited collaboratively, such as Google Drive, Dropbox, or Figma files

QUESTION_ANSWER Question-answer content such as Stack Overflow posts

TICKETS Work item or issue trackers such as Asana tasks, Jira tickets, or Github issues

CODE_REPOSITORY Source code repositories such as Github repositories

CHANGE_MANAGEMENT Code change management systems such as pull or merge requests on Github

EMAIL Email content such as Gmail or Outlook messages

MESSAGING Chat message or conversational content such as Slack or Discord messages

CRM Customer relationship management systems such as Sales Cloud

SSO Single-sign-on services such as Azure SSO or GSuite SSO

ATS Applicant tracking systems such as Greenhouse

PEOPLE This should not be used, please instead use the /bulkindexemployees API to upload data about employees

EXTERNAL_SHORTCUT This should not be used; please contact us for guidance

UNCATEGORIZED This should not be used; please contact us for guidance