> For the complete documentation index, see [llms.txt](https://help.steeple.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.steeple.com/en/administration/lister-communautes.md).

# How do I view communities?

### View the list of communities

Go to the'**Administration** section **Communities** (`/administration/communities`).

The page displays all the communities in your organization. Use the **search bar** to find a community by its name.

#### Information displayed for each community

* **Last name** of the community
* **Number of members**
* **Number of categories** of posts
* **Number of shortcuts**
* Access to the **Settings** (gear icon)

#### Actions available on each community

* **Members** (users icon): view and manage members
* **Categories** (tree icon): manage post categories
* **Shortcuts** (link icon): manage useful links
* **Settings** (gear icon): access the community settings

### Create a community

From the page **Communities**, click the button **Add a community** at the top right.

Then choose the **community type** (static or dynamic).

For **dynamic**communities, define the selection rules (services, sites, etc.) that automatically determine the members.

The **administrator role** can be assigned to any type of community (main, manual, dynamic). It is managed from the employee profile, in the section dedicated to their community access.

### View a collaborator's communities

From the page **Employees** (`/administration/users`), each row of the table displays a column **Communities** with a button indicating the number of communities. Click it to see the list of communities the collaborator belongs to.


---

# 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://help.steeple.com/en/administration/lister-communautes.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.