[ APPROVED SOURCES, NARROW ACCESS ]
Connect school knowledge
Bring selected school material into search and chat while preserving source permissions.
Keep the source close to the question.
Choose a connection to see its school use cases and setup checks.
Connections need school setup and permission review. Availability depends on the deployment and source service.
Choose a source with a purpose
Connect a curriculum collection, staff handbook, or approved resource library because a named group needs it, not simply because the system exists.
Match source permissions
Limit the connection to the folders, spaces, or projects the intended users may access. Test with student, teacher, and administrator accounts.
Own the lifecycle
Name who checks sync health, removes stale content, responds to permission changes, and disconnects a source that is no longer needed.
Start with material your learners already use
Connect a small, well-maintained source before adding a large archive. A class handout collection, a department knowledge base, or an approved coding repository gives you a clear set of questions to test.
Connection does not mean school-wide access
A connector needs an authorized account, source selection, and a review of permissions. The school should verify which users can retrieve which records. Some connector capabilities depend on the source plan or deployment configuration.
Test the full source lifecycle
Search for a known document, open the citation, update the source, and check that the change is reflected after indexing. Remove access for a test learner and confirm that the document is no longer available to that account.
Keep an owner for every source
Assign someone to maintain the credentials, review indexing health, and retire obsolete material. Search quality degrades when many near-identical documents compete to answer the same question.