How the hierarchy works
Real Talk Studio uses two nested layers:- An organization is the top-level account for a company or programme (e.g. “Acme Hospitality Group”).
- Studios are learning spaces inside an organization — typically one per team, region, or cohort (e.g. “Front Desk Training”, “London Managers”).
- Studio members are the people who practice roleplays. They are separate from organization team users, who manage the account.
A studio can also exist without an organization (individual trainer accounts). In that case, the studio owner has admin access directly and there is no organization-level credit pool.
Organization roles
Super Admin
- Automatically assigned to the user who creates the organization.
- Has full administrative control over the organization and all of its studios.
- Displayed with a distinct badge in Organization → Team. There is no separate “super admin only” feature set — the role identifies the founding account.
Admin
- Added by an existing org admin from Organization → Team → Add Admin.
- Can manage studios, members, content, credits, and other org admins (except removing the last admin).
- Receives a trainer account type so they can build and run roleplays.
Member
- Added from the same Team screen with role Member — Can view organization.
- Intended for stakeholders who need visibility into the org (reporting, oversight) without day-to-day admin duties.
- Does not receive trainer/builder capabilities at the organization level.
Organization Member (team role) is different from Studio Member (learner). Organization members manage or observe the account; studio members practise scenarios.
Studio roles
Each studio has two practical roles. A user can be a studio admin through direct assignment or by being an organization admin — org admins automatically inherit admin access to every studio in their organization.
* Moving credits from the organization pool to a studio requires organization admin privileges. Studio-only admins on non-org studios manage credits differently.
How studio admin access is granted
- Direct studio admin — assigned when creating the studio or by an existing admin (typical for team leads).
- Organization admin inheritance — any organization admin can manage every studio in that organization without a separate studio admin assignment.
Studio member (learner) behaviour
- Added by a studio admin (individually or in bulk, with optional welcome emails).
- For private studios, must be an active member to view the catalog; non-members can request access and wait for admin approval.
- For public studios, the catalog may be browsable without membership, depending on configuration.
- Practice sessions consume member credits (allocated by admins from the studio pool), unless the roleplay is marked free.
- Organization admins running sessions in a studio use the organization credit pool instead of member credits.
Custom vs organization content in a studio
When a studio member opens the catalog:
The same pattern applies to presentations linked to the studio.
Credits flow
Credits move down the hierarchy:
All movements are recorded in the Ledger (organization view) and in studio-level transaction history.
SSO access grants (optional)
When SSO is configured for an organization, admins can create access grants from Organization → Team → SSO Access Grants.
This automates studio onboarding for enterprise SSO users without manual member invites.
Standalone studios (no organization)
Trainers can create a studio that is not linked to an organization:
Organization features (multi-studio management, org catalog, personas library, org ledger) require an organization.