Start with your session login.
Use the account and sign-in method provided for your tutoring program. Your school may use a school sign-in service; other students may have a Cignition account.
Technical support
A sign-in question, an audio issue, or a device to set up? Find a few checks to try, the requirements to review, and a real person to contact.
Cignition support center
Contact the support team about accessing or using your tutoring session.
For tutoring program questions, start here.
Before you reach out
These are useful first steps for students, families, and staff. If you’re still stuck, the support team can help you work through it.
Use the account and sign-in method provided for your tutoring program. Your school may use a school sign-in service; other students may have a Cignition account.
Use the latest Chrome on a Windows PC, Mac, or Chromebook. On an iPad, use Safari and install the native meeting app used by your program.
Check your microphone and camera permissions. Close other programs using them, restart the device, and rejoin your session. Check that your device is charged, too.
Install the native Google Meet, Zoom, or Microsoft Teams app used by your program. For Google Meet, sign in to the app with the student’s Google account.
Technology requirements
A device for each student, a supported browser, and a reliable connection help keep attention on the learning.
For supported operating systems, iPad models, and hardware specifications, use the full requirements document.
Headsets with a built-in microphone are recommended where there’s background noise. Keep devices and headsets charged and ready.
For school & district IT teams
Program tools and sign-in methods depend on your implementation. Work with Cignition to confirm the setup, then test it from a student’s point of view.
Review the technical documentStudents can sign in through the school’s SIS/LMS connection or a Cignition account, depending on the program setup.
School sign-in options may include Clever, Google Classroom, ClassLink, or an Edlink-compatible connection. Confirm the sign-in method with your Cignition team before students begin.
For Google Meet programs, student accounts need permission to join Cignition-hosted meetings and access documents shared from Cignition’s Google Workspace.
School networks and managed student devices need access to the domains used by the program. The technology requirements document includes the domain allowlist.
If a district uses filtering or a proxy, have your IT administrator review the configuration with Cignition. Test the experience on a typical student device.
Open the network requirementsTutoring uses Google Meet, Microsoft Teams, or Zoom, aligned with the program’s setup. Application access must be allowed by your IT administrator.
Tools vary by program. Your Cignition team can confirm which applications and permissions your students need.
Coordinate a sample session with Cignition using a typical student device, headset, and student login. Test with the expected number of students and the program’s audio/video configuration.
If network settings differ across school sites, test at each site. If students will participate from home, test that experience as well.
For rostering, coordinate the district’s chosen approach with Cignition, including OneRoster where applicable.
Let’s work through it
When you contact support, a few details can help us understand the issue:
Cignition support center