> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/getting-started.md).

# Get started

Sign in, find your way around, and start using Rhythms with your team.

## Get started with Rhythms

Start by signing in and learning where your work lives. Then choose the setup guide that matches your role and workspace.

### Learn your way around

1. [Sign in to Rhythms](/getting-started/basics/sign-in-to-rhythms.md).
2. [Find your way around Rhythms](/goals-and-okrs/okr-foundations-and-structure/find-your-way-around-rhythms.md).
3. [Use Quick Search](/getting-started/basics/using-quick-search-in-rhythms.md) to find OKRs and documents.

### Set up your work

Choose the path that matches what you need to do next:

* [Set up your OKR program](/getting-started/getting-started-with-goals-and-okrs.md) — configure and launch a goals program.
* [Use Rhythms in Slack](/getting-started/getting-started-in-slack.md) — work with goals, documents, and playbooks in Slack.
* [Use Rhythms in Microsoft Teams](/getting-started/getting-started-in-microsoft-teams.md) — install the Rhythms tab in Teams.

### Need help?

Visit [Troubleshooting and Support](/workspace-settings-and-administration/troubleshooting-and-support.md) for common problems and support options.


---

# 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://help.rhythms.ai/getting-started.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.