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

# Getting started

This page shows you how to log in to Transcribe and familiarize you with the features on the main page.

**Live Site:** <https://ai.ccv.brown.edu/transcribe>

### Logging in

Please utilize your Brown e-mail address to log in to the ChatCCV system, same as if you were logging into Gmail or other Google services.

* Click *Sign in with Google*.
* Log in with your Brown e-mail address.
* Select *Continue* to give CCV AI Services (ChatCCV) account permissions for you to use the site.

{% hint style="warning" %}
Brown e-mail accounts are the only accounts able to access the Transcribe service.
{% endhint %}

### The Transcribe Page

This page has three sections:

* **Usage Statistics**, for generalized information on CO2 emissions from utilizing the service, and other service-related facts.
* **FAQ**, for frequently asked questions on the service. This section is hidden on mobile devices to save screen space.
* **All Jobs**, for access to [*Create Job*](/ai-tools/services/transcribe/creating-a-job.md) and [viewing of a Job](/ai-tools/services/transcribe/viewing-jobs.md)'s status you have requested to run.


---

# 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.ccv.brown.edu/ai-tools/services/transcribe/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 `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.