> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/quick-start/create-an-admin-access-group.md).

# Create an admin access group

Before you begin building your first application, you need to make sure there is at least one access group in the organization. This guide will walk you through the process of verifying whether an access group already exists and how to create one if it doesn't.

In this example, we'll utilize an access group named *Access group for my first app*.

1. Navigate to **Groups**.
2. Verify whether the admin group "Access group for my first app" has already been created. If it has, proceed to  [Add as user](#add-a-user-to-an-access-group). If not, go to [Create new access group](#create-a-new-access-group) and follow the instructions.

## Create a new access group

1. Navigate to **Groups**.
2. Click on **Create Group**.
3. Select **Admin Group**.
4. Name the group Access group for my first app.
5. Grant access to Create Application Packages and Edit all Application Packages.
6. Click **Add user** and add yourself as a user.
7. Click **Save**.

{% tabs %}
{% tab title="Create group" %}

<figure><img src="https://1716064794-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIIgl6sNaTky0iALxYWHH%2Fuploads%2FeL1C5yvWkDwHCadtm4TR%2Fimage.png?alt=media&amp;token=fc181547-9900-4c27-ace4-7019f40d2edc" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Configure group" %}

<figure><img src="https://1716064794-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIIgl6sNaTky0iALxYWHH%2Fuploads%2FTDvS4BjGGdGMBpHmu1lm%2Fimage.png?alt=media&amp;token=d94ddb0c-cbdf-4d34-9c2a-779274500729" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

## Add a user to an access group

1. Navigate to **Groups**.
2. Find the access group *Access group for my first app*, click on the three-dot menu and select Edit.
3. Click **Add user** and add yourself as a user.
4. Click **Save**.

{% tabs %}
{% tab title="Edit access group" %}

<figure><img src="https://1716064794-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIIgl6sNaTky0iALxYWHH%2Fuploads%2FKSSYyhRiEyEInko5EnOm%2Fimage.png?alt=media&amp;token=a685404f-b23f-4c95-aa03-8f042d27eebf" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Add user" %}

<figure><img src="https://1716064794-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIIgl6sNaTky0iALxYWHH%2Fuploads%2FJIP7yj5UmhFoRmwMW6ut%2Fimage.png?alt=media&amp;token=40f6b3f7-10b8-47a3-9c25-7782ac177e4c" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}


---

# 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.novacura.com/flow-connect/quick-start/create-an-admin-access-group.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.
