> For the complete documentation index, see [llms.txt](https://docs.correlaid.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.correlaid.org/~/revisions/hfepfFy5E9C1WpLCChmV/wiki/faq.md).

# FAQ

## Everything seems to be on Slack! How do I get on there?

{% hint style="info" %}
If you want to become part of our Slack, drop an email to our <info@correlaid.org>. If you are already member of our Slack and would like to see your friend become part of the team, you can also [request an invite](https://slack.com/intl/en-de/help/articles/201330256-Invite-new-members-to-your-workspace#request-an-invitation) from within Slack.
{% endhint %}

## Who do I ask when about what? &#x20;

{% hint style="info" %}
Please join our [monthly onboarding call](https://pretix.eu/correlaid/open-onboarding/) or feel free to contact <info@correlaid.org>!
{% endhint %}

## I can't push to the Github repositories ("access rights" error). What's up there?

{% hint style="info" %}
You don't seem to have the correct permissions. Please drop a short email to <info@correlaid.org> and you'll be granted the correct permissions.
{% endhint %}

## I'm lost with Google Workspace or Gmail, where can I find further information?

{% hint style="info" %}
You can find more information [here](https://docs.correlaid.org/~/revisions/T8G3F1S1kUWJiGQZsj4F/wiki/infrastructure/google-workspace) or you can drop a short email to <info@correlaid.org>.
{% endhint %}

## I should have access to a group email (e.g. <konstanz@correlaid.org>) but I don’t see it when I go to [mail.google.com](http://mail.google.com)?! <a href="#i-should-have-access-to-a-group-email-eg-konstanzcorrelaidorg-but-i-dont-see-it-when-i-go-to-mailgoo" id="i-should-have-access-to-a-group-email-eg-konstanzcorrelaidorg-but-i-dont-see-it-when-i-go-to-mailgoo"></a>

{% hint style="info" %}
You need to be logged into your personal Workspace account in order to see the group mail.\
Also try:

* logging out and back in of your account
* reloading gmail
  {% endhint %}

## What is a personal account vs. a group account?

{% hint style="info" %}
Both are normal Google Workspace user accounts. The distinction is conceptual and specific to CorrelAid:

* personal account: your own account in the CorrelAid Google Workspace. For example, <phil.b@correlaid.org>. Only you have access to this account. You can have a Google calendar for your CorrelAid volunteering, send/receive emails in your function as a CorrelAid volunteer (e.g. to communicate with project partners), collaborate on Google Drive, ...
* group account: an account which is mainly there for the purpose of collaboratively managing emails, i.e. collaborative inbox. For example, each chapter has a group account / email, e.g. <konstanz@correlaid.org>. The respective local chapter heads (e.g. members of `group-lc-konstanz-heads` Google Group) have access to the credentials of this account so that they can collaboratively manage the inbox of this email address.
  {% endhint %}


---

# 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.correlaid.org/~/revisions/hfepfFy5E9C1WpLCChmV/wiki/faq.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.