---
id: KB-ET-011
url: https://app.codecontract.io/help/your-workspace/letting-your-team-join-by-email-domain
idioma: en
categoria: espacio-de-trabajo
subcategoria: usuarios
audiencia: administrador
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-AD-006, KB-AD-002]
citadoPor: [KB-PR-011, KB-AD-010, KB-ET-017]
enLaApp: https://app.codecontract.io/settings/organization
---

# Letting your team join by email domain

_Anyone with a company email joins without an invitation. And why that has a limit._

**Responde a:** let employees join the organisation automatically · automatic signup by email domain · i do not want to invite one by one · domain-based auto-join

With twenty people, inviting one by one is a chore. With two hundred, it is a task nobody finishes. The alternative is authorising your domain: anyone registering with a company email joins directly.

## How to enable it

1. **Go to Settings → Organisation.**
2. **Enter your email domain.**
3. **Tick that joining by domain is allowed.**

> [!IMPORTANT]
> It only works with your own domain. It cannot be enabled with gmail.com, hotmail.com or any other free email, and that is blocked deliberately: authorising gmail.com would mean anyone in the world with a Gmail account joins your organisation. That is a hole, not a limitation.

## What to decide first

| Question | Why it matters |
| --- | --- |
| Should everyone with a company email join? | In some companies yes; in others whole departments have no business here |
| With what permissions? | Joining is not the same as joining as an administrator |
| What happens when someone leaves? | If their email is deactivated they can no longer join; if not, they still can |

> [!WARNING]
> This does not replace removing leavers. If your company keeps email active for a while after departure, that person can still get in. Removal is done the same way.

> [!NOTE]
> If you have corporate sign-in, this is redundant: there, who gets in and who stops is decided by your identity system, which is more precise.

**Can I have several domains?**

The authorised domain is one; for multi-brand cases, ask.

**Do they join as administrators?**

No. They join with the basics and permissions are adjusted afterwards.

**Can I disable it later?**

Yes, and those already in stay; new people stop joining.

## Ejemplos

**A 180-person company wants everyone able to look things up without individual invitations.**

- Authorises its corporate domain
- Sets the joining profile to read-only

→ People join by themselves and broader permissions are granted by hand, which are few.

**Each joiner is invited by hand, one by one.**

- Allows entry by corporate domain

→ Onboarding stops being a manual formality.

**Somebody from a similar but unrelated domain gets in.**

- Checks which domains are allowed

→ Only the right people get in.

**A supplier with an address on the same domain gets in unintentionally.**

- Reviews the domain before enabling it

→ The door opens to the right people.

**Somebody joins and nobody assigns them permissions.**

- Defines the default role

→ Whoever joins can work without waiting.

**It is switched off and some users already came in that way.**

- Reviews who came in through it

→ The change leaves no gaps.