What Access Permissions Work Costs and What Moves the Price
A plain look at what a permissions plan for shared drives and cloud storage costs in time and money, and which choices make the figure rise or fall.
Daniel Whitfield · · 6 minutes to read
Start with what you are actually pricing
When a producer asks me what access permissions will cost, I first ask what they think they are buying. Permissions are not a piece of software or a file. They are a set of decisions: who can read a folder, who can change it, and who has the final word on an export. The cost is mostly the time it takes to make those decisions properly and write them down.
In the programme, this module asks you to build a permissions matrix for a sample drive. That exercise is the same shape as the real work. You list the people and roles, you list the areas of the drive, and you fill in each cell with read, edit or approve. A small team with one drive can finish a first version in an afternoon. A larger group across several drives takes longer, and the price follows the hours.
It helps to separate three kinds of cost: the learning, the planning, and any hands-on changes to your storage. They behave differently, and mixing them is where budgets go wrong.
- Learning: working through the module with your own sample drive
- Planning: drafting the matrix and agreeing it with the team
- Changes: setting permissions on live storage, scoped separately
The number of people and roles sets the baseline
The first driver is headcount, but not in the way most people expect. Twenty freelancers who all do the same job need fewer rules than six staff who each carry a different responsibility. What counts is the number of distinct roles, because every role needs its own row in the matrix and its own conversation about what it should touch.
A typical post team has editors, an assistant, a colorist, a sound person, a producer and a client reviewer. Each one needs a different level of access to raw footage, project files and exports. Writing those rules is not hard, yet it takes patience, since people often disagree about who should be able to delete things.
If your roles shift from one project to the next, plan for more time. A matrix that has to flex per job needs a clear template and a short note on how to adjust it, and drafting that template is part of what you pay for.
- Count roles, not just people
- Note which roles change between projects
- Name one person who owns the final matrix
Storage setup: shared drives, cloud, or both
The second driver is where your files live. A single network drive has one permissions model. Cloud storage has another, and many teams run both, with raw camera files on local disks and working exports in the cloud. Each system speaks its own language of folders, groups and sharing links, and the matrix has to be translated into each one.
Mixed setups cost more to plan because the rules must stay consistent across them. A producer who can approve a cut in the cloud should not be locked out of the same project on the shared drive. Catching those gaps on paper is far cheaper than discovering them mid-delivery.
This is also where the line between teaching and hands-on work matters. In the module you learn to design the matrix and map it to your storage. Applying it to your live systems is a separate piece of work, agreed in advance, with its own scope and its own price.
Existing mess adds time before any rules can be written
The third driver is the state of what you already have. A drive where permissions grew by habit, with former colleagues still listed and shared links nobody remembers creating, needs a review before a clean matrix is possible. You cannot decide who should have access until you know who has it now.
That review is closely related to the asset audit module, and the two often overlap. Expect to spend extra hours listing current access, flagging accounts that should no longer exist, and spotting folders that are open to everyone by accident. None of it is dramatic, but it is tedious, and tedious work is billed by the hour.
Teams that arrive with a rough list of current users and shared folders save real time. If you can bring that, the planning phase shortens, and the budget goes toward decisions instead of detective work.
- Bring a list of current users and groups
- Note any shared links still in circulation
- Flag folders that anyone can edit
What is not worth paying for
Some spending adds little. An elaborate matrix with a dozen permission levels looks thorough and then goes unused, because nobody remembers what level seven allows. Three levels, read, edit and approve, cover almost every production team, and they are easy to explain to a new hire on the first day.
Another low-value cost is rebuilding the whole structure for every project. A good template, set up once, makes the next job a matter of copying and adjusting. If a plan needs a full rewrite each time, the design is wrong, not the project.
Finally, be wary of paying to lock everything down so tightly that people work around the rules. Editors who cannot reach a file will copy it somewhere else, and then you have a duplicate with no controls at all. Sensible access that people respect beats strict access that people avoid.
Setting a budget you can defend
To set a figure, start from three questions. How many distinct roles do you have, how many storage systems do they cross, and how much cleanup does the current drive need? Answer those honestly and you can estimate the planning hours without much guesswork. Anything beyond that, such as changes on live storage, gets its own quote.
I would also suggest keeping a small allowance for review. Permissions drift. People join, leave and change jobs, and a matrix that was right in spring can be wrong by the end of the year. A short check every few months costs little and keeps the original investment from quietly decaying.
If you are weighing this against other modules, treat permissions as one of the cheaper areas to get right early. A clear matrix prevents the expensive mistakes: an overwritten final export, a client seeing a draft, a deleted master. Those are the real costs this work is meant to avoid.
- Estimate roles, storage systems and cleanup first
- Quote live-storage changes separately
- Schedule a short review every few months
The price of access permissions work comes down to roles, storage and starting condition. Fewer roles, one storage system and a tidy drive keep it modest; mixed setups and years of drift push it up. Decide what you want to learn, what you want planned and what you want changed on live storage, and keep those three apart. That separation makes the figure easier to agree and easier to defend later.
Send us a message
- Call us
- (505) 214-0873
- By email
- [email protected]