# Signing in

Sign-in methods, what a role actually controls, and why the screen you see may differ from a colleague's.

Source: https://replicatelabs.ai/docs/getting-started/signing-in
Last updated: 2026-09-03

---

## How to sign in

Your workspace has its own web address. An administrator or your provider will have sent it to you; it is the same address every time and worth bookmarking.

Three sign-in methods are supported, and which ones are enabled is set at the account level:

<figure class="dfig">
<div class="dframe">
<div class="dtiles">
<div class="dtile"><b>Email and password</b><span>The default. Available on every account.</span></div>
<div class="dtile"><b>Google</b><span>Sign in with a Google account. Common where the organisation runs Google Workspace.</span></div>
<div class="dtile"><b>Your own identity provider</b><span>Enterprise accounts can sign in against their existing provider, Okta for example. Set up once, by agreement, during onboarding.</span></div>
</div>
</div>
<figcaption><b>Sign-in methods.</b> If single sign-on is enabled for your organisation, use it. Password accounts and SSO accounts are not automatically the same person.</figcaption>
</figure>

For the full picture, including what an administrator can see and control, read [Authentication and access](/docs/security/access).

## Roles decide what you see

A role is not a seat. One person holds a list of roles, and the surface changes to match.

| Role | What it gets |
| --- | --- |
| `user` | The rep surface. Your coach, your conversations, your roleplays and your own scores. |
| `manager` | The manager surface as well: the manager coach, and visibility of the teams you manage. |
| `admin` | Configuration as well: users, teams, knowledge, roleplays, scorecards. |

Because roles are a list, a sales leader who also runs their own deals holds `user` and `manager` on one login and switches between the two surfaces. They do not need, and should not have, a second account.

<div class="dnote key">
<span class="dnote-h">Why your screen differs from a colleague's</span>
<p>Two things drive it. Your <b>roles</b>, and the <b>coach you are currently on</b>. The buttons above the composer belong to the coach and to the active role, so a manager looking at the rep coach sees the rep buttons, not the manager ones. If a colleague describes a button you cannot find, check both before assuming it is a fault.</p>
</div>

## Team membership

Users belong to teams, and team membership carries its own role. That is how one person can be a `user` in the account overall but a `manager` of one specific team, which is the normal shape for a player-coach.

Teams also determine what a manager sees and how knowledge can be scoped. See [Users, teams and roles](/docs/admin/users-teams-roles).

## Seats

An account carries a seat limit, which an administrator can see. A seat is one named human. Accounts can be set to unlimited seats, in which case no limit is enforced.

If you cannot add a user and no error explains why, the seat limit is the first thing to check.