Auxilison Talk with us
Documentation · Surface i

Creator Studio

Where the program creator authors the methodology, manages who's authorized to deliver it, and sees how the network is performing. The most differentiated of Auxilison's three surfaces — nothing in adjacent software categories has anything like it.

For creators and certifying bodies · Web-only · ~25 minute read

Overview

The Creator Studio is the home of the program creator's intellectual property. Every program a creator authors lives here. Every practitioner the creator authorizes is managed here. Every outcome the network produces aggregates here.

The job of the Studio is threefold:

The Studio is web-only by design. This is administrative, structural work — not work you do in line at the airport.

Top-level navigation

Dashboard

The home view. A snapshot of network health, program engagement, and any items requiring attention. Designed to answer "what should I look at today" in the first three seconds.

What's on the Dashboard

Design note

The dashboard avoids vanity metrics. Every number on it represents either an action you might take (review a flag, publish an update, onboard a practitioner) or a trend that informs a decision (engagement softening in a particular cohort, assessment scores moving in a meaningful direction). Counts that don't drive decisions are not on the dashboard.

Programs

The authoring environment. Where you build and maintain your methodology. This is the deepest area of the Creator Studio and where you'll spend the most time when shaping a new program or evolving an existing one.

Program list

Every program you've authored, organized by status:

Each program in the list shows its active enrollment count, last-published version, and authorized practitioner count.

Program editor

The studio for building a single program. The editor has eleven structural elements you can configure, each addressing a different aspect of how the program is delivered.

Program metadata

Name, description, intended population, contraindications. The information that frames what the program is for and who it's appropriate for.

Phase structure

Define ordered phases with gating rules. A phase is a structural section of the program — preparation, intake, foundational sessions, deepening, integration, completion. Phases enforce sequencing: a client cannot skip from phase 1 to phase 3 without completing phase 2.

Pathway definitions

Alternative routes through the program. A program may offer different paths for different client populations — for example, an integration program might have separate pathways for first-time participants versus those returning for additional cycles.

Session content

The actual material delivered to the client. Auxilison supports five content types within a session:

Session sequencing within a phase

How sessions order within a phase. Some sessions are strictly sequential; others can be completed in any order; others are unlocked based on client response or practitioner authorization.

Variants

Alternative versions of the same session for different client populations or sensitivities. A breathwork session might have variants for clients with respiratory conditions; a sound-therapy session might have variants for different hearing profiles. The practitioner selects (or the system suggests) the appropriate variant for each client.

Titration controls

Dose limits, pacing rules, prerequisite checks. For programs where over-administration would be clinically problematic — sound therapies, integration work, intensive somatic protocols — titration enforces what the protocol allows. The practitioner cannot accidentally accelerate the client past safe limits.

Pre-session check-ins

Configure what's asked before each session. A check-in might gather state, readiness, recent symptoms, or specific responses to questions the practitioner has set up.

Post-session reflections

Configure what's asked after each session. Reflections capture state shift, helpfulness ratings, optional written notes, and program-specific structured questions.

Linked assessments

Which clinical instruments attach at which points in the program. GAD-7 at baseline, mid-program, and completion. PHQ-9 weekly. BBCSS or BPQ20-ANS for autonomic-focused programs. Custom assessments authored by the creator.

Authorized practitioner credentials

Which credentials are required to deliver this program. A creator can specify that a particular program requires LCSW or higher, or NGH certification, or completion of the creator's own training cohort. Practitioners without the required credentials cannot enroll clients in the program.

Version control

Every program has versioned releases. When you publish a change, you control how it propagates:

Past versions are retained for historical outcome comparison. You can see whether version 2.0 is producing better outcomes than version 1.8 in the Outcomes section.

Templates

Start a new program from a structured template. Available templates include:

Templates are starting points, not constraints. Every element of a templated program can be modified.

Program preview

Experience the program as a client would, before publishing. Preview mode walks you through the entire program flow — sessions, check-ins, assessments — exactly as a client would encounter it. This catches sequencing errors, missing content, and pacing issues before any client sees them.

Network

Practitioner management. The Network area is where you see and shape who is authorized to deliver your programs.

Practitioner roster

List of all certified practitioners with the information you need to manage the network at a glance:

The roster is filterable and sortable on every dimension. Common views: "show me practitioners I haven't heard from in 60 days," "show me practitioners whose certifications expire in the next quarter," "show me practitioners delivering Program X."

Invitation and onboarding

Invite a new practitioner via email or a shareable link with credential verification built in. The practitioner accepts the invitation, completes their profile, uploads credential documentation if required, and is onboarded into your specified programs. The whole flow typically takes the practitioner 10–15 minutes.

Credential management

Track licenses, certifications, scopes, and expiration dates. Auxilison can auto-suspend access when credentials lapse, with configurable warning periods (notify the practitioner 90 days before lapse, 30 days before, and at lapse).

Credentials supported include:

Authorization assignment

Assign which programs each practitioner is authorized to deliver. Authorization is credential-gated by default — if a program requires a specific credential, only practitioners with that credential can be authorized. You can manually override credential gating when appropriate (with audit logging of the override).

Practitioner cohorts

Group practitioners by training cohort, region, specialty, or any other dimension you find useful. Cohorts make it easy to:

Compliance status

A focused view of practitioners who need attention: lapsed certifications, pending re-credentialing, flagged for fidelity issues, or otherwise requiring action.

Practitioner messaging

Communicate to the network. Send announcements, training updates, program-change notifications, and continuing-education content. Messages can be scoped to all practitioners, specific cohorts, or individual practitioners.

