Notes by Auribus
Back to home

FAQ

How Notes by Auribus works

Pick a topic below, or scroll through answers about sharing, billing, files, the review interface, and workflow.

⌘K

12 questions across all topics

Common questions

Sharing, access, and approval basics

01

Does my client need an account?

Preview links are public; commenting and other write actions require signing in and claiming the invite.

When you share a project, Notes generates a secure invite link. Anyone with the link can open a read-only preview of the project and its tracks without creating an account first.

If a collaborator wants to leave feedback, they sign in (or create an account) and claim the invite. The role you assign on the invite — Client or Viewer — controls what they can do after claim.

Clients can comment when a track is in review. Viewers can listen and read but cannot write. Owners always retain upload, status, and deletion controls.

How it works

  1. 1

    Owner creates an invite

    From Share access, you generate a link or send an email invite and pick Client or Viewer.

  2. 2

    Recipient opens the preview

    The /share/{token} page loads project and track metadata with no login required.

  3. 3

    Write actions gate on auth

    Commenting, voice notes, and invite claim run only after Cognito sign-in; the server enforces role permissions on every mutation.

Share access — invite link, role picker, and what guests can do before and after sign-in

notes.auribus.io/share/a8f3…k2m9

Without account

  • Open preview link
  • Play tracks & read comments
  • Leave comments (sign in required)

After sign-in + claim

  • Role applied from invite
  • Redirect to /review?projectId=…
  • Server enforces permissions

Quick answer: Anyone can open the shared preview link. Authentication is required for write actions, depending on role and flow.

03

What is an approval receipt?

When a track moves to Done, Notes records who closed the loop and when — exportable as plain text.

An approval receipt is not a legal contract on its own; it is a durable audit trail inside Notes showing that a specific reviewer marked a track Done (or requested changes) at an exact time.

The receipt includes reviewer display name, UTC-localized timestamp, optional note, track name, and final status. Owners can download it as a .txt file for archives or client records.

Status changes are owner-only. Collaborators comment during In review; the owner moves the track through Draft → Sent for feedback → Done.

How it works

  1. 1

    Track reaches In review

    Owner uploads a version and sets status so clients can leave timestamped feedback.

  2. 2

    Owner marks Done

    From the approval panel or kanban, the owner transitions the track to Done when feedback is resolved.

  3. 3

    Receipt is generated

    Notes stores reviewer, timestamp, and note; the Approval panel exposes a download action for the text receipt.

Approval panel — Done state card and the downloadable text receipt file

Done

Summer Campaign — Final Mix

NOTES BY AURIBUS — APPROVAL RECEIPT
Track: Summer Campaign — Final Mix
Status: DONE
Reviewer: Alex Rivera (Owner)
Timestamp: 2026-07-08T14:32:00Z
Note: Client sign-off received via email.

Quick answer: A timestamped text record generated on approval with reviewer identity, date/time, and optional note.

04

Can clients upload new versions or delete tracks?

Collaborators comment and review; project owners control files, versions, and workflow.

Notes separates creative feedback from project administration. Clients and viewers cannot upload new revisions, delete tracks, change kanban status, or manage billing.

Owners can upload versions, soft-delete tracks, archive projects, invite members, and move approval states. Clients comment when a track is In review; viewers are read-only.

This prevents accidental overwrites during a review cycle and keeps a single person accountable for what version is officially 'out for feedback.'

How it works

  1. 1

    Role is set on invite

    Share access assigns Owner (you), Client, or Viewer per member.

  2. 2

    Server checks every action

    tRPC routers call permissions.canUpload, canChangeTrackStatus, and canDeleteTrack before mutations succeed.

  3. 3

    UI mirrors the rules

    Upload buttons, status menus, and delete controls render only when the signed-in user is the project owner.

Permission matrix — which actions are available to Owner, Client, and Viewer

ActionOwnerClientViewer
Upload new version
Delete track
Change status (kanban)
Comment (in review)
Voice note replyStandard
Invite collaborators

Quick answer: No. Uploading, deletion, and status control are owner-only permissions.

Billing & plans

Subscriptions, tiers, and cancellation

05

What is the main difference between Starter and Professional?

On the product today: Free vs Standard — voice comments, transcription, storage, and member limits.

Homepage copy uses Starter / Professional as shorthand. In the app, plans map to Free and Standard (Premium is reserved for a future tier).

Free includes core waveform review for small projects: about 700 MB storage, up to 2 owned projects, and 2 members per project. Text comments and share links are included.

Standard removes those caps for practical team use (50 GB storage, unlimited projects and members) and enables voice-note replies in comments plus transcription features.

How it works

  1. 1

    Subscribe in Settings

    Plans & billing opens Stripe Checkout for Standard or the customer portal to manage payment.

  2. 2

    Entitlements sync to your account

    Notes reads tier limits on upload, invite, and voice-comment actions and blocks over-limit usage with upgrade prompts.

  3. 3

    Bundles with Voice

    Auribus bundle subscribers can inherit Standard-equivalent limits without a separate Notes subscription.

