GitHub connector

Use GitHub as a source only when the school has enabled and scoped the connector.

A useful starting point

Begin with approved code examples and project documentation. Choose one collection that has a named audience and owner.

Limit Nexus to approved GitHub spaces. Test with each intended school role and remove access at the source when a user no longer needs it.

Review sync health, citations, deleted material, and permission changes. GitHub availability depends on the school deployment.

Keep exploring

Bring selected school material into search and chat while preserving source permissions.

Use connected, school-approved documents and inspect the cited passage.

Protect school information with tenant boundaries, role-based review, and deliberate operations.

Put learning first