Collections let you create custom subsets of your company’s knowledge connected to SiftHub, making it easy to streamline your work and generate targeted responses. You can link specific Documents, Q&As and items from sources like Google Drive/SharePoint, Notion, Websites, and more into a single “mini-repository” for use across SiftHub.
Key Benefits:
Organize your knowledge: Pick and choose documents, folders, or websites from any connected source or your uploaded Documents / Q&As to create a Collection. You can create Collections for a product line, region, or category.
For example: A “Security” Collection might include past security questionnaire, a Drive folder with certificates, and your website’s privacy policy page.
Generate targeted responses: Use Collections to filter the knowledge used for generating answers, autofilling questionnaires, or creating content with the AI Teammate. When filtering on a Collection, only the items in the Collection are used to generate responses.
Create a Collection
To start, go to Collections → Create Collection in SiftHub.
Fields:
Name (required) – E.g., “Security and Privacy”
Description – Explain the Collection’s purpose or contents
Access (required) – Choose who can use the Collection: Public, Restricted, or Private (see details below)
Owner – Automatically set to the creator; cannot be changed at creation time
Tip: New Collections default to Private. Admins can create Public, Restricted, or Private Collections; Members can create Private Collections only.
Link items to a Collection
From the Collection detail view use Link … to add items.
Documents and Q&As
Link specific documents, folders, or Q&As from the SiftHub repository.
All files within a linked folder are included.
Toggle ‘Link all’ to include all current and future uploads.
De-link specific files or folders no longer relevant.
Google Drive
Link specific files or folders from connected Google Drive content.
Toggle ‘Link all’ to include all connected files/folders.
Example: Link a “Certificates” folder for a “Compliance” Collection.
SharePoint
Link specific documents or folders from connected SharePoint sites.
Toggle ‘Link all’ to include all connected folders, files, and sites.
Example: Link a “Contracts” folder for a “Legal” Collection.
Notion
Link specific Notion pages from connected pages.
Toggle ‘Link all’ to include all connected pages.
Child pages of a linked page are automatically included.
Example: Link a “Roadmap” page for a “Product A” Collection.
Websites
Link specific websites from connected public websites.
Toggle ‘Link all’ to include all connected websites.
Child pages of a linked web page are automatically included.
Example: Link your privacy policy page for a “Security” Collection.
Slack
- Link specific channels from the channels already connected to SiftHub.
- Toggle ‘Link all’ to include every connected channel.
- Only channels already synced by the Slack connector appear in the picker — you cannot add new channels to SiftHub from here. If a channel is missing, use Sync now in the picker, or add it in the Slack connector settings first.
- Search by channel name to find a channel quickly.
- Example: Link #security-questions for a “Security” Collection, so answers draw on that discussion without pulling in unrelated channels.
Other Connectors
Support for linking specific items from other connectors (e.g., Zendesk) is coming soon.
Currently, toggle ‘Link all’ to include all items from a specific connector.
Collection access
Each Collection has one of three access types, defining who can use it for response generation:
<Company name> – Visible to everyone in the account.
Restricted – Visible to the Owner and specific users you add.
Private – Visible only to the Owner.
Important notes:
- Admins can create Public, Restricted, or Private Collections; Members can create Private only.
- New Collections default to Private.
- Delete Collection: A confirmation modal appears. Deleting a Collection does not delete linked items.
- Collections don’t control access to linked items. For example, if a Collection is Private, linked documents/Q&As remain visible to users with native access to those items.