Step by step
- Open Team Management and select a teacher.
- Review the member activity drawer for the teacher you selected.
- Compare activity patterns across the roster to spot champions, inactive users, and likely support needs.
- Use those signals to decide where to train, follow up, or escalate.
You should see
Keep in mind
- Treat teacher activity as a rollout aid, not a performance score.
Common blockers
- Low activity does not always mean resistance; it can also mean a teacher is still waiting on seats, credits, LMS setup, or training.
Step by step
- Open Support & Settings from the Institution Admin Center.
- Start a support request from the institution context.
- Describe the rollout or account issue clearly and paste the relevant teacher, class, or license details into the request.
- Submit the request and keep the school context together in one thread.
You should see
Keep in mind
- The in-product support form is text-based, so screenshot sharing has to happen outside the form if needed.
Common blockers
- The institution support flow is better for school-scoped issues than opening separate teacher-level tickets.
Step by step
- Use the product docs first when the issue is really a workflow misunderstanding.
- Document local rollout expectations and internal training notes for issues the school can solve itself.
- Escalate to Classwise support only when the blocker is tied to accounts, licenses, integrations, or institution-scoped behavior.
You should see
Keep in mind
- Local rollout notes should stay aligned with what teachers actually see in the product.