Active vs. inactive view

See which practitioners are actively delivering versus credentialed-but-dormant. This view drives billing — only active practitioners (those with at least one client enrolled in the past 90 days) count toward your subscription cost. Dormant practitioners remain in your network at no cost.

Outcomes

The creator's window into how the program performs across the entire network. This is the killer feature of the Creator Studio — nothing else in the adjacent software landscape does this. Every outcome data point captured by every practitioner across your network aggregates here.

Network outcome dashboard

Aggregate performance across all practitioners, clients, and programs. Headline metrics:

Cohort analysis

Compare outcomes across cohorts on any dimension you've defined:

Pre/post and longitudinal trends on attached clinical instruments. View the trajectory of assessment scores across the program arc, with statistical confidence intervals where the sample supports them.

Common assessments supported out of the box:

Engagement analytics

Completion rates broken down by phase, drop-off points within sessions, session-to-session adherence patterns, time-of-day engagement preferences, and content-type engagement (does the audio content land better than the video content for your specific population?).

Practitioner performance

Anonymous comparative view of practitioners' client engagement and outcome delta. Designed carefully to inform — not to rank or punish. The default view is anonymized so the creator can identify general distribution patterns without singling out individuals; named views are available with explicit access controls and audit logging.

Fidelity flags

Instances where the program was delivered out of sequence, with skipped phases, or with non-authorized variants. Fidelity flags are not punitive — they're an audit trail showing where actual delivery diverged from authored protocol. Some divergence is appropriate (clinical judgment); systematic divergence may indicate a content problem or a training gap.

Custom report builder

Define and save custom views for the creator's specific analytics needs. The report builder lets you combine any dimension (cohort, version, region, specialty, time period) with any metric (completion, outcome delta, engagement, fidelity) and save the resulting view for ongoing reference.

Data export

CSV export, structured data export (JSON, Parquet), and research-grade longitudinal export with appropriate de-identification options. Research exports support IRB-compliant data handling for academic partnerships and clinical studies.

Library

The shared content repository. Where program assets live, separate from any specific program. Assets in the Library can be referenced by multiple programs — updating an asset propagates to every program that uses it.

Asset types

Asset usage

For every asset, see which programs use it. Updating an asset (uploading a new version) propagates correctly to every dependent program. The system warns you when an update affects programs with active client enrollments.

Bulk upload and processing

Drag-and-drop a folder of files; the system handles auto-encoding (audio normalization, video transcoding), transcript generation, and accessibility checks (caption availability, alt-text suggestions for images embedded in PDFs). Bulk uploads are particularly useful when migrating an existing program from another platform.

Catalog

How the creator's programs are discovered and consumed. Less a marketplace than a structured presentation of the creator's portfolio.

Program presentation

How each program appears to practitioners considering enrollment. Includes a structured description, intended population, prerequisites, expected client commitment, and outcome evidence (where the creator chooses to share aggregate data).

Marketing assets

Descriptions, images, and videos that practitioners see when considering whether to add a program to their authorized list. The creator controls how the program is presented.

Enrollment workflow

How practitioners enroll into authorization for a program. Can be auto-approve (any practitioner with the right credentials can self-enroll), application-based (practitioner submits a request the creator reviews), or invite-only (practitioner can only enroll if explicitly invited).

External catalog page

Public-facing creator page, optionally embeddable on the creator's own website. Useful for certifying bodies who want to make the available programs visible to prospective practitioners considering certification.

Settings

The administrative layer. Where you configure how the Creator Studio represents your organization and integrates with the rest of your stack.

Organization profile

Creator name, logo, branding. The information used in the client experience — what clients see when they open their program. The client experience is presented as your program; Auxilison itself remains intentionally invisible.

Brand customization

Colors, fonts, voice for the client-facing experience. The Client App takes its visual identity from the program creator, not from Auxilison. Standard brand customization includes:

Billing and subscription

Current plan, active practitioner count, billing history, payment method. The billing view shows the active-practitioner count that drives your monthly cost, with a 90-day rolling window so you can see trends and project upcoming charges.

Team members

Admin users within the creator organization, separate from practitioners. Useful for certifying bodies and larger creator organizations where program authoring, network management, and outcome analysis are handled by different team members.

Roles and permissions

Standard roles: Owner, Admin, Editor, Analyst, Billing. Custom roles available with granular permission control. Every administrative action is audit-logged.

Integrations

Connected tools: CRM, email, analytics, third-party assessments. Standard integrations include Mailchimp, ConvertKit, Google Analytics, Mixpanel, Hubspot, Airtable, and Zapier (which extends compatibility to several thousand additional services).

API access

For creators with technical capability who want to extend or programmatically manage their Auxilison data. The API supports read access to network state and outcome data, and write access for program management and practitioner management. Available on Network tier and above; full read/write API access on Enterprise.

Compliance and legal

HIPAA BAA management, terms of service, data handling policies, audit log access. The signed BAA is downloadable; audit logs are exportable; data handling configuration controls how long different types of data are retained.

Notification preferences

What alerts the creator wants and how they're delivered (email, in-app, SMS where applicable, webhook for technical integrations). Granular controls let you subscribe to specific event types — for example, "notify me when any practitioner's certification is within 30 days of expiring" or "weekly digest of fidelity flags."

Begin a conversation

Tell us about your program.

The shape of your network, the methodology you've built, and what you're trying to accomplish. We'll match you to the right tier — and if your situation is unusual, we'll work out commercial terms that fit. There's no script and no pressure.