> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/screen-recorder/getting-started/install-and-sign-in.md).

# Install and sign in

Install Screendesk Screen Recorder from the [Chrome Web Store](https://chromewebstore.google.com/detail/screendesk/ahlekhjogfceepmgfhpbombbepcgjcao), then pin it to Chrome's toolbar.

## Connect your account

1. Click the Screendesk icon.
2. Choose **Sign In**, or **Create Account** if you are new to Screendesk.
3. Complete sign-in in the Screendesk window and follow the prompts to connect the extension.
4. Return to the extension to start a capture.

You do not need to copy an API key into the extension.

If the connection does not finish, check that you completed the sign-in window, then reopen the extension. Sign in to the account and workspace where you want your captures uploaded.

## Start your first capture

Choose **Capture Screenshot**, **Record Tab** or **Record Desktop**, or enable **Instant Replay** for the current website.

Review your capture and choose **Upload** to save it to your workspace and get a shareable link. Camera and microphone access are separate permissions; you can record your screen without enabling either.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/screen-recorder/getting-started/install-and-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 `build a script that syncs our docs to a CMS` 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.