> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/docs/get-started/sign-in.md).

# Sign in and out

Sign in with your OTOY account or an access token, choose whether to stay signed in, and log out.

Open the [Render Network web app](https://render-beta.otoy.studio/).

## Sign in

{% tabs %}
{% tab title="OTOY account" %}

1. Select **sign in** on the login page.
2. Check **Remember me** if you want to stay signed in after closing the browser.
3. Click **Sign in with OTOY** and complete sign-in on OTOY's page.

You return to the web app after signing in.
{% endtab %}

{% tab title="Access token" %}

1. Select **use token** on the login page.
2. Paste your token into **Access token**.
3. Check **Remember me** if you want to stay signed in after closing the browser.
4. Click **Sign in**.

For full web app access, use a personal token with **All permissions**. See [Access tokens](/docs/web-app/access-keys.md) to create one or change its permissions.
{% endtab %}
{% endtabs %}

With **Remember me** unchecked, sign-in lasts for that tab. With it checked, the browser remembers your sign-in across tabs and browser restarts in the same browser profile. OTOY's own sign-in state is separate from this choice.

If **Select Layout Style** appears after signing in, choose your [layout and colour theme](/docs/web-app/appearance.md).

## Sign out

Click your name or account icon at the bottom of the sidebar, then click **Log Out** in the account menu.

If other tabs share the same remembered sign-in, they are signed out too.

## If sign-in fails

For OTOY sign-in, check your connection and try again. For token sign-in, check that you pasted the complete token and that it has the permissions you need. You can use **sign in** to return to OTOY sign-in instead.


---

# 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://know.rendernetwork.com/docs/get-started/sign-in.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.