CampusLayer Connect
Connect school systems without replacing them first.
Connect is the provider layer underneath CampusLayer. Canvas is connected through user supplied access tokens today. Skyward compatibility work remains useful for development, while the preferred district production path is an official Skyward partner integration.
Provider connections
Connect and verify provider accounts from one CampusLayer account.
Encrypted credentials
Provider secrets are encrypted server side before they are stored.
Live verification
CampusLayer tests the provider credential before marking a connection active.
Supported provider paths
Production integrations should use provider and district approved authorization instead of brittle local compatibility work.
Canvas now
URL, access token, verify, connect.
A user provides the Canvas URL and access token from their own Canvas account. CampusLayer verifies that token against Canvas, encrypts it, and can immediately use it for live authorized API requests.
Skyward path
Compatibility for development. Official integration for districts.
Existing compatibility work stays behind a replaceable Skyward adapter. For a real district deployment, CampusLayer intends to pursue Skyward Partner Portal access, provider review, licensing, and a supported production connection.