Getting started
Signing in
Sign-in methods, what a role actually controls, and why the screen you see may differ from a colleague's.
#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:
For the full picture, including what an administrator can see and control, read Authentication and 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.
Two things drive it. Your roles, and the coach you are currently on. 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.
#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.
#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.
Last updated 3 September 2026
View as Markdown