EyeClap Studios · Internal Reference · April 2026
Shade Infrastructure
Master Guide
Architecture, workspace structure, drive setup, team access, ShadeFS mounting, Mac Finder fix, drive migration, and editor workflow rules. Single source of truth for the EyeClap Shade system.
Plan
Growth
$20/seat/mo · annual
Architecture
Per-client drives
One drive per client
Paid seats
RD + Editors
ShadeFS mounting only
Storage
500GB/seat
Backblaze BYOS when needed
Core Architecture
One Drive Per Client
Every client gets their own dedicated Shade drive. This keeps permissions clean, Collections scoped correctly for client delivery, and editors working in clearly defined spaces. Marlo (NEEBA) is added to specific client drives on an as-needed basis as the partnership activates — no standing structural separation required.
Architecture Decision
There is no EyeClap vs. EyeClap + NEEBA drive split. All drives are owned by EyeClap. Marlo's access is managed at the individual drive level when joint work requires it. This keeps the system lean and honest about how the partnership actually operates.
EyeClap Workspace
Owner: RD White · Growth Plan · admin
Amplify
RD + editors · Marlo when active
Joint
Bosley
RD + editors
EyeClap Direct
Heartwood
RD + editors · Marlo when active
Joint
Keranique
RD + editors
EyeClap Direct
Root Evidence
RD + editors · Marlo when active
Joint
File Management
Folder Convention
Every client drive uses the same three-subfolder structure. The underscore prefix sorts all three to the top alphabetically regardless of what else is added.
Folder 1
ASSETS
All source material. Subfolders: Footage/Proxies (camera originals and proxy files), GRFX (graphics, logos, client-provided assets), Stock Footage, Audio (dialogue, SFX, voice), Music (licensed tracks, Artlist).
Folder 2
PROJECT
Premiere Pro project files, After Effects comps, DaVinci projects. This is what editors open and stream directly via ShadeFS. Project files never leave this folder.
Folder 3
DELIVERY
Finished exports ready for client. All editor exports go here — never to local drives. Use V1, V2 subfolders to preserve revision history. Client review links point to this folder.
Project Naming Convention
Each client drive contains multiple projects. Project folders use the first 3–4 letters of the client name followed by the project title — e.g.
BOS_HollywoodHills-Podcast, AMP_Q2-SocialCampaign, HTWD_EventHighlights, KER_ProductLaunch, ROOT_CaseStudy. Each project folder contains its own ASSETS, PROJECT, and DELIVERY subfolders.Client Drive (e.g. Bosley)
BOS_HollywoodHills-Podcast
ASSETS
Footage/Proxies
GRFX
Stock Footage
Audio
Music
PROJECT
BOS_HollywoodHills-Podcast.prproj
DELIVERY
V1
V2
BOS_BestDecisionEver-LocalOffice
ASSETS
PROJECT
DELIVERY
File Naming Convention
Incoming from RD:
RD_ClientCode_ProjectTitle_V1D1 · From Cooper Ravetch: CR_ · From Kevin Jung: KJ_ · From Edit Lobby: EL_ · From GK Ram: GK_ · From Bo Collet: BC_ · Version notation: V#D# = Version number, Draft number. Client code matches project folder prefix — e.g. BOS, AMP, HTWD, KER, ROOT.Team Access
Seats vs. Guests
Paid seats are only for team members who need ShadeFS drive mounting — the remote editing capability. Everyone else operates as a free guest via shared upload or review links.
| Team Member | Access Type | Why | Cost |
|---|---|---|---|
| RD White | Member · Admin | Workspace owner · full ShadeFS access all drives | $20/mo |
| Cooper Ravetch | Member · Editor | Full editor · ShadeFS mounting · file prefix CR_ |
$20/mo |
| Kevin Jung | Member · Asst. Editor | Assistant editor · ShadeFS mounting · file prefix KJ_ |
$20/mo |
| Marlo (NEEBA) | Member · As Needed | Added to specific joint client drives when partnership activates | $20/mo settled between partners |
| Edit Lobby / Nihal | Guest · Free | Delivers via shared upload links — no ShadeFS needed | $0 |
| GK Ram | Guest · Free | Project-based delivery via shared links | $0 |
| Clients | Guest · Free | Review via published Collection links — up to 150 guests included | $0 |
| Current total (RD + Cooper + Kevin) | $60/mo | ||
ShadeFS · macOS
Mounting Drives on Mac
ShadeFS mounts drives to /Volumes by default — not the Finder sidebar. This is a known Mac behavior with virtual network volumes, not a Shade bug. Follow the one-time fix below and drives will appear automatically in the sidebar on every future mount.
Do this once per drive, per machine
After completing the steps below, the Shade drive will appear in your Finder sidebar every time it's mounted — no repeated setup required. Each editor needs to complete this once per client drive they're assigned to.
01
Mount the drive in the Shade desktop app
In the Shade desktop app left panel, find the client drive. Click the ... menu next to the drive name → select Mount Drive. The drive is now mounted but won't appear in Finder sidebar yet.
02
Navigate to /Volumes in Finder
Open Finder. Press Cmd + Shift + G. In the dialog that appears, type
/Volumes and press Enter. You'll see all currently mounted drives listed here including the Shade drive.03
Drag the drive into your Finder sidebar
Find the Shade client drive in the /Volumes window. Drag it into the Locations section of your Finder sidebar — the left panel. It will pin there permanently. From this point forward, every time this drive is mounted it will appear in the sidebar automatically.
04
Repeat for each client drive you're assigned to
Each client drive needs to be pinned once. If you're working across multiple client drives, mount each one and drag it to the sidebar before your first editing session. After that, all your drives will be right there every time.
Cache tip
ShadeFS uses a 26GB default cache shared across all mounted drives. If you're mounting multiple client drives simultaneously, bump this up first: Shade desktop app → Settings → Preferences → Cache Size. An external SSD as your cache location significantly improves streaming performance.
Client Delivery
Collections for Client Review
Never share a raw folder link with clients — they'll see your internal folder names. Use Collections to create a clean, client-facing view with a name you control, pulling from your DELIVERY folder.
01
Create a Collection inside the client drive
In the client drive left sidebar, click Collections → + New Collection. Name it what you want the client to see — e.g.
Bosley — Q2 Campaign Review or simply the project title. The client sees this name, not your folder structure.02
Add deliverables to the Collection
Browse to
DELIVERY, right-click the finished files → Add to Collection → select the Collection you just created. Files stay in DELIVERY — Collections are a view layer, not a separate copy.03
Share the Collection link
Open the Collection → click Share → copy the published link. Send to the client. They see a clean, branded review experience with only the files you've added — no visibility into your drive structure.
Editor Standards
Workflow Rules
These rules apply to every editor on every project. No exceptions.
Non-negotiable
The Four Rules
Never download to local drive. Open all project files and media directly from the mounted Shade drive. Work lives in Shade, not on your machine.
Always edit on proxies. Keep the proxy toggle active during all editing sessions. Full-res streaming is for final export only.
Export to DELIVERY only. Never export to desktop, Downloads, or any local folder. All finished files go directly to the client's
DELIVERY folder on the Shade drive.Use the naming convention. Every export:
Initials_Client_Sequence_V#D# — no exceptions. This is how RD finds work instantly across all clients.Reference
Key Links
Shade app
Desktop app download
shade.inc/download
Mac (Apple Silicon · Intel) · Windows
Mac (Apple Silicon · Intel) · Windows
ShadeFS guide
Backblaze BYOS integration
Mac Finder fix
Cmd + Shift + G →
/Volumes → drag drive to Finder sidebar. One-time per drive per machine.Shade support
In-app chat · support@shade.inc
Backblaze B2
backblaze.com · $6/TB/mo · trigger when approaching storage limit
Large migration guide
Rclone migration guide · use for transfers over 5TB