> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/onboarding/account/sso.md).

# Sign in with Google or Microsoft

You can sign in to Stoïk Protect using your Google or Microsoft work account, no Stoïk password needed.

## Signing in

On the Stoïk Protect login page, click **Continue with Google** or **Continue with Microsoft**.

You will be redirected to your provider's sign-in screen. After authenticating, you land straight in Stoïk Protect.

The next time you visit, a **Last used** badge marks the method you used most recently.

## Accepting an invitation via SSO

When a Stoïk Protect admin sends you an invitation, you can join without creating a password:

1. Click the link in your invitation email
2. On the sign-up page, click **Continue with Google** or **Continue with Microsoft**
3. Authenticate with your work account
4. You land directly in Stoïk Protect

Your account must use the same email address as the one the invitation was sent to.

{% hint style="info" icon="lightbulb" %}
If your account has MFA enabled (or required by your admin), you will still be prompted for your second factor after signing in via Google or Microsoft. SSO does not bypass MFA.
{% endhint %}


---

# 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.stoik.io/onboarding/account/sso.md?ask=<question>&goal=<user_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.