Studio Team Handbook

Welcome

The Pür Cunda digital ecosystem and the purpose of this handbook.

Pür Cunda Recording & Residence is the world's first residential studio with a comprehensive digital platform — bringing studios, online services, gastronomy, residence and events under a single roof on Cunda Island. The platform is the nervous system of daily operations: every session, every equipment move, every artist request leaves a trace in the system.

This handbook is written for you — the studio team — to answer the questions "what is where, how does it work, why is it like this" the first time you open the software. The content is divided into four parts: General (login and navigation), Modules (what each page does), Scenarios (real daily workflows) and Reference (glossary, troubleshooting, contacts).

Five Pillars

In Phase 1 the studio and online services are fully active; in Phase 2 gastronomy, residence, and events fill in. For now studio + online is the centre of daily work; the other modules exist but are not heavily used yet.

Login & Account

First login, password reset, session rules, language selection.

The URL

The internal app URL will be shared with you separately. This is Pür Cunda's team-side platform. The public site at purcunda.com (WordPress) is separate — it's the marketing front; we are the team side. Don't mix them up.

First Login

Password Reset

On the login screen click "Forgot password". Enter the 6-digit code sent to your email, then choose a new password. The code is valid for 10 minutes; if it expires, restart the flow.

Session Lifetime

• Access token: 15 minutes. Validated on every API call; auto-refreshed when expired.
• Refresh token: 7 days, stored in an httpOnly cookie. While the tab is open it silently refreshes in the background. Browser extensions can't touch it.
• 5 failed attempts: account locks for 15 minutes. Even password reset won't help during the lockout — you have to wait.

Language

Profile > Settings > Language. Türkçe, English, Deutsch, Français. The whole UI and all emails follow your choice. This handbook is published only in TR and EN — toggle with the TR ↔ EN switch in the top-left.

Account Security

• Change password at least every 6 months (the system reminds you).
• Suspicious-login alerts (new IP / new device) drop into your email. The "Wasn't me" link revokes all refresh tokens — everyone has to sign in again.
• Don't share your account. New assistant? System admins will create a separate account.

UI Tour

Sidebar, top bar, theme, keyboard shortcuts.

Sidebar

The left-hand menu is the centre of navigation. Studio roles see these links:

Sidebar Behaviour

• Collapse: click the small bar on top to switch to icon-only mode (frees space when DAW is on the same monitor).
• Notification dot: a red number next to a menu item means there's pending work (e.g. unassigned online project, timesheet awaiting approval).
• Mobile: below 900px the sidebar hides; tap the button in the top-left.

Top Bar

Three things in the top-right:

