The Kadrenta handbook What Kadrenta does, how it works, and why it is built that way. The chapters are in the order they are most useful to read. Search above, or pick one below.
This chapter takes you from kadrenta.com to a studio of your own, and shows the places you come back to every day: the top bar, the dashboard, your profile, and the way to tell us when something is wrong.
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.
A shot breakdown is the list of shots in one cut of a job: the film, the teaser, the 10-second version. Each breakdown has its own shots, its own full edit, and its own way of tracking them: statuses that fit your pipeline, columns for what your shots need (frames, a plate, a sequence, a supervisor), and a shot code in the form your studio already uses. This chapter shows how to set one up, fill it, and keep it current, by hand or from a spreadsheet.
Review is where work gets judged. A version lands as a draft, your studio looks at it, and when the moment is right you publish it, so the people holding a link can watch, comment, draw on the frame and approve. Sending, publishing and telling somebody are three separate steps, and nothing happens by itself. When the work is agreed, you finish the review and it moves out of the way.
A share link is the one door between your studio and everyone outside it, whether it opens a review, a canvas or a transfer. Nobody needs an account to open one. Looking is free, and anything that changes something is an explicit button, on the far side of a link as much as inside your studio.
Every picture, video, 3D model and document in Kadrenta goes through one file service, wherever it lands: a shot version, a card on a canvas, a project's own files, the studio's shared folders, or a transfer to a client. That is why storage, the trash and video playback behave the same everywhere. This chapter covers what you can upload where, where your studio's working files live, how much room you have, and how to get something back.
Transfers is how you hand finished files to a client without a separate service. Drop files in, say who they are for, and a link goes out that opens without an account. A transfer is a hand-over, not a shared drive: it always has an end date, and its files clear themselves out afterwards.
A canvas is an endless board where you lay out cards (images, video, PDFs, notes, and cards that show real work from a project) and connect them with wires. It is where a studio thinks out loud together: moodboards, pitches, a breakdown with every shot laid out, a walk-through for a client. A canvas is a window onto your project, never a second copy of it, so arranging and wiring things is always safe.
What am I supposed to be doing, and what is late? That is what tasks answer. A task is the smallest unit of work in Kadrenta. It can hang off a project, off a shot inside a project, or off nothing at all, for the small errand that does not deserve a project of its own.
Who do we sell to, and what are we pitching them right now? A client is a company, not a person. A deal is one opportunity with that company, on its way from first enquiry to won or lost. Kadrenta keeps this deliberately small: enough to know who you are talking to and what a job might be worth, and never invoicing or bookkeeping. Everything here lives under Sales in the top bar, in three tabs: Funnel, Approach and Companies.
Who is in my studio, what does that cost, and what happens if I change my mind? A studio holds two kinds of people: those who work there as their home studio, who take a seat, and those who help on one job while keeping a studio of their own, who cost you nothing. This chapter covers seats, roles, invitations, prices, the free plan, and changing what you pay. All of it lives in the Admin Console, mainly on the Team and Billing tabs.
Kadrenta tells you what needs you in a few places: your notifications in the app, your mailbox, and Discord if you connect it. This chapter explains what goes where by default, why messages wait a few minutes before they are sent, and how what your crew hears differs from what a client ever receives.
Kadrenta can be connected to your own AI assistant, such as Claude or Codex, so you can ask about your studio the way you would ask a colleague instead of clicking through screens. This chapter explains how to connect, what the connection can read and change, and the rules that keep it from ever doing something you could not do yourself.
This handbook describes Kadrenta as it works today. If something here does not match what you see, that is worth telling us.
kadrenta.com Help & FAQ support@kadrenta.com Privacy Terms