People and Teams

Every person in a studio has one role. The role is the single switch that controls their entire experience: what menus appear, whose data they can see, and whether they can build or only consume content. Salesably enforces these boundaries automatically, so you set the role and the platform handles the rest.

There are four roles, from most to least access: Admin, Supervisor, Member, and Guest. Most of your people will be Members. Guest is a limited-access role for occasional or trial users. The tables below focus on the three roles you will use day to day.

Access Comparison

Access area	Member	Supervisor	Admin
Their own results	Yes	Yes	Yes
Their team's results	No	Yes (their direct reports only)	Yes (everyone)
Other teams' results	No	No	Yes
Reports	No	Yes (filtered to direct reports)	Yes (whole studio)
Admin menu	No	Yes (limited)	Yes (full)
Configure the studio	No	No	Yes
Build practice content	No	No	Yes
Assign work to a team	No	Yes	Yes
Add new people	No	Yes (as their direct reports)	Yes (any role)

What Each Role Sees in the Admin Menu

Supervisors get a focused subset of the admin menu, scoped to running a team:

• People & Training: People (their direct reports), Communities, Assignments, Learning Paths, plus the Multiple Choice, FAQ, and Glossary test builders
• Performance: OKRs (and Badges when the studio has badges turned on)
• Insights: Analytics

Admins get everything above for the whole studio, plus the configuration sections that supervisors never see:

• Studio: Configure Studio, Positioning
• Content: Content, Glossary, FAQs, Capability Maps, Takeaway Reports
• Module Configuration: Personas, Rubrics, Stories, and the six scenario builders (Discovery, Messaging / Pitch, Outbound & Inbounds, Objections, Plays, and Management with its Other Personas)

The Line That Matters

The cleanest way to remember the split: supervisors run a team, admins run the studio. A supervisor can assign existing assignments, learning paths, and tests to their direct reports and watch their progress, but they cannot create the personas, scenarios, or rubrics that those activities are built from. Building and configuring the studio is admin-only.

Roles do not just hide menus, they decide whose data a person can see. This matters most in Reports, where the same screens show a completely different slice of people depending on who is logged in. The filtering is automatic, so you never have to hand-build views per manager.

How the Data Is Scoped

• Members have no access to Reports. They see only their own results on their dashboard.
• Supervisors see Reports, but every report is filtered to their direct reports only. A supervisor with five direct reports sees those five people, never the rest of the studio.
• Admins see Reports for everyone in the studio.

Reports access also extends to community leaders. If you group people into a community and name a leader, that leader can open Reports for their community even if their role is Member. Communities are managed under People & Training → Communities.

Why It Is Built This Way

This keeps coaching data in the right hands. A frontline rep should not browse a peer's scores, a line manager should focus on their own team without studio-wide noise, and an admin needs the full picture to make program decisions. Because the scope follows the role, adding or moving a person updates who can see them without any extra setup.

Pick a role by asking one question: does this person practice, run a team, or run the studio? That maps directly to Member, Supervisor, and Admin. (A fourth role, Guest, exists for limited or trial access and behaves like a restricted Member.)

Member

Your frontline practitioners. This is the default and the role most people should have.

• They see: their own dashboard, the assignments, learning paths, and tests given to them, and their own results and progress.
• They do not see: anyone else's results, Reports, or any admin menu.

A Member can be linked to a supervisor. That link is what lets the supervisor coach and report on them.

Supervisor

A team lead or manager who coaches a specific group. Supervisors get a limited admin menu and Reports, both scoped to the people who report to them (their direct reports).

• They can: view results and analytics for their direct reports, assign existing assignments, learning paths, and tests, set OKRs, manage communities, and add new people (who join as their direct reports).
• They cannot: see anyone outside their team, build personas, scenarios, or rubrics, or change studio settings.

A supervisor coaches with the content admins build. They consume the library, they do not author it.

Admin

The studio owner-operator. Admins have the full menu and see everyone.

• They can: see all results across the studio, build and configure every type of content, assign any role to any person, set up communities and supervisors, and change studio settings and branding.

Admins are the only role that can promote someone to Admin or Supervisor. Keep this group small.

Why the Split Exists

• Privacy: members never see each other's scores.
• Focus: supervisors see their team, not the whole studio.
• Control: admins keep authorship and configuration in one trusted place.
• Zero maintenance: the platform enforces all of this from the role, so you do not manage permissions by hand.

Assign the lowest role that lets a person do their job. That keeps data private by default and keeps content authorship in trusted hands. You can always promote someone later.

Make Someone an Admin When