• Bell: confirmed sessions, assigned work, incoming messages. Click to see the list.
• Theme: dark (default) or light. The Pür Cunda cream (#F1ECE2) is applied to light mode too; the colour system stays consistent.
• Profile avatar: settings, language, sign out.

Keyboard Shortcuts

Dashboard

The first page you open every day. The studio's pulse.

Purpose

Dashboard gives a one-hour photograph of studio operations: which sessions are happening today and tomorrow, which rooms are occupied, which client is in the building, which requests are waiting for an answer, how many projects are in the online queue. When you sit down in the morning and ask "what should I do?", this is the first answer.

How to open

Sidebar → Dashboard  /dashboard  (default after login).

What's on the page

1. KPI Cards (top row)

Click the numbers — they take you to the related page. Clicking 4 / 6 Free Rooms opens /rooms and shows you which four are free.

2. Today & Tomorrow Table

Two columns: Today and Tomorrow. Each row shows time, client, room, assigned engineer, status badge.

• Reserved — Client booked it; not yet confirmed.
• Confirmed — Confirmed; equipment/room prep should start.
• In Progress — Room currently in use, engineer is inside.
• Stopped — Temporarily paused; not finished.
• Cancelled — Cancelled; cancellation policy applied.

3. Room Status Grid

Six cards: Studio A, B, C, D, Mastering Suite, Musicians' Lounge. Each card shows:

• Room name + size
• Currently free or busy (green/orange dot)
• If busy: which session, which engineer, when it ends
• Next reservation (if any)

4. Incoming Requests Feed

In the right panel artist requests stream in (those AI-routed to the studio department). Each shows: who sent it, summary, priority (urgent/normal), source (app/WhatsApp/in-person).

• Seen — request acknowledged.
• Resolved — closed; action taken.

5. Online Projects Widget

A summary of the online mixing/mastering queue. Each row: client, service, status, assigned engineer (if any). Click the widget → goes to /online-services.

Sessions

Individual sessions — start, stop, assign engineer, attach files.

Purpose

A session is a single recording/mix/mastering meeting in a physical room. A project may contain dozens of sessions — for example, "Tarkan 2026" project: 12 sessions for vocals, guitars, percussion, mix, master, etc.

This page lists, creates and edits sessions. The Calendar (/calendar) is the visual form of the same data — there it's "when", here it's "what was done".

How to open

Sidebar → Sessions  /sessions.

What's on the page

• Top filter bar: search, room filter, status filter, date range.
• Table: Date · Time · Client · Project · Type · Room · Engineer · Status.
• Top-right "+ New Session" button — opens a modal.
• Click a row to open /sessions/[id].

Session Types

Session States

Side branches: Stopped (temporary pause) and Cancelled (won't happen; cancellation policy applies).

Creating a Session

Session Detail Page

When you click a session, the detail page lets you:

• Change state: Start, Stop, Complete, Cancel.
• Notes: add timestamped notes during the session.
• Files: upload stems, references, mixdowns. They auto-link to the related folder in /files.
• Equipment allocation: log which mics, preamps and monitors were used. The trace is kept in /assets.
• Guest list: anyone besides the artist who was in the room (manager, producer, observer).

Calendar

6 rooms + maintenance + event layers. Drag-drop editing.

Purpose

The calendar is the visual form of sessions. In week view the daily occupancy of all six rooms flows side by side; you see conflicts, free slots, and which engineer is available at a glance. /sessions is the "what was done" list; /calendar is the "when" map.

How to open

Sidebar → Calendar  /calendar.

Views

• Day: single day, hour by hour, all six rooms side by side.
• Week: 7-day slice. Most-used view.
• Month: high-level occupancy; useful for spotting busy periods.

Layers

Top-right has a layer toggle. Turn each on/off:

Extra layers: Maintenance (equipment maintenance windows), Events (live shows, masterclasses), Residence (large bookings — guest check-in/out).

Interactions

• Drag & drop: hold a session and drop it on another time. Conflict check runs automatically.
• Resize: grab the top/bottom edge of the block to extend or shorten.
• Click: a mini popover shows quick info and a "Open Detail" link.
• Click empty space: opens a new-session modal pre-filled with the time and room.
• Filter: top-right "Only my sessions" toggle reduces a busy calendar to your work.

Dante Network Awareness

All six rooms are interconnected via Dante — recording in Studio A while feeding from Studio D is possible. The calendar shows a Yellow warning when two rooms sharing the same network are both heavily loaded. It doesn't block, just flags attention — physical occupancy and network occupancy are different things.

Clients

CRM. Artists, producers, labels; preferences, contacts, sensitive data.

Purpose

Clients are our heart. This page is the registry of every artist, producer, label, or band we work with. Each client profile carries: contact info, preferences, history, dietary needs, allergies, favourite engineer, favourite room, favourite microphone. It's the knowledge base that lets the whole team remember a client when they call.

How to open

Sidebar → Clients  /clients.

Client Types

20 types are available; pick the right one. Most common:

What's on the page

• Top filter: search, type, status (Active/Inactive/Blocked), country, company.
• Table: Name · Email · Type · Status · Country · Company · Created.
• Top-right "Add Client", "Export CSV".
• Click a row → /clients/[id] detail page.

Client Detail Page

The detail page has four tabs:

• Profile: name, contact, type, status, country, company, social links, notes.
• Preferences: favourite room, engineer, mic; preferred working hours, time zone.
• Sensitive: dietary needs, allergies, health notes — encrypted with pgcrypto. Visible only to studio_director, residence_manager, kitchen_manager and concierge.
• History: all sessions, projects, quotes, invoices, stays. When a client returns, opening this tab gives you instant context.

Contacts (Band Member & Delegate)

Under a band client, two structures live:

• Band Member: Marcus (drums), Yuki (bass). Their own dietary, their own room.
• Delegate: someone "speaking on behalf of" — manager, assistant. Has permission to make requests, but every entry is auto-tagged "on behalf of".

For details see scenario #19 and the "Proxy Request" section in CLAUDE.md.

Lead → Client

/clients/leads is a separate page: people who came in via the enquiry form but haven't become clients yet. Review a lead and click "Convert to Client" → automatically moved to /clients with full history preserved.

Projects

Kanban (6 stages). Pre-Production → Recording → Mixing → Mastering → Delivery → Completed.

Purpose

A project wraps the entire arc of an album, an EP, a film score. You create the project, then bind sessions, tasks, files, and invoices to it. The stage tells you in real time where the artist sits — recording, mixing, or mastering.

How to open

Sidebar → Projects  /projects.

Two Views

• Grid: card layout — concise, good for fast scanning.
• Kanban: 6 columns side by side; drag-drop to change stage. The most studio-friendly view.

Kanban View

Project Types

• recording — Recording project.
• mixing — Mix only.
• mastering — Master only.
• atmos — Dolby Atmos spatial mix.
• production — Production / programming.
• online_mixing, online_mastering, remote_recording — From outside the facility.

Creating a Project

Project Detail Page

• Top info: client, lead engineer, status, budget vs actual spend.
• Sessions: all sessions linked to this project.
• Tasks: a mini-Kanban — project-specific tasks.
• Files: project folder; all session files auto-aggregate here.
• Timeline: activity stream — who did what when.
• Billing: linked line items, sent quotes, invoices.

Tasks

To-Do · In Progress · On Hold · Complete.

Purpose

Tasks track small deliverables tied to an artist or a project. "Prepare the vocal pad", "Upload the Cunda Atmos reference", "Backup B". Larger work = project, small concrete work = task.

How to open

Sidebar → Tasks  /tasks.

Kanban Columns

Task Fields

• Title (required)
• Description (markdown supported)
• Assignee (you can assign to yourself)
• Priority: Low · Normal · High · Urgent
• Due date
• Linked project (optional but recommended)

Tips

• Filter: "Assigned to me" is the default. Switch to "Whole team" for a wider view.
• Drag-drop: drop a task into another column. Moving to "Complete" stamps a finish time.
• Notification: the bell lights up when something is assigned to you; press ? for shortcuts.

Online Services

Mixing, Mastering, Atmos, Remote Recording — the global queue.

Purpose

For clients who never come to Cunda: an online portal. They upload stems, we mix, they receive WAV masters back. Opened this year; a global revenue stream. This page shows the incoming queue, assigned engineers, and status updates.

How to open

Sidebar → Online Services  /online-services.

Flow

States

• Submitted — Client applied, uploaded stems.
• Reviewing — Studio reviewing; will we accept?
• Accepted — Accepted; engineer assigned.
• In Progress — Engineer is working.
• Revision Requested — Client asked for changes.
• Delivered — WAV delivered, awaiting client approval.
• Completed — Done, paid.
• Cancelled — Client cancelled or we declined.

Engineer Assignment

Revisions

After delivery the client says "this vocal is too loud, that reverb is too wet". They press "Request Revision" in their panel and write the notes. The system pings the engineer; status moves to "Revision Requested". The engineer fixes it and re-delivers.

Each package has a revision allowance (typically 2). The third revision is paid; the system shows the surcharge schedule automatically.

Delivery Links

The WAV master lives in cloud storage; the system generates a 7-day, single-use, token-based download link. If it expires, the client says "my link doesn't work" and you regenerate with one click. Each download is logged to the audit trail.

Files

Stems, mixdowns, masters, references. Versioning and secure sharing.

Purpose

All audio lives on encrypted, redundant cloud storage. The system folders each file by session and project. Versions track automatically (v1, v2, ...). For sharing with clients we mint time-limited (default 7-day) links.

How to open

Sidebar → Files  /files. Each session and project detail also has its own files panel — context already established.

Folder Hierarchy

/clients/[client]/
  /projects/[project]/
    /sessions/[session]/
      /raw/      ← stems, multitrack
      /mixdowns/ ← v1, v2, v3...
      /masters/  ← final WAV
      /reference/← client references

What you can do

• Upload: drag-drop or "Upload" button. Multiple files and folders supported.
• Download: single file or multi-select (ZIP).
• Rename, move, delete: right-click menu.
• Share: generate a time-limited link. You set the duration (1 hour / 1 day / 7 days / 30 days).
• Versioning: uploading a same-name file creates v2; the previous version stays.

Secure Share Link

When you click "Share", a modal appears:

• Duration: 1 hour / 1 day / 7 days / 30 days / custom.
• Single use? (Link dies after one download.)
• Password-protect? (4-digit numeric code.)

Copy the link, send it. Audit log: who, when, from which IP downloaded.

Disk Usage

Storage is cheap but not unlimited. Profile > Settings > Storage shows a usage chart. Files from old projects auto-archive after 90 days, marked with a "Frozen" badge — they need a ~30 second wake-up before download.

Rooms

6 studio profiles. Dolby Atmos 9.2.4, Dante network.

Purpose

This page manages the studio rooms: 6 profiles, photos, fixed-config equipment, current occupancy, maintenance schedules. When a room is reconfigured, taken offline for service, or gains a new feature, it surfaces here. For equipment moves there's a separate page — Asset Management.

How to open

Sidebar → Rooms  /rooms.

Studio Rooms

Room Page — what you'll see

• Whether it's free now; if busy, who's inside.
• Fixed configuration: console, main monitors, acoustic features.
• Upcoming reservations.
• Maintenance schedule (semi-annual servicing dates).
• Photos — useful when a client asks to see it.

Dolby Atmos 9.2.4

Studio A and Mastering offer full Atmos: 9 bed-channel speakers, 2 subs, 4 height speakers. DAD AX32 Atmos renderer. When you create an atmos session, the system suggests Studio A or Mastering automatically.

Dante Network

All six rooms are linked over Dante (1 Gb audio over IP). Recording in Studio A while feeding from Studio D is supported. This matters for the calendar conflict rule — physical occupancy is one thing, network occupancy is another.

Asset Management

Microphones, preamps, monitors, cables, instruments — barcoded inventory, transfer, maintenance, service history.

Purpose

The page that manages the studio's physical inventory end-to-end. Every single microphone, every preamp, every DI box, every cable bundle, every instrument, every monitor lives here as an asset. Each has a unique barcode; the system knows where it is, what state it's in, when it was last serviced, and which sessions it has been used in.

A correctly maintained asset inventory answers "where is the vintage U47 from Studio A?" in five seconds. An incomplete or stale inventory means lost equipment and accountability problems.

How to open

Sidebar → Asset Management  /assets.

What's on the page

• Top KPI strip: Total assets · Active · In Maintenance · Out of Studio · Assigned (linked to a session/project).
• Filter panel: Type, current room, status, brand, acquisition date, last service date.
• Table: Barcode · Name · Type · Brand/Model · Current Room · Status · Last Seen · Notes.
• Top-right: "+ New Asset", "Scan Barcode", "Export CSV" buttons.
• Click a row: the asset's detail page opens — history, photos, manual, service records.

Asset Types

Status Tags

• Active — In place, ready to use, not bound to any session.
• Assigned — Allocated to a session or project; nobody else can grab it.
• In Maintenance — Out for service; estimated return shows in the field.
• Out of Studio — Festival, off-site recording, lent to another studio. Return date is mandatory.
• Retired — Removed from active service; not deleted from inventory because the history is preserved.

Adding a New Asset

Mobile Barcode Scan

In a phone browser, the /assets page exposes a "Scan Barcode" button. Point the camera at a barcode — the system jumps to that asset's detail page: "currently in Studio A, not assigned, last serviced 8 months ago". This saves time during night shifts and pre-session checks.

Transfer Flow

When equipment moves from one room to another:

Maintenance & Service

The system remembers two key dates per asset:

• Last service date: when it was last maintained.
• Next service date: auto-suggested per manufacturer interval (e.g. yearly for an SSL console).

As the next-service date approaches, a notification drops on the dashboard. "Send to Maintenance" sets the asset's status to In Maintenance; the system automatically excludes it from session assignments.

Adding a Service Record

• Service date
• Service provider (in-house / external — name, contact)
• Work performed (capsule swap, capacitor revision, calibration)
• Cost
• Logging staff (auto-filled)
• Invoice PDF attachment (for accounting)

Off-Site Checkout

For festivals, off-site recordings, or loaning gear out:

Sessions Linkage

In the session detail page, "Allocate Equipment" lets you bind one or more assets to a session. While bound, the asset's status is Assigned and no other session in that time window can call it. When the session completes, status automatically returns to Active.

The "Usage History" tab on each asset's detail page shows every session and artist that touched it — so years later, "when did we last use this vintage guitar?" has an answer.

Common Scenarios

Reporting

/assets > "Reports" tab (top-right). Includes:

• Total inventory value (current market value, when filled in).
• Most-used assets (by session count).
• Least-used assets (idle inventory — opportunity).
• Annual maintenance cost.
• Total off-site days — how much time each asset spent on external gigs.
• CSV or PDF export.

Concierge

Artist requests, AI routing, proxy requests. 3-pane interface.

Purpose

Concierge is the "control tower" where every artist and guest request is managed in one place. When an artist writes from the app, WhatsApp or in person, the AI routing classifies the message and sends it to the right department (studio, kitchen, hotel, housekeeping). As studio personnel, you see the requests routed to studio.

How to open

Sidebar → Concierge  /concierge.

Three-Pane Interface

• Left pane: conversation list. Filter defaults to studio; switch to "All departments" if needed.
• Centre pane: the active conversation — message bubbles, date dividers.
• Right pane: the person's profile — client card, history, preferences. Your team won't have to ask "who is this?".

Message Sources

• App — Artist wrote in the app (Zola interface).
• WhatsApp — Sent.dm webhook (Phase 2).
• Proxy — Staff captured a face-to-face request on behalf of the guest.
• System — Automatic notifications (booking confirmed, etc.).

AI Routing Tags

Each message carries small tags above it: department, priority, action_time. Example:

👤 Drummer (band member)
🏷️ studio · normal · @session_start
"Can we open up the snare top a bit?"

The AI only classifies — it does not generate replies. You write the reply. The system picks the channel automatically (app/WhatsApp).

Proxy Request

The artist isn't using the app and tells you in person. You create a request on their behalf:

Urgent Escalation

A Urgent tagged request goes to two places at once: the relevant department + the general manager. Studio matters that can't be resolved escalate to the studio director; non-studio matters do not.

Bookings

Studio + Stay packages, guest rosters, room assignments.

Purpose

A group is coming to Cunda — studio + stay + meals package. That's not a single session; it's a booking wrapping sessions, room assignments, band-member rosters, delegates and dietary preferences. It's the bridge between Studio + Residence + Restaurant.

How to open

Sidebar → Bookings  /bookings.

Package Types

• Studio Use & Stay (B&B): studio + room + breakfast.
• Studio Use & Full Board: studio + room + three meals.
• Lockout (Studios A & B): the studios are exclusive to one client for a period.
• Production Package: production-focused (Studio C/D + a guest room).
• Full Facility Lockout: the entire facility for one client. Where albums get made.
• Writing Camps & Masterclasses: education-focused, multi-room + curriculum.

Booking Structure

Booking: "Album Camp — September 2026"
├── Primary Client: [Artist]
│   ├── Room: Suite 1
│   └── Delegates:
│       ├── [manager]
│       └── [assistant]
├── Band Member: [drummer]   → Room 4, gluten-free
├── Band Member: [bassist]   → Room 5, vegetarian
└── Crew: [sound tech]       → Room 6

What's on the page

• Top table: all active/upcoming bookings. Date, client, status.
• Detail page: visual reflection of the structure above. Click each row to drill in.
• Studio sessions auto-link.
• Restaurant reservations (dinners) drop here too.

Your part

As studio personnel, your concern is the studio leg of the booking:

• Which days, which rooms, which engineer.
• Did the artist request special equipment (vintage U47, etc.) — read the booking notes.
• If it's a lockout, the calendar auto-blocks competing bookings.

Scenario: New Reservation

From client request → quote → acceptance → project → sessions → check-in.

A solo artist's manager asks about a 10-day album session in September 2026. The scenario starts with an email; you're translating it into the system.

Scenario: Online Mixing Delivery

Submission → assignment → mixing → revision → final delivery → invoice.

An indie artist from Berlin is submitting a 4-track EP for mixing. They will not visit; everything is online.

Scenario: In-Session Request

AI routing → triage → route to right department → resolve.

An artist is recording in Studio A. During a vocal break, they ask for something. Three possible channels:

A) From the app

B) From WhatsApp (Phase 2)

C) Face-to-face (proxy)

Scenario: Conflict Resolution

Two rooms want a Dante feed at the same time.

An artist is recording vocals in Studio A. At the same hour, a producer in Studio D — booked two days ago — has a composition session. Studio D is taking a Dante feed from A (following the A-side reference pad). But A's own cue is also receiving the feed — they're sharing Dante.

Glossary

Technical terms and abbreviations used in the system.

Troubleshooting

Common issues and their solutions.

Contact Matrix

Which subject goes to which role; who escalates to whom.

Company Emails

• studios@purcunda.com — Studio enquiries (external)
• reservations@purcunda.com — Stay enquiries
• ten@purcunda.com — Restaurant
• info@purcunda.com — General
• license@purcunda.com — Software / system support (Emre)
• Phone: +90 549 471 27 22

Closing

This handbook will grow over time. Anything missing, wrong, or confusing — write to Emre at license@purcunda.com and it will be fixed in the next revision.