> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/get-started/signing-up-and-signing-in.md). # Signing up and signing in Follow these instructions to get set up when you're just starting out with Cogram. ## Signing Up If you don't yet have a Cogram account, create an account [on Cogram's Sign Up page](https://app.cogram.com/auth/register/).
The Cogram sign up page with email, password, and confirm password fields, plus Google and Microsoft sign-up options

The sign up page

{% hint style="warning" %} Sign up with the same email you use in your calendar to schedule and join meetings. Personal email addresses (Gmail, Yahoo, etc.) aren't supported, so use your work email. {% endhint %} After clicking "Sign Up", Cogram will send you a confirmation email to verify your email. Click on the link in the email to confirm your account. If you do not receive a confirmation email within a few minutes after registering, contact . Head to the [Sign In](https://app.cogram.com/auth/login) page to log in. ## Signing In
The Cogram sign in page with email and password fields, plus Google, Microsoft, and SSO sign-in options

The sign in page

To sign in, enter the email and password you used to sign up. On your first login, Cogram walks you through basic setup and a short tutorial. Follow the on-screen tooltips to learn how to invite Cogram for note-taking in a virtual meeting and how to view Cogram's notes after a meeting. --- # 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://docs.cogram.com/get-started/signing-up-and-signing-in.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.