One of the main trust questions schools ask is whether AI is being used in a way that keeps student work authentic. Classwise is designed so students can still complete work in an AI-free, paper-based classroom while AI handles grading and feedback behind the scenes.
Classroom trust model at a glance
Area | How Classwise handles it |
|---|---|
Student work mode | Students can stay on paper while AI works on grading and feedback behind the scenes. |
Teacher judgment | Teacher review remains the control point before results are treated as final. |
Sharing control | Completed results are not automatically equivalent to published or emailed results. |
Key points
- Students can keep working on paper instead of being pushed into a screen-first workflow
- Teachers stay in control of review and sharing decisions
- The product is designed to support teacher judgment, not replace it
Notes
- Use this section to explain how Classwise fits a paper-first classroom model. Use formal policy documents for legal review.
Security questions often show up in day-to-day product areas: connected logins, LMS provider access, institution-managed accounts, and who can see billing or admin tools.
Key points
- Classwise supports both OAuth-style LMS connections and token-based LMS connections depending on the provider.
- Teachers manage connected logins and passwords from profile settings where applicable
- Institution-managed members may have school-scoped access and billing visibility
- School-scoped LMS restrictions and provider-account conflict checks are part of the real access model.
- LMS connections are visible in-product so teachers can understand what is connected
Common blockers
- OAuth-style LMS connections and credentials-style LMS connections do not behave the same way.
- Institution-managed LMS restrictions affect which providers users can even see.
Public docs should explain the practical trust model, but deeper procurement or legal review should still be handled through the school evaluation process. The docs should clarify what the product does without over-claiming.
Decision checklist
- Use the workflow docs when the school wants to understand how grading, review, and sharing work day to day.
- Use the public privacy policy and terms when the school moves into policy review.
- Escalate to formal procurement or trust review when the question goes beyond what the in-product docs can prove.
Key points
- Use docs to explain workflow, review controls, and classroom model.
- Use the public privacy policy and terms pages for policy-level review before moving into school-specific conversations.
- Use product and institutional conversations for procurement-specific questions.