My Studies · Management
Manage studies, sharing, links, and task properties.
| Study | Owners | Runtime | Config | Runs | Last Result | Actions |
|---|
My Studies · Results
Open and export run data by study.
| Study | Owners | Runs | Last Result | Actions |
|---|
Experiment Preview
Run a full experiment session before deploying links.
Analysis
Run basic descriptive reports per study using a Python or R workflow.
Report Inputs
Report Jobs
Chart Builder (On Request)
Integrations
Generate recruitment-platform launch links and completion redirects per study.
Study
This study selection is shared by both SONA and Prolific generators.
SONA Link Generator
Create SONA-friendly launch links that return participants to SONA after completion.
Prolific Link Generator
Generate a Prolific-ready external study URL for the selected study.
To Go
Package a local runtime bundle with Interpreter metadata for task-flow variants and engine options.
Quick Start Help: launch and test locally (step by step)
Launch Checklist
- In this To Go tab, choose your study/options and click Prepare And Download Bundle.
- Unzip the downloaded archive on the target machine.
- Run one launcher from the bundle root: run-kiosk.sh (Linux), Run Kiosk.command (macOS), or run-kiosk.bat (Windows).
- Wait for services to come up, then open http://127.0.0.1:8088 if your browser does not open automatically.
- For a local data-file test run, add &debug=1 to the Interpreter URL (or click Download data on completion).
Where files/data are stored
- Bundle files: stay in the folder where you unzip the archive.
- Interpreter metadata JSONs: in interpreter/metadata/ inside the unzipped bundle.
- Participant run exports (JSON/CSV): saved to the browser's default Downloads folder when debug/download export is used.
- By default local mode does not write run-result files to disk automatically; without debug/download, data is kept in-browser for that session and logged to console.
- LSL bridge container: emits markers and persists behavioral result files into local_results/ (bundle root, via Docker volume mount).
Bundle Setup
Bundling Progress
Bundle Timeline
- Ready: no bundle request yet.
Ethics & Compliance
Copy-ready boilerplate text for IRB / ethics board submissions.
Data Encryption at Rest
Use the following paragraph when describing how participant data is stored:
Participant Identifier Pseudonymisation
Use the following paragraph when describing identifier handling:
Data Transmission Security
Use the following paragraph when describing data in transit:
Data Retention and Deletion
Use the following paragraph when describing retention policy:
Access Controls and Audit Logging
Use the following paragraph when describing access controls:
Credits
Task authorship and contribution mapping using CRediT role categories.
This view follows the same principle as the Builder authorship tracker: each task_type lists its key components/features and associated contributors.
Source tracker: docs/task_feature_catalog.md from the original Builder repo.
CRediT reference: Zenodo Record 18421449
Task Scope Reference
| Task Type | Schema-backed Components In Scope |
|---|---|
| Loading task scopes… | |
Task Contribution Assignments
| Task Type | Component (Task Scope) | CRediT Role | Contributor | Notes | Actions |
|---|---|---|---|---|---|
| Loading credits… | |||||
Feedback
Send product feedback directly from the portal.
Share Feedback
Admin Panel
Manage platform users, roles, and account lifecycle.
| Username | Role | Active | MFA | Last Login | Actions |
|---|
Account Settings
Manage your credentials, MFA, and profile.
Two-Factor Authentication (TOTP)
Works with any TOTP-compatible authenticator app (for example Duo, Google Authenticator, Authy, 1Password, Microsoft Authenticator).