Admin & organizations

This guide covers the customer-facing admin surface on app.realtalkstudio.com — account management, distribution, and reporting. For how scenarios are built, see Scenario creation. For role permissions, see Organization & studio permissions.

Hierarchy

Organization
├── Team (org admins & org members)
├── Organization credits
├── Catalog (roleplays, presentations, personas)
└── Studios
    ├── Studio admins
    ├── Studio members (learners)
    ├── Studio credits
    └── Learning content assigned to the studio

Credits flow down the hierarchy; sessions consume credits at the member level (or org balance for org admins):

Organization credit pool
        ↓  (org admin allocates)
Studio credit pool
        ↓  (studio admin allocates)
Individual member credits
        ↓  (deducted on practice)
Roleplay session

Organization credit purchases are sales-led. Self-serve Stripe covers learner credits and admin credits (persona creation). See Plan & billing.

Organization admin

Entry point: Organizations (/organizations).

Area	What admins do	App path
Overview	Stats, credit balance, analytics snapshot, studio list	`/organizations/[id]`
Create org	Name, slug, description; creator becomes super admin	`/organizations`
Team	Add admins and members; SSO access grants when SSO is enabled	`/organizations/[id]/team`
Catalog	Org-wide roleplays and presentations; duplicate, upgrade, enhance	`/organizations/[id]/catalog`
Personas	Org persona library	`/organizations/[id]/personas`
Studios	Create and manage learning spaces	`/organizations/[id]/studios`
Ledger	Filterable credit transaction history	`/organizations/[id]/ledger`

Studio admin

Entry point: /admin/studios/[slug] (also reachable from the org studio list).

Area	What admins do	App path
Overview	Curate catalog, allocate credits, distribution tools	`/admin/studios/[slug]`
Branding	Logo, colours, promo video, creator bio	Create / edit studio
Members	Add individually or in bulk; deactivate; assign credits	`/admin/studios/[slug]/members`
Cohorts	Group learners; filter analytics and sessions by cohort	Members page
Content curation	Add, remove, feature, and reorder roleplays and presentations	Studio overview
Distribution	Embed codes, share links, single-use links	Studio overview
Analytics	Completions, scores, skills, confidence deltas, survey stats	`/admin/studios/[slug]/analytics`
Session history	Transcripts, moderation flags, CSV/ZIP export	`/admin/studios/[slug]/sessions`
Feedback config	Custom post-session survey questions	`/admin/studios/[slug]/feedback`
Toggles	Leaderboard, confidence tracking, privacy (public/private)	Studio settings
Webhooks	POST completion data to your systems	Studio webhook URL — see Webhook config

Catalog management

Scenario creation is covered in Scenario creation. Admin catalog work is management after creation:

Add to studio — assign org scenarios to a learner-facing studio catalog
Duplicate — copy a roleplay within the org
Enhance / Upgrade — AI enhancement or avatar migration on existing scenarios
Feature & reorder — highlight and order content in the studio catalog

How learners access a studio

Member management above covers the admin side. This section covers how learners get in.

Studio access modes

Three configurations control who can practise. They combine studio privacy with optional SSO.

Mode	Studio setting	Who can access	Admin workflow
Invite mode (private)	Private studio (default on create)	Only active studio members	Add members, approve access requests, allocate credits
Public mode	Public studio	Anyone can browse the catalog; studio listed on public gallery	No membership required to view catalog; learners sign in to practise
SSO mode	SSO enabled on org + studio	Users who sign in via corporate SSO	Pre-provision via SSO access grants; users appear in Members on first login — manual Add Users is hidden

Invite mode and SSO mode often apply together for enterprise: the studio stays private, but users join via SSO rather than manual invites. Public mode suits open programmes, demos, and trainer-led studios.

Entry paths

Path	Admin sets up	Learner experience
Direct invite	Studio admin → Members → Add Users (bulk or individual, optional welcome email, cohort assignment)	Receives credentials or welcome email → signs in → lands on studio
Access request	Private studio; learner not yet a member	Visits `/studio/{slug}` → Join studio → admin approves
SSO access grant	Org admin → Team → SSO Access Grants (email, initial credits, target studios, optional expiry)	Signs in via corporate SSO → automatically added to studios with credits
SSO login	Org SSO configured + studio SSO enabled	Authenticates via SSO → appears in Members on first login
Single-use link	Studio admin → roleplay → Generate single-use link (optional expiry, bulk)	Opens one-time URL → completes scenario without full studio membership
Share link	Studio admin → share link per roleplay or presentation	Direct link to a scenario; access depends on studio privacy and login state
LMS / embed	Studio admin → Embed Code → paste into LMS	Practises inside course iframe; no Real Talk Studio account required — see LMS integration

For embed sessions, analytics may attribute completions to the org/studio admin or as anonymous external users. Factor this in when reviewing session history.

Example studio landing page

Learners typically land on /studio/{slug} — a branded home with learning path, progress, and Start Practice.

Learner practice start — scenario overview before starting a session — Practice start — scenario overview, learning outcomes, and Start Practice. Learners reach this after choosing a scenario from the studio catalog or a direct link.

UI element	Purpose
Studio branding	Logo, name, description, creator bio
Next up / learning path	Ordered scenarios with progress; Start Practice CTA
Hero stats	Skills practised, sessions, practice time, average score (logged-in members)
Remaining credits	Shown for private-studio members when credits are allocated
Join studio	CTA for non-members on private studios
Catalog / Leaderboard	Links to full catalog and rankings (when enabled)

Browse public example studios at app.realtalkstudio.com/studio. Private vs public landing:

Public — catalog and learning path visible; learner signs in when starting practice
Private (non-member) — featured scenarios only; Join studio or login prompt; full path unlocks after membership

SSO access grants

When SSO is configured for an organization, admins create access grants from Organization → Team → SSO Access Grants:

Field	Purpose
Email	User who receives access when they sign in via SSO
Initial credits	Credits assigned on first login
Studios	Which studios the user is automatically added to
Expiry	Optional expiration date

Full permission tables: Organization & studio permissions — SSO access grants.

Optional / tier-gated features

Not every studio has all capabilities enabled:

Presence / non-verbal analysis (scenario + studio config)
Take Action compliance gate (category-specific)
Leaderboard and preparedness / confidence tracking (studio toggles)
Policy adherence and product knowledge scoring (scenario-dependent)
Whitelabel / Partner tier branding

Scenario creation — build scenarios before adding to catalog
Practice experience — learner session flow
Feedback & evidence — what admins export from session history
LMS integration · Webhook config · Organization & studio permissions

Overview

Product

Guides

MCP setup and management

IT Administration

Hierarchy

Organization admin

Studio admin

Catalog management

How learners access a studio

Studio access modes

Entry paths

Example studio landing page

SSO access grants

Optional / tier-gated features

​Hierarchy

​Organization admin

​Studio admin

​Catalog management

​How learners access a studio

​Studio access modes

​Entry paths

​Example studio landing page

​SSO access grants

​Optional / tier-gated features

​Related

Hierarchy

Organization admin

Studio admin

Catalog management

How learners access a studio

Studio access modes

Entry paths

Example studio landing page

SSO access grants

Optional / tier-gated features

Related