Taking notes

Notes are an org-wide knowledge base built into TurbineX. Use them to capture findings from a study (“rated-speed oscillation only at TI > 18 %”), to share context with teammates (“use this DLC override for the gearbox team”), or as a lightweight design log alongside a running campaign.

Reaching Notes

Two entry points:

• The Notes page at /notes — full surface with search, filters, and CSV export.
• The floating Notes popup— a small button on the bottom-right of every page opens a compact list overlay alongside whatever you're working on. Useful when you're mid-study and want to jot something without breaking context.

What a note holds

• Title and body (markdown supported).
• Visibility — private (only you) or org-shared (everyone in the org).
• Optional study link— a soft reference to a specific study. The note shows up filtered on that study's Notes panel; deleting the study doesn't delete the note.
• Created / updated timestamps and the author name (always shown, even for shared notes).

Searching

The Notes page has a free-text search bar plus filters for visibility (private / shared) and linked study. Search runs across title and body. There's no full-text relevance ranking yet — matches are returned newest-first.

Exporting

The Export CSV button on the Notes page downloads every note you can see (respecting filters) as a single CSV: title, body, visibility, study_id, author, created_at, updated_at. Useful for backup or for porting to another system. There's no inverse import flow; this is one-way.

Org-level policy

Org owners can:

• Disable the Notes feature entirely for the org — the popup button vanishes and the page returns 403. Useful for orgs with strict information-handling policy.
• Set the default visibility for new notes (private or org-shared). Authors can still override per note.

Both controls live under Org settings → Notes on the Profile page. Demo / unverified accounts can read but not create notes.

Tips

• Link the note to the study you're looking at.The study's Notes panel becomes a per-campaign logbook that survives re-runs.
• Use the popup as a scratchpadfor “I should remember to” — then promote the useful ones to shared.
• CSV-export periodically if notes are the system of record for an investigation. Local backup is cheap.

Limitations

• No attachments yet — body-only. For file artifacts, use a study's Share Space.
• No comments / threading — notes are single-author. We may add threading once we see how teams actually use them.
• No mention notifications. If you want a teammate to see a note, share the URL in your usual chat.

Next steps

Ask Zeph to summarise the notes on a study (Zeph guide), or wire Notes into your scripts via the API endpoints listed under API overview.