Plans comparison — Free (Starter) vs Standard (Professional) limits side by side

Starter (Free)

$0
  • 700 MB storage
  • 2 owned projects
  • 2 members per project
  • Text comments & share links
  • No voice-note replies

Professional (Standard)

Paid
  • 50 GB storage
  • Unlimited projects & members
  • Voice-note comments
  • Transcription
  • Priority collaboration limits

Quick answer: Professional unlocks voice-note feedback and broader collaboration limits.

06

Can I cancel anytime?

Manage or cancel Standard through the billing portal; Free tier has no subscription to cancel.

Paid plans bill through Stripe. From Settings → Plans or Billing, Update plan opens the Stripe customer portal where you can cancel, change payment method, or download invoices.

After cancel, your subscription remains active until the end of the current billing period. When it lapses, the account moves to Free tier limits; projects and media are retained subject to storage retention policy.

You can resubscribe at any time without losing project history, as long as data is within the Free retention window.

How it works

  1. 1

    Open Settings → Billing

    Authenticated owners see current tier, renewal date, and portal shortcuts.

  2. 2

    Stripe portal handles cancel

    Cancel at period end is immediate in Stripe; Notes picks up the webhook and updates entitlements.

  3. 3

    Free tier resumes

    Upload and invite limits tighten to Free defaults; over-limit retention emails may apply per storage policy.

Settings billing — current plan, renewal date, and Stripe portal actions

Current plan

Standard

Renews Aug 8, 2026

Update payment methodStripe portal
Download invoicesStripe portal
Cancel at period endStripe portal

Quick answer: Yes, cancellation is self-serve in account settings.

Files & projects

Uploads, formats, and project structure

02

What audio formats are supported?

Common lossy and lossless formats upload through the same scan-and-stage pipeline.

Notes accepts the formats teams already export from DAWs and mastering tools: MP3, WAV, FLAC, OGG, and AIFF, plus other browser-safe audio types.

On upload, files land in private S3 storage under your project. An optional audio scan pass reads loudness, peak, and technical metadata before you publish the track or version.

Each published upload becomes a numbered revision (v1, v2, …) with comments scoped to the version collaborators are reviewing.

How it works

  1. 1

    Choose a file in the upload modal

    Drag a mix or stem into the scan upload flow from the dashboard or review page.

  2. 2

    Staging scan runs

    Lambda analyzes the file while you confirm title and project; QC readouts appear in the bento panel.

  3. 3

    Track version is created

    On save, the file is linked to the project, v1 (or the next version) is written, and collaborators see it on the share link.

Upload modal — supported formats and the pre-publish loudness / peak scan panel

MP3WAVFLACOGGAIFFM4A

Drop mix_master_v3.wav

Staging scan runs before publish

Integrated LUFS

-14.2

True peak

-1.1 dBTP

Duration

3:42

Quick answer: MP3, WAV, FLAC, OGG, AIFF, and related web-safe audio formats.

12

How are projects and tracks organized?

Level 1 is your project library; Level 2 and the review playlist are two ways to navigate tracks inside a project.

A project groups related tracks (an album, campaign, podcast season, etc.). The /projects page lists your owned and shared projects as thumbnails or a table, with filters for shared access and archived work.

Opening a project enters Level 2: all tracks in that project with kanban, icon grid, or list views. Upload, share access, and archive live here.

The review page playlist (FileSystemView) adds Icon, Boards, and Files tree modes to switch tracks without returning to the dashboard. URL state (?projectId & trackId) remembers your place.

Versions stack per track (v1, v2, …). Comments can be version-scoped; collaborators always review the latest unless comparing A/B. Soft-deleted tracks and projects are hidden but recoverable within the retention window.

How it works

  1. 1

    Create a project

    From the dashboard grid, name the folder and optionally set a thumbnail from track art.

  2. 2

    Add tracks and versions

    Upload into the project; each revision bumps the version number while history stays browsable.

  3. 3

    Share and review

    Invite collaborators at project level; they land in review with the playlist sidebar for track switching.

Projects library and track views — Level 1 grid, Level 2 kanban, and review playlist modes

Level 1 — Projects

Q3 Campaign

4 tracks

Podcast S2

4 tracks

Brand Film

4 tracks

Level 2 & review playlist

ThumbnailsKanbanFiles treeReview

Review interface

Waveform, comments, sidebar, and timeline

07

How does the waveform player work?

The waveform is the center of review — real audio peaks, timestamped markers, and tools for precision listening.

Notes decodes your uploaded file into a true peak waveform (not a placeholder). Comment markers appear as pins on the timeline; hover or tap them to jump to that moment.

