Help Center

Why timestamps match your studio clock.

People, production, finance, and module configuration.

ER codes, event log, compliance pack.

Toggle modules per studio so unused areas disappear from the sidebar.

Monthly feature drip, entitlements, and what DCC clients receive.

External review without counting client seats.

What clients see when they approve or request changes.

Signed links, watermarks, and audit on client downloads.

Supervisor review queue, sessions, playlists, and what happens after submit.

Review links use watermarked proxies - studio tier vs forensic options.

How proxied media keeps review fast and off full-res storage.

Check-in, task timers, Smart Save, submit to dailies, timesheet and leave.

Send a version from Houdini (or other DCC) to the review queue.

Context, Smart Save, publish, and multi-DCC parity.

What gets published, version history, and dependency health.

Show, sequence, shot, and scene context before you save or publish.

Maya, Nuke, Blender, and Unreal follow the same context + publish pattern as Houdini.

Element IDs track versions, costs, and upstream/downstream lineage.

Where-used, incoming dependencies, and publish ripple alerts via PEID lineage.

Lineage graph, impact panel, software and file-type labels.

Farm compute time plus on-disk storage GB rolled up per PEID.

Invoices, expenses, AP/AR, GST, and project P&L.

Bill clients and track aging receivables.

Record vendor bills and payables workflow.

GST/TDS registers and statutory reporting.

How task time, farm cost, and expenses roll into project P&L.

Your first hour in the studio hub - navigation, profile, and where to find work.

Artist, producer, HR, finance, and client portal - who sees what.

Submit for review - From your DCC or the web, submit a version to dailies. It enters the review queue; your supervisor reviews and

Render farm - Open <b>Render Farm</b>, submit a job with the DCC, scene path and frame range. The farm splits it into chunks across

Formulas and data sources for dashboard numbers: attendance, P&L, render farm, deps, PEID lineage.

My Approvals - Leave, expenses, timesheets and profile changes awaiting you appear in My Approvals. Open an item to see evidence (r

Day one - <ol><li>Log in and set your password.</li><li>Complete My Profile (bank, emergency contact).</li><li>Read the Studio Handboo

The home base - Open a project from <b>Projects</b>. The project page is your hub - its action bar links to everything for that sho

Check-in, hours, and weekly timesheet approval.

Request time off and ask HR questions.

How payslips are generated and where employees find them.

First-login profile, documents, and HR helpdesk for new hires.

Attendance bot, dailies /submit, and reminders.

Notion ingest and task history sync policy.

Notion/planning ingest and Discord relay for producer sheets.

Report pipeline bugs, app issues, and client feedback with SLA teams.

Assign teams, track SLA, and read issue analytics.

Connect bugs and feedback to production context.

Attendance - Check in and out each day. Pay is based on effective days worked. Timesheets - Log hours against your task

Respect - We expect professional, respectful conduct toward colleagues and clients. Harassment of any kind is not tolerated. <h3

Content security - All review media is watermarked and access-controlled. Do not screen-record, re-host, or share client links. Use

Receipts required - Every claim needs a receipt. Add vendor, GSTIN and invoice number for tax claims. Submit from <b>Expenses</b>;

Leave types - Sick, Casual (capped 12 days/year), Comp-off, Maternity, and LOP (unpaid). Apply from <b>Leave</b> in the sidebar; yo

Welcome - This is the studio handbook. It covers how we work, the tools in your portal, and where to find help. Update your profile

Project → shot → task hierarchy, bidding, schedule, delivery, wrap.

Set estimates and compare to logged hours and costs.

Watermarked packages, client sign-off, and closing a project.

Turn bids into dated tasks and see studio workload.

Overdue tasks, bid burn, and delivery risk in one dashboard.

Four green/red checks on the shot page before delivery.

Dashboard, queue, workers, costs, and submitting from Houdini.

Register a render machine so it can claim chunks.

Send a render from Houdini to the farm queue.

Filter the queue, open job detail, and read costs per shot.

Windows, Linux, and macOS workers must resolve the same scene paths.

Who sees render cost, queue column, and per-shot rollups.

Access denied, missing pages, and error reference codes.

Stuck jobs, failed chunks, worker offline.

Quick answers to common questions.

R2 storage errors and upload failures.

When Discord DMs or channel posts fail.