---
id: KB-ET-001
url: https://app.codecontract.io/help/your-workspace/setting-up-your-organisation
idioma: en
categoria: espacio-de-trabajo
subcategoria: cuenta
audiencia: administrador
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-PS-001, KB-ET-002, KB-ET-003, KB-ET-019]
citadoPor: [KB-ET-002, KB-CC-001, KB-AD-001, KB-PS-003, KB-ET-004]
enLaApp: https://app.codecontract.io/settings/organization
---

# Setting up your organisation on day one

_The four settings worth getting right before you send your first document._

**Responde a:** how do I change my organisation's name and logo · setting up the account for the first time · put my company logo on the emails that go out · what to do after creating the account

You can start working without configuring anything, but four things are worth settling before your first send, because changing them afterwards does not fix what already went out: your contacts will have received a generic email under the wrong name.

**En corto**

- Your name and logo appear on everything your contacts receive.
- Connecting your email makes notices come from your own domain and stay out of spam.
- Badly configured internal alerts end up muted by the whole team.
- Each contact's language decides what language they receive, not yours.

## 1. Name and logo

It is the first thing the person you are asking for a document sees. A notice arriving with your company name and logo gets opened; a generic one looks like phishing and ends up in the bin. Change it in Settings → Organisation; it affects everything sent from that moment on.

## 2. Connect your email account

Notices can go out from your own domain instead of a generic one. This is the single biggest improvement to deliverability: an email from your domain, with your authentication records in order, lands in the inbox. One without them lands in spam, and you conclude the supplier is not replying.

> [!WARNING]
> If notices still land in spam after connecting your email, an authentication record on your domain is almost always missing. That is for whoever runs your DNS, not for the platform.

## 3. Alerts

The defaults notify fairly generously. It pays to turn them down at first and raise them later: a team receiving thirty platform emails a day ends up filtering all of them, including the ones that mattered.

## 4. Contact language

Each contact carries their language on their record, and that is what is used when writing to them. Noting it when you add a foreign supplier saves the "I do not understand what you are asking for" conversation.

## Frequently asked questions

**Can I change the logo later?**

Yes, whenever you like. What does not change is what already went out: emails sent with the previous logo stay as they were.

**Is connecting email mandatory?**

No, it works without it. But response rates drop noticeably, because notices come from a domain your contacts do not recognise.

**Can I have several organisations under one account?**

Yes. One person can belong to several organisations and switch between them; each one's data is kept separate.

**Who can change these settings?**

The owner and administrators. An editor can work normally but cannot touch the organisation's configuration.

## Ejemplos

**An accountancy starts using the platform and sends its first fifty requests without configuring anything.**

- Notices half of them never reply
- Checks that notices were going out from a generic domain
- Connects their email and resends

→ The second batch gets three times the response rate, with the same text and the same people.

**Everything is configured before there is a real case.**

- Configures the minimum and adjusts with use

→ The configuration answers what actually happens.

**The whole team is invited on day one.**

- Whoever will use it that week comes in first

→ Nobody receives access to something empty.

**Twenty folders are created before there are documents.**

- Creates the structure as it is needed

→ The structure reflects the real work.

**Nobody decides who administers.**

- Names two administrators from the start

→ The account does not depend on one person.

**The organisation's name and details are left half done.**

- Completes them before sending anything out

→ What a third party receives is recognisable.