> For the complete documentation index, see [llms.txt](https://klassdocs.gitbook.io/klassapp-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klassdocs.gitbook.io/klassapp-documentation/docs-site/help/admins/google.md). # Connect Google tools ยท 1 minute ## Connect Google tools ::: info Coming soon Google Drive, Google Classroom, and Google Sheets are not connected from the school admin screens on this release. There is no **Connect Google** button to use yet. ::: ### What you can do today **Continue with Google** on the register page only creates a KlassApp login. It does not attach Drive, Classroom, or Sheets to the school. To look at connections that do exist, open and choose **Integrations** in the settings bar. **Settings** is on the school admin menu only. If nothing is turned on for your school, the page says **No integrations available yet.** WhatsApp is separate. Parents message the school's KlassApp number. See [WhatsApp for parents](https://github.com/KlassApp-Foundation/KlassApp/tree/main/help/parents/whatsapp/README.md) and [Link requests](https://github.com/KlassApp-Foundation/KlassApp/tree/main/help/admins/link-requests/README.md). ### What happens next When a Google connection ships, this page will name the button and the menu path. Until then, do not expect Drive or Classroom inside Toshi. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://klassdocs.gitbook.io/klassapp-documentation/docs-site/help/admins/google.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.