Zoom (scroll wheel, pinch, or +/- controls) expands the timeline horizontally so you can inspect transients, edits, and fades. At zoom 1 the full track fits the viewport; above 1 you pan by dragging the waveform.

Range selection lets you highlight a start and end time. Playback loops inside that window — useful for reviewing a single line, chorus, or SFX hit without re-scrubbing manually.

The full-track transcript panel (Standard) runs Deepgram on the master and shows clickable words synced to playback. That is separate from per-comment voice-note transcripts described in the comments section.

How it works

  1. 1

    Click or scrub the waveform

    Sets the playhead and opens the comment composer at that timestamp when you add feedback.

  2. 2

    Enable range mode

    Drag two handles on the timeline; audio loops between them until you clear the selection.

  3. 3

    Open Transcript

    Side panel or bottom sheet lists words with timings; selection on the waveform can scope transcription to a passage.

Live waveform — play, zoom, drag a loop range, and click comment markers on the real review player

08

How do comments, voice notes, and reference audio work?

The comment composer supports three feedback types; replies thread flat under the root comment.

Click the waveform (or use Add comment) to open the inline composer at the current time. Text supports @mentions of project members so they get notified.

Voice notes (Standard) record directly in the browser — hold the mic, preview playback, then post. The voice file is stored in S3 and appears as a playable chip in the thread.

Reference audio lets you attach an alternate take, guide track, or example clip from disk. It uploads as a separate file linked to the comment, not mixed into the master.

Voice message transcript: on Standard, tap the waveform icon on any voice comment or reply. Notes sends the clip to Deepgram and shows the text inline — useful for search, accessibility, and quoting feedback in email. Track-level transcription (the full mix) is a separate panel opened from the transport bar.

Replies flatten under the root thread: parentId groups the conversation while replyToId preserves who you answered. Owners and authors can delete their own comments; owners can delete any.

How it works

  1. 1

    Pick a timestamp

    Every comment stores start time (and optional range) so feedback stays tied to the mix.

  2. 2

    Choose feedback type

    Type text, record voice, or attach reference — or combine text with audio.

  3. 3

    Collaborators reply in-thread

    Voice replies use the same chip player; clicking a comment seeks the waveform to that moment.

Live comment area — real composer with text, mic, and reference attach, plus a voice note and sample transcript in the sidebar

10

What is timeline mode?

Toggle from the header when you want feedback inline on the timeline instead of in the right panel.

Timeline mode hides the comments sidebar and renders TimelineComments beneath the waveform. Each thread is a card on a horizontal axis positioned at its timestamp — zooming the waveform widens the filmstrip in sync.

Click a card to seek; double-click can expand actions depending on role. Resolved vs open threads use the same status colors as the sidebar. Panning the timeline scrolls the comment strip; on the review page this stays locked to waveform zoom.

Use sidebar mode for day-to-day threaded review; use timeline mode for presentations, spotting sessions, or when you want the whole feedback map visible at once without a separate panel.

The full-track transcript panel can still open from the transport bar in either view. Voice-note transcripts remain on each comment's audio chip in both modes.

How it works

  1. 1

    Toggle view in the header

    Desktop review page switches between Sidebar and Timeline; mobile always uses the tabbed sidebar pattern.

  2. 2

    Comments anchor to time

    Cards sit at their timestamp on the horizontal axis; zoom expands detail for dense sessions.

  3. 3

    Same data, different layout

    Threads, replies, voice notes, and statuses are identical — only the presentation changes.

Live timeline mode — real waveform with TimelineComments filmstrip below, synced to the same demo track

Workflow

Kanban columns and track status

11

How does the kanban board work?

The project dashboard kanban mirrors the approval workflow every track follows.

Level 2 of the project dashboard (and Boards view on the review playlist) shows one column per approval status: OPEN (Draft), IN_REVIEW, CHANGES_REQUESTED, and DONE.

Owners drag a track card between columns; a confirmation popover explains the transition before it saves. Clients never see Draft or Done columns — only tracks actively in review.

Status labels are role-aware: what the owner calls 'Sent for feedback' a client sees as 'Ready for feedback.' Comment permissions follow status — clients can only write during In review.

Dropping a new audio file onto a column opens the upload modal with that status pre-selected, so you can publish straight into the right stage of the workflow.

How it works

  1. 1

    Upload or create a track

    New work starts in Draft (owner-only) until you send it for feedback.

  2. 2

    Drag to In review

    Collaborators receive access to comment; their feedback accumulates on the latest version.

  3. 3

    Resolve and mark Done

    Owner moves to Done when approved; receipt is available and comments lock for clients.

Project kanban — four status columns with track cards and a drag target highlight

Draft

Intro VO

Sent for Feedback

Hero Mix
Sting v2

Ready to Work

Bed + FX

Done

Final Print

Still have questions?

Contact us