> For the complete documentation index, see [llms.txt](https://docs.spreo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spreo.io/getting-started/signing-in.md).
# Signing In
The ways to sign in to Spreo, and where to manage your sign-in details.
### Ways to sign in
* **Email code** - enter your email address and we send you a 6-digit code. The code is valid for 15 minutes.
* **Google or Microsoft** - continue with your existing Google or Microsoft account.
* **Single Sign-On** - if your organization uses SSO, entering your work email takes you to your company's sign-in page. See [Single Sign-On](/management/single-sign-on.md).
You stay signed in on that browser for 30 days.
### Passwords
Spreo does not ask for a password when you sign up. If you would rather use one, you can set a password once you are signed in, in Your Settings under Security. You can remove it again from the same place.
### Your Settings
Open Your Settings from the profile menu in the top right.
It has these sections:
| Section | What you can do there |
| --------------- | ------------------------------------------------------------------------------------------------------- |
| Personalization | Change your name and how you appear on boards |
| Controls & UI | Change mouse, zoom and other board preferences |
| Security | Change your email address, set or remove a password, and see your connected Google or Microsoft account |
| Integrations | Manage your connections, such as Jira and AI assistants |
| Notifications | Choose which emails and notifications you receive. See [Notifications](/boards/notifications.md) |
| Danger Zone | Delete your profile |
### Guests
If the organization allows it, guests can join a board with a temporary profile, without signing in. See [Share your board](/boards/share-your-board.md#guests).
---
# 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.spreo.io/getting-started/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.
