Knowledge domains
Limit which external domains knowledge connectors can reach.
The Knowledge Sources tab controls which external domains Collection connectors can access, service by service.
A domain that isn't on the list is refused when the connector is configured, in the workspace.
The services covered
- Atlassian: allowed domains for Confluence and Jira.
- SharePoint: allowed domains.
- OneDrive: allowed domains.
Each has its own list. Allowing a domain for Atlassian doesn't allow it for SharePoint.
Why the list exists
Without it, anyone with permission to create Collections in the workspace could index an arbitrary site using the organization's infrastructure and credentials.
The list flips the default: nothing is reachable until someone with the Superadmin role explicitly authorizes that domain.
Add a domain
Open the configuration for the corresponding service and add the domain to the allowlist.
Check the exact domain the service uses. An Atlassian instance at company.atlassian.net isn't reached by an atlassian.net entry, and the error only shows up when someone tries to configure the connector.
When a connector fails to be created with a domain error, the cause is here, not in the workspace permissions or the service credential.
Next steps
- Understand what connectors feed in Collections and knowledge.
- See the other tabs in Settings.