Workspaces
Keep conversations, Connections, model defaults, and future files and artifacts in one durable context.
Developer preview
An AI workspace that can work across the systems you are already authorized to use.
CampusLayer Assistant brings conversations, governed provider tools, workspaces, files, execution, generated artifacts, privacy controls, and model selection into one school-aware product.
Connected systems
Reuse account-scoped Connections such as Canvas without asking for the same credential every session.
Governed context
Authorization and Context Gateway policy apply before provider data crosses an inference boundary.
Artifacts
The runtime architecture is designed for generated PDFs, spreadsheets, presentations, and other persistent work products.
Product architecture
Chat is the surface. The product is the controlled workspace underneath it.
Assistant separates account Connections, workspace state, provider tools, privacy policy, model inference, and execution runtimes so one layer cannot silently grant authority to another.
Teacher / Administrator
↓
CampusLayer Assistant Workspace
Context Gateway + policy
Account Connections
Files + artifacts
Execution runtime
↓
Approved model and runtime providers
Current scope
The workspace foundation is being built now.
Conversations, Canvas tools, model selection, privacy tokenization/rehydration, history, usage metering, and the account Connection model exist today. Workspace-aware history, Connection bindings, and platform surfaces are the current implementation tranche.
Not claimed yet
- • Production Google Drive file workflows
- • Persistent generated-artifact storage
- • General hosted execution for school data
- • Shared teacher or department workspaces
- • Native Learn or Records product availability