---
id: KB-AD-005
url: https://app.codecontract.io/help/administration/signing-in-with-your-company-account
idioma: en
categoria: administracion
audiencia: administrador
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-AD-002, KB-ET-005]
citadoPor: [KB-AD-001]
---

# Signing in with your company account

_One password fewer, and leavers are handled automatically._

**Responde a:** configure single sign-on · sign in with microsoft or google · stop users needing another password · automatically provision users

If your people already sign in to everything with their work account, giving them one more password makes little sense. Single sign-on removes it, and along the way fixes the thing nobody remembers: closing access when someone leaves.

**En corto**

- One fewer password to manage, forget and reuse.
- Your security rules — expiry, two-factor — apply here too.
- Deactivating someone in your system removes their access here.

## What changes most

It is not the convenience of signing in: it is the leaver. An account still open six months after someone left is the commonest security failure in small companies, and with single sign-on it stops depending on somebody remembering.

| Without it | With it |
| --- | --- |
| One more password per person | The usual one |
| Leavers handled manually, if remembered | Applied automatically |
| Your password policy does not reach here | Applies as it does everywhere else |

> [!IMPORTANT]
> Before enabling it, make sure at least one administrator has an alternative way in. If your identity provider goes down and nobody can sign in, you need a service door.

> [!WARNING]
> Single sign-on does not distribute permissions on its own: it says who you are, not what you can do. Permissions are still decided here.

> [!NOTE]
> It is worth it from ten or fifteen people upward. Below that, managing accounts by hand costs less than configuring it.

**Does it work with Microsoft or Google?**

With the usual identity providers, yes.

**What about people without a work account?**

It can coexist with normal sign-in for specific cases.

**Do third-party signers come in this way too?**

No. They have no account and do not need one.

## Ejemplos

**A seventy-person company finds five open accounts belonging to people who left.**

- Enables single sign-on
- Keeps an alternative route for two administrators

→ Later leavers are cut off the same day without anyone having to remember.

**Everyone signs in with a different personal account.**

- Uses the corporate account to sign in

→ Joining and leaving follow the company.

**Somebody leaves and their access depends on a personal address.**

- Ties access to the company account

→ Departure cuts access.

**Passwords are forgotten constantly.**

- Signs in with the account they already use daily

→ There stops being one more password.

**Somebody signs in with two different accounts.**

- Merges into the corporate one

→ The history stops splitting.

**The corporate domain changes.**

- Updates the configuration before the change

→ Nobody is locked out on the day.