> For the complete documentation index, see [llms.txt](https://docs.coordinape.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coordinape.com/get-started/circles/creating-a-circle.md).

# Creating a Circle

## Setting up your Circle

You can create a circle from the Coordinape homepage or by going to <https://app.coordinape.com/new-circle>.

Clicking on the **Start a Circle** button will take you to the screen where you can create your Circle.

<figure><img src="/files/1OijtzQujQWHtIYQhwdk" alt=""><figcaption></figcaption></figure>

You can also create a new Circle in your current Org from the admin panel by clicking the Add Circle button

<figure><img src="/files/rBVEBJW78cB0je4H3VGm" alt=""><figcaption></figcaption></figure>

### Circle Information

Complete the form below to set up your organization. The Circle Admin can change these fields once the Circle is created, but only by the Circle admin.

<figure><img src="/files/w5f7FCJSo8tJuZxcWOlG" alt=""><figcaption></figcaption></figure>

### Form Information

{% tabs %}
{% tab title="Circle Name" %}
**Circle Name:** This will be the circle name that your users will select.

For Example, if your DAO is **Acme DAO \[Organization]** and you have a core team.

Your Circle name could be **Acme Core.**

**More On**

{% content-ref url="/pages/75mKABReK4auZ6ibv5mN" %}
[Circles](/get-started/circles.md)
{% endcontent-ref %}
{% endtab %}

{% tab title="Organization Name" %}
**Organization Name:** This is the higher level of your circle that will encompass all of the circles within an organization.

The Organization name will need to be verified by the Coordinape Team to prevent spoofing from another team.

**Acme DAO \[Organization]**

You might set up your Coordinape like this.

* Design Team \[Circle]
* Dev Team \[Circle]
* Community \[Circle]

\
More On

{% content-ref url="/pages/ucSSHNdmIC2cV0DaqmLi" %}
[Organizations](/get-started/organizations.md)
{% endcontent-ref %}
{% endtab %}

{% tab title="Circle POC" %}
In the "Circle Point of Contact" field, supply a contact method. If we find a bug or need to support you with an issue, we will use this information to reach out.

**Contact Methods**

Email - <yourname@domain.com>
{% endtab %}
{% endtabs %}

### Learn more about Circle Setup

*Explore potential use cases and frameworks for your organization*

{% content-ref url="/pages/75mKABReK4auZ6ibv5mN" %}
[Circles](/get-started/circles.md)
{% endcontent-ref %}

### Finishing Up

After you click **Launch Circle,** you're in! You've created your first Circle, and you are one step closer to compensating and encouraging your team.

<figure><img src="/files/7OJhqJZzfOB2q48W0SFO" alt=""><figcaption></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.coordinape.com/get-started/circles/creating-a-circle.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.