> 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/communautes/creer-communaute.md).

# How do I create a community?

### Overview

A community brings together employees around a **location**, a **department** or a **topic**. You create a **dynamic**, whose members are determined automatically by their departments and locations, or **manual**, whose members you choose. See [What are the types of communities?](/en/communautes/types-communautes.md).

### Open creation

Creating a community is reserved for **organization administrators**. There are three ways to get there:

1. **From the Communities space** : click **Create**, at the top of the left pane. The **Create a community** window opens.
2. **From Administration** : **Administration** > **Communities**, then **Create a community**.
3. **When a department or a location is added** : Steeple suggests creating the corresponding dynamic community. See [How do you manage departments and locations?](/en/administration/gerer-services-et-sites.md).

<figure><img src="https://608007981-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FByS0e17eM732OXdGGkme%2Fuploads%2Fgit-blob-a65635a0c3f754ef8125185949652ec06ab0af4f%2Fcommunautes-creer.png?alt=media" alt="La fenêtre Créer une communauté, à l&#x27;étape 1 sur 2 : nom et description"><figcaption></figcaption></figure>

The creation takes place in **two steps**.

### Step 1 — Information

Fill in:

* the **name** of the community (required);
* a **description** (optional), to explain the purpose of the community and what is shared there;
* a **image** (optional), so you can recognize it at a glance in the community list. Click **Upload an image**. Without an image, the community keeps the default illustration.

<figure><img src="https://608007981-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FByS0e17eM732OXdGGkme%2Fuploads%2Fgit-blob-71556546092dfa3269cd7eb65e45717882df379c%2Fcommunautes-creation-infos.png?alt=media" alt="Étape 1 Informations : nom, description et image de la communauté"><figcaption></figcaption></figure>

### Step 2 — Members

Choose how members are defined, using the selector **Dynamic / Manual**. **Dynamic** is selected by default.

**Dynamic** : choose one or more **departments** and/or **locations**. Several values in the same field are cumulative — with two departments, it is enough to belong to one of the two. However, the two fields are cumulative: by choosing departments **and** locations, employees who match both at once will be members. The list is updated automatically when assignments change. The rule is built from the departments and locations of your organization: see [How do you manage departments and locations?](/en/administration/gerer-services-et-sites.md).

<figure><img src="https://608007981-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FByS0e17eM732OXdGGkme%2Fuploads%2Fgit-blob-30ffa5d802e894cdeaa1233903565cec87b92401%2Fcommunautes-creation-dynamique.png?alt=media" alt="Étape Membres, mode dynamique : règle basée sur les services et les lieux"><figcaption></figcaption></figure>

{% hint style="info" %}
If your organization does not yet have any departments or any locations, the step opens by default on **Manual** : a dynamic rule would have nothing to rely on. The tab **Dynamic** remains available and explains what is missing.
{% endhint %}

**Manual** : search for and select employees one by one. You can add or remove them at any time.

<figure><img src="https://608007981-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FByS0e17eM732OXdGGkme%2Fuploads%2Fgit-blob-ebc2e922c94ec3f61d25a34b310bbed67116adfc%2Fcommunautes-creation-manuel.png?alt=media" alt="Étape Membres, mode manuel : recherche et sélection des collaborateurs"><figcaption></figcaption></figure>

Click **Create the community** to confirm.

### Content created with the community

Each new community automatically receives its first content, in its name:

* a **section**, for the community's Posts — see [How do you manage sections in Posts?](/en/news/news-rubriques.md) ;
* a **conversation**, a group discussion for members — see [Messaging app](/en/messagerie-1/application-messagerie.md) ;
* a **folder**, for sharing Documents — see [How do you manage folders and permissions in Documents?](/en/docs/docs-dossiers-permissions.md) ;
* a **calendar**, for community events — see [Calendar app](/en/events/application-events.md#les-agendas).

Their names, what members can do with them, and the case of the main community: see [What content does a new community receive?](/en/communautes/contenus-par-defaut.md).

### After creation

You are redirected to the new community space.

If you chose **Dynamic**, the addition of members happens in the background: the list may be completed a few moments after creation.

### To go further

* [What content does a new community receive?](/en/communautes/contenus-par-defaut.md)
* [How do you manage a community's members from the Communities space?](/en/communautes/gerer-membres-espace.md)
* [How do you change the membership rule of a dynamic community?](/en/communautes/regle-appartenance.md)
* [How do you designate the administrators of a community?](/en/communautes/gerer-administrateurs-communaute.md)
* [How do you manage join requests for Communities?](/en/administration/gerer-demandes-adhesion.md)
* [How do you delete a community from the Communities space?](/en/communautes/supprimer-communaute-espace.md)

### What the assistant can do

With the Administration scope, the assistant can **create a community** on your behalf, dynamic or manual: it asks you to confirm before creating it, and it receives its first content like any new community. It can also **add or remove members**, and **designate or remove administrators**.
