Editor Onboarding · Shade Remote Editing · EyeClap
EyeClap Studios · Cloud Editing · Editor Onboarding

Remote Editing
via Shade

This guide covers everything needed to get an editor up and running on a cloud-based editing workflow using Shade. Two sides: what RD does to prepare, and what the Editor does to get editing.

RD — before handing off
Invite editor to Shade workspace
Confirm AI indexing is complete
Send project brief with sequence names
Confirm file naming convention
Share this guide
Editor — getting up and running
Accept Shade invite, create account
Install Shade desktop app
Mount drive via ShadeFS
Open project file from mounted drive
Enable proxy workflow, begin editing
Phase 1
RD — Prepare & Invite
RD
01
Confirm upload and AI indexing is complete
In Shade, check the bottom-left status bar. It should show all files indexed — not a pending count. The editor should not be invited until indexing is fully done. Shade's AI search and metadata only works on indexed files.
02
Invite the editor to the workspace
In Shade, go to Settings → Members → Invite Member. Enter the editor's email address. Set their role to Member. After they accept, go into the specific drive they need access to → People → confirm they're listed with the correct permission level. They should have access to the drive and its folders — not workspace admin rights.
03
Send the project brief alongside this guide
The brief should include:
Which sequences to work on — by exact name as they appear in the project
What the job is — specific task description (e.g. replace lower thirds, swap graphic elements in sections marked in timeline)
Where to find the project — full folder path: drive name → client folder → _PROJECT → project file name
Where exports go — _DELIVERY folder, using the KJ_ClientName_SequenceName_V1D1 naming convention
Deadline and preferred communication channel (Slack)
04
Verify the editor can see the correct drive
Ask the editor to confirm in Slack once they've logged in and can see the drive and project folder. Don't assume the invite worked — confirm it before they spend time on setup.
Phase 2
Editor — Account & App Setup
Editor
Do this once — before any project
This phase only needs to be completed once. After the Shade desktop app is installed and the drive is mounted, future projects just need a new project file — no reinstallation required.
01
Accept the Shade invite
Check your email for an invite from Shade. Click the link to accept. If you already have a Shade account, you'll be added to the EyeClap workspace automatically. If not, create a free account — use your professional email address.
02
Download and install the Shade desktop app
Go to shade.inc/download and download the correct version for your machine.
Mac (Apple Silicon / M-series): download the Apple Silicon build — do not use the Intel version on an M1/M2/M3/M4 Mac
Mac (Intel): download the Intel build
Windows: download the Windows build
Install the app and sign in with the same account you used to accept the invite
03
Mount the drive via ShadeFS
Once signed in to the desktop app, you'll see the EyeClap workspace and its drives in the left panel. Find the drive you've been given access to and click Mount. The drive will appear on your computer as a network volume — on Mac it shows in Finder under Locations, on Windows it shows as a mapped network drive. This is your cloud hard drive. Everything you need is already there.
04
Confirm your internet connection is adequate
ShadeFS streams files in real time. A minimum of 25 Mbps upload and download is recommended for smooth proxy editing. Run a speed test at fast.com before your first session. If your connection is slower, contact RD — a different workflow may be needed.
Phase 3
Editor — Open the Project
Editor
Critical — do not download files
Do not copy project files or media to your local hard drive. Open everything directly from the mounted Shade drive. This keeps the project live and collaborative — RD can see your saves in real time.
01
Navigate to the project file on the mounted drive
Open Finder (Mac) or File Explorer (Windows). Navigate to the mounted Shade drive → client folder → _PROJECT. You'll see the .prproj file there. Double-click to open it directly in Premiere Pro. Do not copy it to your desktop first.
02
Relink media if Premiere shows offline clips
Premiere may not automatically find the media on the first open since the paths are new. If you see offline clips (red media in the timeline):
Right-click an offline clip in the Project panel → Link Media
Navigate to the _ASSETS folder on the mounted Shade drive → find the corresponding media file → click OK
Premiere will auto-relink the remaining clips — check Relink Others Automatically in the dialog
If proxies are also offline, repeat for the _ASSETS / Proxies folder
03
Enable the proxy toggle
In the Program Monitor, click the wrench icon (Settings) → enable Toggle Proxies to add the proxy button to your toolbar. Click the proxy button so it's active — your timeline should switch to the lighter proxy media. You should be editing on proxies for this job, not full-res media. If the toggle button isn't available, go to Preferences → Media → Enable Proxies.
04
Confirm playback is smooth before starting work
Scrub through the timeline on proxy media. Playback should be smooth with no buffering. If you experience stuttering, check: is the proxy toggle on? Is the Shade drive still mounted? Is your internet connection stable? Resolve any issues before beginning the actual edit.
Phase 4
Editor — Edit & Deliver
Editor
01
Complete the job as briefed
Work in the sequences specified in the brief. Save frequently — Cmd/Ctrl + S — directly to the mounted drive. Your saves are visible to RD in real time via Shade. No need to send files back and forth.
02
Export finished sequences to _DELIVERY
When a sequence is complete, export directly to the _DELIVERY folder on the mounted Shade drive. Do not export to your desktop or local drive.
File → Export → Media (or Cmd/Ctrl + M)
Set the output path to: Shade drive → client folder → _DELIVERY
File naming convention: EditorInitials_ClientName_SequenceName_V1D1 — e.g. KJ_Bosley_OfficeSpot_V1D1
Export format and codec will be specified in the project brief — use those settings exactly
03
Notify RD via Slack when complete
Message RD on Slack when all deliverables are exported to _DELIVERY. Include: sequence names completed, any issues encountered, and whether anything needs RD's attention before client review. Do not send files via email or WeTransfer — everything lives in Shade.
Non-negotiable workflow rules
The Four Rules
Never download project files or media to your local drive. Open everything directly from the mounted Shade drive.
Always edit on proxies. Full-res media streaming is reserved for final export — keep the proxy toggle on during all editing sessions.
Save exports to _DELIVERY only. Never export to desktop, Downloads, or any local folder. All finished files live in Shade.
Use the file naming convention on every export. EditorInitials_Client_Sequence_V#D# — no exceptions. This is how RD finds your work instantly.
Questions or issues?
Message RD directly on Slack for anything technical or project-related. For Shade-specific issues (mounting problems, app errors, access issues) visit academy.shade.inc or reach Shade support via in-app chat. Do not wait until delivery day to flag a problem — surface it early.