Projects
A project is where a job lives: its team, its deadline, its tasks, its shots and the versions of work on each one, and the files that go out the door. This chapter covers starting a project, finding your way around its page, working with versions on a shot, and putting a finished job away. How to set up and fill a shot list has its own chapter: Shot breakdowns.
Two letters is enough, and it reads every chapter.
How do I start a project?
Press + Add Project on the dashboard, or New → Project in the top bar. The popup has three tabs:
- Project: the name, the type of work and the client, the status, the deadline, who leads it (Choose team lead) and Who else is on it. If the client company does not exist yet, type it in and it is made on the spot.
- Deliverables: what the job hands over, in the client's own words. You can tick these off as they go out.
- Planning: the moments in between (a blockout review, a model review) and how many rounds of comments you agreed for each, plus Rounds agreed, as a rule on this job. Every line becomes a review track the job is waiting on; nothing goes to the client until you publish a version on one.
Only the name is needed to start. Everything else can be filled in later.
How is a project page laid out?
One page, in chapters that follow the order the work happens in: General Tasks, Pre‑Production, Shot Breakdowns, Production, Post‑Production, Deliverables, Canvas, Links, Transfers and Project Details.
The row of boxes at the top shows which chapters are on the page: a filled box is shown, an empty one is hidden. Press a box to hide or show that chapter. Hiding never deletes anything; it keeps a page you only use for tasks from being ten chapters long. Your choice is remembered for you.
Versions: one chain per kind of file
Open a shot and drop work onto it (an image, a video, a 3D file, a document). Each kind of file gets its own version chain, so image v2 never replaces video v1. The Current badge marks the newest version that has not been thrown away; delete v4 and v3 is current again.
A version number is never reused. Bin v3 and the next upload becomes v4, so a note that says "fixed in v3" keeps meaning the same file. When the oldest surviving version is v005, the list says how many were thrown away, so the gap is explained.
Removing a version is its own action, separate from removing the shot. If the version is in a review round, the popup asks whether to take it out of review as well. That box starts unticked, so throwing away a working file never reaches into a client's conversation by accident.
Sending work onward from a shot
Tick the versions you want and two buttons appear side by side: Send to review (let the client judge it) and Transfer files (hand it over).
- Send to review always lands as a draft. Publishing it is a separate step on the review page; see Review.
- Transfer files sends the files without uploading them again, and costs no extra storage; see Transfers.
The first time a shot is sent to review, Kadrenta asks once: Internal, for us or Client, for them. Later versions of that shot follow the same answer, so an internal shot never picks up a client round by accident.
Standard tasks
The ☰ button on a project chapter opens your studio's list of things every project needs (Moodboard, Script, Storyboard, and so on). Tick what this job needs and each line becomes a task in that chapter. Lines already on the project show as already here. See Tasks for building the list.
The ☰ on an opened shot works the same way, with the shot tasks of its breakdown; see Shot breakdowns.
Folder templates
A studio can set up its own folder trees once (Renders / Source files / Reference / Delivery) under Admin Console → Studio settings → Folders, and apply one to any project. Applying a template creates those folders in the project's files.
Links: addresses that live somewhere else
The Links chapter holds addresses that belong to the job but live outside Kadrenta: a Pinterest board, a Miro board, a network path, a Drive folder. Paste one and press Enter; a name is optional. A badge shows what kind of address it is. An address only becomes a clickable link when it can open safely; otherwise it shows as text.
How do I leave a project?
Press the door icon on the project's tile, or Leave project on your own row in the project's team. Your open work goes back to whoever runs the job. The project's owner and its last lead cannot leave; hand the job to someone else first.
Archiving a project
Archive takes a finished project off the active lists. Nothing about its shots, tasks or files is touched, and you can restore it from the project's settings at any time. If the project holds files, the popup offers to put those in the trash too.
Archiving also closes the project's doors to the outside: its share links and transfers stop opening, and its reviews count as finished. The popup counts what is still open before you press, for example "One share link on this project is still open to the outside, and archiving closes it. Restoring the project opens it again."
Everything a studio has put away (projects, lost deals and canvases) is listed under Admin Console → Archive, sorted by size or by when it was filed. A shot, task or version is never a row of its own there; it travels with its project.
Only from the archive can something be deleted permanently. That popup says exactly what goes and how much room it frees, for example "3 shots, 40 tasks and 12 files go with this job. That frees 2.1 GB, and none of it comes back.", and you type the project's name to confirm.