# Community

> The community is the unit of everything on Memberfy. Address, brand, structure, people and money belong to it, and nothing crosses from one community to another.

On Memberfy, a **community** is your whole environment: one address, one brand, one menu of sections and spaces, one list of members and one till. Everything you create — a post, an event, a plan, a sale, a payout — belongs to one community, and to that community only.

## Why think of it this way

Because the community is what separates one customer from another. A coding school, a coworking space in São Paulo and a company's HR team can all be on Memberfy at the same time, and none of them sees anything of the others: not members, not content, not money.

| Example | How it's set up |
|---|---|
| A school with courses and mentoring | One community, with sections for courses, cohorts and plans |
| A coworking space | One community, with announcements, a calendar and the residents' plan |
| A company with a customer community **and** an employee community | Two communities, with separate brands, rules and tills |

## What belongs to each community

| | What it is | Where you change it |
|---|---|---|
| **Address** | A subdomain of `memberfy.net` or a domain of your own. It's how the platform knows which community to show | [Custom domain](/configuracoes/dominio-proprio) |
| **Brand** | Name, description, logo, favicon, sharing image and the two color scales | [General settings](/configuracoes/configuracoes-gerais), [Colors](/configuracoes/cores) |
| **Main language** | The language of the emails and the starting point for newcomers | [Languages](/configuracoes/idiomas) |
| **Structure** | The menu's [sections](/conceitos/secoes) and [spaces](/conceitos/espacos) | Side menu |
| **People** | The [profiles](/conceitos/conta-e-perfil) of everyone who takes part, with their [role](/conceitos/papeis-e-permissoes), tags and groups | **Administration › Members** |
| **Entry rules** | Whether sign-up is open and whether visitors see what is public | [Sign-up and entry](/membros/cadastro-e-entrada) |
| **Money** | Products, plans, coupons, sales, balance, payouts and the payout account | **Administration › Monetization** |

## How a community is born

During the closed beta, the Memberfy team creates the community from your request. It comes with:

- the agreed name, address and language;
- you as **owner**, with a temporary password valid for 7 days;
- the ranking (gamification) turned on;
- a **Home** section with a **Feed** space, marked as the initial section.

See [Getting your community](/primeiros-passos/como-ter-sua-comunidade).

## One person, several communities

The same person can take part in more than one community, with a different role in each: owner of one, member of another. The login (email and password) is the same; the profile, role, tags and points belong to each community. See [Account and profile](/conceitos/conta-e-perfil).

## The till belongs to the community

Each community receives its own sales, has its own balance and pays out to its own bank account, registered in its [Business Information](/pagamentos/informacao-comercial). Two communities of the same company have two tills.

## Deleting the community

Only an **owner** can delete the community. This takes down the address, the structure and every member's access. Before you even consider it, pay out the balance and talk to the Memberfy team.

## Frequently asked questions

**Can I have two communities?**
Yes. Each one is created from a request and has its own address, brand and till.

**Can a member of one community see the other?**
No. Only if they are invited to it or sign up there too.

**Can I change the name later?**
Yes, in **Settings › General**. The address is a different matter: changing it is arranged with the team.

**Where do I find the community ID for the API?**
In `GET /api/communities/my`, which lists your account's communities with the `id` and your role in each one.

## In the API

The community of each call comes from the `X-CommunityId` header. It decides where the operation happens and which role the person has. See [X-CommunityId](/api/x-community-id).

## Related

- [Roles and permissions](/conceitos/papeis-e-permissoes)
- [Sections](/conceitos/secoes)
- [General settings](/configuracoes/configuracoes-gerais)