> For the complete documentation index, see [llms.txt](https://docs.roombelt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roombelt.com/supplemental-info/understanding-permissions-in-google-calendar.md).

# Understanding permissions in Google Calendar

When signing up for the product with a Google account, you grant Roombelt permission to access and modify your calendars. Roombelt uses this permission whenever it interacts with Google Calendar.

{% hint style="info" %}
Roombelt's use and transfer of information received from Google APIs will adhere to [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy#additional_requirements_for_specific_api_scopes), including the Limited Use requirements.
{% endhint %}

Let's call the user who signed up to Roombelt and configured devices an **admin user.** When someone taps the button to create a meeting from a tablet, Roombelt creates the meeting in the name of the admin user (The admin user will be a creator of the meeting in Google Calendar).

Moreover, Roombelt can read and edit only the calendars visible on the Google Calendar list in the admin user account (see screenshot below). If a meeting room is missing in Roombelt or marked as read-only, see [How to add missing Google Calendar room](/tutorials-and-troubleshooting/how-to-add-missing-google-calendar-room.md).

<figure><img src="/files/pfg7bLlr10rXDpFuowWv" alt="" width="265"><figcaption><p>Google Calendar UI with "My calendars" section highlighted.</p></figcaption></figure>


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.roombelt.com/supplemental-info/understanding-permissions-in-google-calendar.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
