Team Roles and Permissions in a Photography Studio

Give each person access to what they need to do their job and nothing else. For a photography studio, that usually means owners and admins see everything, team members see the jobs they work on, and freelancers and editors see only their own tasks, not prices, income or client payment details. Here is how to decide who needs what.

Who needs to see what

Start from the task, not the title. Ask what each person does in a typical week.

Review the table whenever you add a role. Least access is safer for everyone.

Prices and income

Money information is the most sensitive. Reasons to hide it:

• Pay differs between people, and comparisons cause friction.
• Client prices are commercial information you may not want freelancers to take elsewhere.
• Fewer people with access means fewer places for a leak.
• Accounts can be compromised, and then only so much can be seen.

A second shooter does not need the package price to do the job well. An editor needs the style, the deadline and the deliverable count. Keep invoices, payment status and profit with owners and admins only.

If you pay people per job, share their own fee with them, and nothing else. Put it in the agreement.

Client contact details

Clients trust you with names, phone numbers, addresses and family details. Share them on a need-to-know basis.

• Show the contact for the day, such as a planner or family member, not the full record.
• Do not send everyone the whole client list.
• Keep private notes private, like health information or sensitive family matters.
• Use the studio's own channels rather than personal messages for client contact where possible.
• Remind freelancers not to contact clients for their own marketing.

Rules on personal data differ by country, so check what applies to you. Put a confidentiality clause in freelancer agreements. A clear call sheet gives the team what they need on the day without exposing the client's file.

Roles to start with

Keep the structure simple at first. A starter set:

1. Owner: full access, billing and settings.
2. Admin: runs the day to day, sees money, manages the team.
3. Member: works on assigned jobs, sees their own tasks and schedule.
4. Freelancer or editor: sees only their own work, no prices or income.

Add roles only when a real need appears. Having ten roles for four people is complicated to maintain. For hiring outside help, our post on outsourcing tasks lists what to hand over first.

Also consider who can approve edits and change a delivery. Our post on revision policy is a useful companion.

It also helps to review access every few months even when nobody is leaving. People change roles, projects end and old logins linger. A ten-minute check of who can see what keeps the setup honest and catches anything that grew beyond its purpose.

Offboarding

When someone leaves, a short routine protects you:

• Remove their access the same day.
• Change any shared passwords and codes.
• Collect or delete files they hold, as agreed.
• Reassign their open jobs and tell affected clients.
• Settle final payments and keep the paperwork.
• Remind them of confidentiality in writing.
• Review the permissions of everyone else while you are at it.

Example: a freelance editor finishes a contract on Friday. By Friday afternoon, their login is off, their open files are moved to another editor and a thank-you message goes out. The process is an example, so adapt it.

Common mistakes

• Giving everyone full access "to keep it simple". It is simple until someone leaves or an account is compromised.
• Sharing one login. You cannot tell who did what, and you cannot remove one person without changing the password for all.
• Forgetting the team inbox. If client emails sit in personal mailboxes, a departing member takes the history with them.
• Hiding too much. An editor who cannot see the deadline or style notes will ask you every time. Hide money and contact details, not the instructions.
• Setting permissions once and never checking. Roles drift as people take on more.

Example: a six-person studio

Example: an owner, a studio manager, two photographers, one freelance editor and one second shooter who works weekends. The owner and manager see money and settings. The photographers see their own jobs, call sheets and client notes. The editor sees the files, the style notes and the deadline for each job. The second shooter sees the call sheet and timeline for the days they are booked. When the second shooter stops working with the studio, only one account needs to be removed, and no pricing was ever visible to them. The structure is an example, so shape yours around your own tasks. For how a larger crew coordinates, see crew for large events and team communication.

How ClickBook helps

ClickBook has owners, admins and members, with editors and freelancers seeing only their own work, never prices or income, and a team-only inbox. A won deal becomes a project with crew and call sheets so each person gets what they need. See it in the demo.

Frequently asked questions

Should freelancers see client prices?

Usually no. A second shooter or editor needs the job details, not what the client paid. Limiting access also reduces awkward comparisons.

How many admins should a studio have?

As few as you can manage, often one or two. Admins can change settings and see money, so each one is a risk if their account is compromised.

When should I remove someone's access?

On the last day of their work, or sooner if you end the relationship badly. Do it the same day and change shared passwords.

Do I need written agreements as well as permissions?

Yes. Permissions limit what people can see, and agreements set out what they may do with it, including client data and images.