They need to build or configure the studio: creating personas, scenarios, and rubrics, editing studio settings and positioning, or seeing results across every team. Keep this group small (often one to a few people). Anyone who can author content and assign roles can reshape the whole studio.

Make Someone a Supervisor When

They manage and coach a specific group but should not author content or touch studio settings. This is the role for sales managers and team leads. A common shape: 50 reps as Members, with 5 managers as Supervisors, each linked to their own direct reports. Supervisors can assign existing work, track progress, and add new people to their team without any admin-level reach.

Leave Someone as a Member When

They practice and complete assigned work and have no need to manage others or see team analytics. This is the right role for most of the studio.

Rules Worth Knowing

• A Member or Guest can have one supervisor at a time. Only admins assign or change that link.
• Promoting a Member or Guest to Supervisor or Admin removes their existing supervisor link, since managers are not supervised inside the tool.
• Supervisors can only set the Member and Guest roles. They cannot create other supervisors or admins. Only an admin can do that.
• Supervisors can use the existing content library but cannot create new personas, scenarios, or rubrics.

Day-to-day account management lives under Admin (People & Training) → People. Admins manage everyone; supervisors see and manage only their direct reports. The People list opens with tabs (admins also get Supervisors and Admins tabs to filter quickly). Click any person to open their profile, where roles, account settings, labels, assignments, and admin actions all live.

Add People

Use the Add people button on the People page. It opens one dialog with two ways to add:

• Invite link: copy a join link (or a ready-made invite email) and share it. People click it and create their own account, which lands them in your studio. There is an optional toggle to start new members in training mode so they begin in unscored practice and only see assigned content.
• Import roster: add one person with a form, or upload a spreadsheet to add many at once. Download the template first. Email, Name, Role, and Password are required; Display Name, Timezone, Supervisor, and Labels are optional. Roles must be one of member, supervisor, admin, or guest; Labels are comma-separated; Timezone uses IANA format (for example, America/New_York). You can choose whether to send welcome emails and whether new people start in training mode. After importing, the flow offers an optional step to assign learning paths, assignments, and tests to everyone you just added, all with a single due date.

Set or Change a Role

Open the person's profile and use the Role dropdown under Settings. Admins can set any role; supervisors can set only Member or Guest. The change saves immediately. Promoting to Admin or Supervisor clears any supervisor link, since managers are not supervised in the tool.

Assign a Supervisor

For a Member or Guest, a Supervisor selector appears under Settings (admin only). This is the link that gives a supervisor coaching and reporting access to that person. To build a team from the manager's side instead, open the supervisor's profile and use Direct reports → Add to attach people.

Enable or Disable an Account

Admins can flip the Account active switch at the top of a profile. A disabled account cannot log in until it is re-enabled. Use this instead of deletion when access should pause but the person's history should stay intact.

Onboarding Mode

Onboarding mode gives new people a gentler start while they learn. It does two things: it tells the AI scoring a more forgiving story (each rubric score is shifted up by one point, capped so it cannot reach the top of the scale) and it signals the practice bot that the person is still learning. It does not change the interface or the flow of a conversation. Turn it on for someone's first weeks from the Onboarding mode toggle on their profile, then turn it off once they are up to speed so their scores reflect real performance.

Training Mode

Training mode strips the app down to the essentials for focused onboarding: it restricts navigation to learning paths, assignments, and the screens needed to complete them. It is meant for Members and Guests and is not available for admins or supervisors. You can also start new people in training mode from the invite link or the import flow.

Scored Mode

The Enable scored mode toggle controls whether a person can run scored simulations on their own. When it is off, scored practice is available only through assignments and learning paths, which is useful when you want self-directed practice to stay unscored and reserve scoring for assigned work.

Labels

Labels are tags you attach to people (for example, by team, cohort, or region) to organize and group them. From a profile, open Manage labels to apply the studio's existing labels to that person. You can also set labels in bulk during import using the optional Labels column (comma-separated).

Admin Actions

The Admin actions panel on each profile holds the account operations you reach for less often:

Action	What it does
Remove user	Permanently removes the person from the studio. This cannot be undone. To pause access instead, disable the account.
Set password	Sets a new password directly for the person.
Send password reset email	Emails reset instructions (with an optional CC).
Reset two-factor auth	Clears their 2FA secret so they set it up fresh on next login. Use when someone is locked out of two-factor.
Resend welcome email	Re-sends the original welcome and sign-in instructions.

Admins (and super users) can also Impersonate a person from their profile to see the studio exactly as they do, which is handy for troubleshooting. Treat Remove user with care, since it deletes the account and its history.