Who should be able to see financial information in a post-production studio?

In most post houses the schedule is public knowledge and the rate card is not. Yet the moment a facility moves its operations into software, those two things tend to land in the same place. This article is about keeping them apart: who genuinely needs to see money, who only needs to see the work, and how to set that up without slowing anyone down.

Two kinds of information in every booking

A single grading session carries two layers of information. The operational layer is what the floor needs: which room, which colourist, which project, what time, how many hours were planned and how many were actually used. The financial layer sits on top of it: the room's hourly rate, the artist's rate, the project's quoted hours and budget, the challan that will be raised from the session, the invoice it ends up on, and whether the client has paid.

On a whiteboard or a shared calendar the financial layer simply isn't there, so nobody worries about who can see it. In software it is one click away unless the system deliberately separates it. That is the whole problem, and the whole fix.

Who needs what

Every facility is different, so treat this as a starting point rather than a rulebook.

Role in the facilityNeeds to seeUsually does not need
Colourist, Flame artist, online editorTheir bookings, the project, the client name, session times, deliverablesRoom and artist rates, quotes, invoices, payment status
Studio coordinator / bookerThe whole schedule, room and artist availability, leave, project statusRates and billing, unless they also raise challans
Line producer / producerSchedule plus quoted hours vs. actual hours, quotations, whether sessions have been billedOften fine to see invoices; recording payments is usually someone else's job
Studio manager / head of productionMost of the above, plus utilisation and billing status across projectsDepends on the facility; many managers do not need to record payments
Accountant / financeChallans, invoices, payments, overdue balances, reportsDay-to-day schedule changes (read-only is enough)
OwnerEverything—

Two things stand out. First, the people who spend the most time in the schedule are usually the people who least need the money. Second, "sees financial information" is not one switch: seeing an invoice, creating one and recording a payment against it are three different levels of trust, and a sensible setup treats them differently.

Least privilege, in plain terms

Security people call this least privilege: give each person the access their job needs and no more. In a post house it is less about distrust than about hygiene.

None of this requires a particular tool. A spreadsheet with a separate, restricted tab can do a crude version of it. The point is to decide deliberately rather than let the software decide for you.

How Organize handles financial visibility

Organize builds the separation into roles. Every user in a studio has one role, and only some roles carry financial access.

Financial access means the person can see invoices, challans, quotations, recorded payments, the billing dashboard, and the hourly rates on rooms, artists and projects. In Organize the roles with financial access are Owner, Administrator, Accountant, Line Producer, Finance and Manager.

Operational access means the person can work with the schedule and projects without the money attached. The roles without financial access are Studio Coordinator, Staff, User and Viewer. These users book rooms and artists, see projects and clients, and record session hours; the rate fields and billing pages are simply absent for them. Viewer is read-only across scheduling and projects and is still excluded from financial screens.

Within the financial roles, what each one can do differs. Recording a payment against an invoice is limited to Owner, Administrator, Accountant and Finance. Creating invoices and challans is available to those roles plus Manager. A Line Producer can create quotations and read challans and invoices but does not record payments. Only an owner can grant the Owner role, and only owners and administrators can create users or change roles.

This separation applies on the server, not just on the screen. Financial API routes and PDF documents check the user's role before returning anything, and the rate fields are stripped from the responses operational roles receive. A coordinator cannot reach an invoice by typing its address into the browser.

Two honest caveats. The roles are fixed sets rather than a custom permission editor, so if your facility's structure does not map onto them you may need to pick the closest fit. And financial separation is about what people in your studio can see; it is a different control from keeping your studio's data separate from other customers, which Organize also does.

Setting it up without friction

  1. Start from the list above, not from the org chart. Decide who needs to see rates, who needs to see invoices, and who needs to record payments. Usually that is three short lists.
  2. Give artists and coordinators operational roles by default. It is easier to add financial access later than to take it away.
  3. Keep payment recording narrow. One or two people. It is the step where errors are most expensive to unwind.
  4. Review when people change jobs. A coordinator who becomes a line producer should get the new role; the old account should not simply accumulate access.
  5. Tell the team. People accept not seeing rates far more readily when they know it is a rule for everyone, not a judgement about them.

You do not have to use Organize's role structure to apply any of this. If you do use Organize, it is already in place on day one of a trial, so the setup is a matter of choosing roles when you invite people.

See the role separation in a real studio setup

Create your studio, invite a coordinator and an accountant, and compare what each of them sees. Free to start.

Start Free