Give the Crew Access Without Giving Away the Keys

There is a day on every growing farm when one person can no longer do everything, and the website becomes the thing nobody else can touch. You are on the tractor, and a customer emails asking to change an order. You are at the market, and a photo needs swapping before the newsletter goes out. The answer, for far too many farms, is to text somebody the master password and hope for the best. Team Accounts is how you stop doing that forever — real staff accounts for farms, each with their own login, the right permissions, and a record of everything they touched, so you can hand the crew access without handing over the keys.

If you raise pasture-raised meat and sell it direct, the business grew up around you. For a long time that was fine — you were the only one who logged in, so there was only ever one password and one person to blame. But a farm that is working starts to need hands: a spouse who runs the books, a market crew who packs and hauls, a part-timer who is good with a camera and keeps the store looking sharp. Every one of those people needs to do their piece of the work online, and none of them should have to become you to do it. Team Accounts, which arrives on the Farm To Net Growth plan and scales up to unlimited staff on Pro, is the difference between delegating and dumping — between giving someone the exact access their job requires and giving away the whole farm.

The one-password problem every growing farm eventually hits

It starts innocently. You build the website, you set a password, and for a season or two you are the only human who ever types it. Then the farm grows. You bring on help, and help needs to get into the admin — to check an order, update a price, fix a typo, post a restock. So you do the thing that feels easiest in the moment: you read the password aloud across the barn, or you text it, or you write it on the whiteboard by the office door. And just like that, the single most important login on your farm is known to three, four, five people, none of whom you can tell apart once they are inside.

The trouble with a shared master password is not that your crew is dishonest. It is that it erases every boundary at once. The seventeen-year-old who helps at the Saturday market now has the same power as you: to change bank details, to delete products, to refund orders, to see every customer's contact information, to knock the whole store offline with one wrong click. When something goes wrong — a price is suddenly half of what it should be, a product vanishes, a payout account gets edited — you have no way to know who did it, because everyone is the same person as far as the system is concerned. There is no accountability because there is nothing to hold anyone accountable with.

And a shared password is fragile in the ordinary ways too. Someone leaves the farm on bad terms and still knows how to get in. Someone reuses that password on a site that gets breached, and now a stranger has it. You want to cut off one person's access and you cannot, because cutting them off means changing the password for everybody and re-distributing it — which just recreates the whole mess. Farm team management that runs on one shared login is not management at all. It is a standing risk you have simply gotten used to.

The goal was never to keep the crew out. It was to let each person in exactly as far as their job goes — and to know, afterward, who did what.

Team Accounts replaces the shared password with something a real business runs on: individual farm employee logins, each tied to a person, each carrying a role that defines what that person can and cannot do, and every meaningful action written to an activity log. Nobody shares a password again. Nobody has more power than their work requires. And when you need to know who changed the price of the ribeye at 9pm on a Tuesday, the answer is right there.

How Team Accounts actually works

The idea is simple enough to explain in a sentence: you invite people by email, you give each one a role, and the software enforces what that role is allowed to do. But the everyday feel of it is what matters, so here is what it is actually like to run.

Every person on your team gets their own account, reached from their own email address, protected by their own login. When you bring someone on, you invite staff by email — you type their address, choose the role that fits their job, and send. They get a message, they set up their own login, and from that moment they are a distinct person inside your farm's admin, not an anonymous copy of you. When they do their work — edit a product, mark an order ready, publish a page — the system knows it was them, because they signed in as themselves.

The heart of it is role based access for the farm. A role is a job description the software understands. Instead of every login being all-powerful, each account carries a role — owner, manager, or editor — and that role draws a clear line around what the person can reach. An editor can do editor things and cannot do owner things, not because you asked them nicely, but because the buttons that would let them simply are not there for them. This is what turns "please don't touch the payout settings" from a hope into a fact.

The three roles, in plain language

You do not need a security degree to set this up. There are three roles, and each maps to a kind of person you already have on the farm.

• Owner is you — or you and a business partner. The owner can do everything: change billing and payout details, invite and remove other team members, set everyone's roles, and reach every corner of the store and the site. Owner is the top of the ladder and the smallest circle. Most farms have one owner, sometimes two. This is the role you never hand out casually, because it is the role that can hand out every other role.
• Manager is the person who runs the day to day but does not need the keys to the bank. A manager handles the real operating work — products, prices, orders, customers, the store, the schedule — everything it takes to keep the farm selling and shipping. What a manager cannot do is touch the things that put the whole business at risk: billing, payouts, and adding or removing other people. Your right hand, the person you trust to run the shop while you are haying, is a manager. They can run the farm without being able to rewrite who gets paid.
• Editor is for the hands who do a specific slice of the work. An editor can work on content and the everyday pieces they are responsible for — updating a page, fixing a description, keeping products current — without reaching pricing decisions, customer data they do not need, or any of the settings that steer the business. The market helper, the part-time content person, the family member who keeps the photos fresh: editor is the role that lets them contribute without exposing anything they have no reason to see. It is the answer to "I want help, but I do not want to worry about what they can break."

These three cover the shape of almost every farm crew, and the point of them is subtraction, not addition. Each step down the ladder takes away power the person does not need — access to money, access to customers, access to other people's accounts — until what is left is exactly the work you hired them for. That is what good permissions for farm store software feel like: invisible when you are doing your job, immovable when you are reaching for something that is not yours.

The audit log: who changed what, and when

Roles decide what a person can do. The activity log records what they did. Together they are the whole answer to running a multi user farm website without losing your mind, because between them they cover both halves of trust: limiting what can go wrong, and knowing exactly what happened when something does.

Every meaningful action on the farm — a price changed, a product added or removed, an order edited, a page published, a team member invited — is written to an activity log with a name and a time attached. It is a quiet, factual history of your farm's back office. Most days you will never open it. But the days you need it, you need it badly, and having it changes the emotional temperature of the whole operation.

Picture the moment: you notice the price of your ground beef is wrong. On a shared-password farm, this is the start of an argument nobody can win, because there is no way to know who did it or whether it was even done today. With an audit log, it is a ten-second question. You open the log, you see the change, you see the name, you see the time, and you either fix a mistake and gently coach the person who made it, or you find out it was you three weeks ago and quietly close the tab. Either way, the drama is gone, replaced by a fact. Accountability stops being an accusation and becomes a record.

The log does something subtler, too. It makes people careful in the good way. When your team knows their work is signed with their name, they slow down at the right moments, because there is no anonymous hiding place. That is not surveillance — you are not watching over their shoulder — it is just the ordinary accountability every real workplace has, finally present on the one system your whole business runs through.

Who this is for

Team Accounts shows up differently depending on the shape of your farm and the shape of your crew. A few pictures.

The farm that grew past one person

For a long time it was just you, and the website was a solo instrument — one password, one player. Then it was not. You brought on a first employee, and suddenly the thing that made you efficient, being the only one who could log in, made you the bottleneck. Every online task waited for you. A customer's change waited for you. A restock post waited for you. Team Accounts is how you stop being the single point of failure for your own farm's website. You give your first hire a login and a role, and the work that used to pile up behind you starts flowing again — without you having to be nervous about what you just handed over, because the role decides that for you.

The farm with a market crew and a bookkeeper

This is the classic case, and it is where team roles farm software earns its keep. You have two very different kinds of helper. The market crew needs to see orders and pull sheets, mark things ready, maybe fix a product now and then — the operating work of getting boxes to people. The bookkeeper needs the numbers and the exports and nothing else; they have no business editing your storefront, and they do not want to. One master password would give both of them everything, which is exactly wrong for both. With roles, the market crew becomes managers or editors who can run fulfillment, and the bookkeeper gets an account scoped to what a bookkeeper does. Each person sees the shape of their own job when they log in, and the farm hums, because nobody is wading through tools that are not theirs to reach a job that is.

The farm nervous about sharing the master password

Maybe you have been avoiding hiring help for the website at all, because the only way you know to grant access is to hand over the master password, and every instinct you have says do not do that. That instinct is correct, and it has been quietly costing you — because it means you keep doing work that someone else could do, simply because the alternative felt dangerous. Team Accounts removes the danger from the equation. You never share your login. You create theirs, at the level you choose, and you can change it or revoke it in seconds without disturbing anyone else. Access without the master password is not a compromise; it is how it was always supposed to work.

The farm that needs an audit trail

Some farms reach a size or a structure where "I trust everybody" stops being enough on its own — not because trust is gone, but because the operation is big enough that memory no longer covers it. Multiple people are making changes, seasons are long, and "who set that price?" becomes a real question with real money attached. For these farms the audit log is the whole reason to be here. It gives you a paper trail for a paperless business: a record you can check, a way to reconstruct what happened, and the plain accountability that lets a bigger team stay a trustworthy team. Growth stops meaning "more people who could have done it" and starts meaning "more people, each accountable for their own work."

Everyone-shares-one-login versus roles and an audit log

It is worth laying the two worlds side by side, because most farms are living in the first one and have half-forgotten there is a second.

• One shared master password means everyone is you. The market teenager can change your payout account. Anyone who has ever been told the password still knows it. When something breaks, there is no way to know who did it. Cutting off one person means changing the password for all. There is no accountability, because there is nothing to attach a mistake to. It feels simple right up until the moment it costs you.
• Farm To Net roles and an audit log mean everyone is themselves. Each person has a login scoped to their job — owner, manager, or editor — so nobody has power they do not need. You revoke one person without touching anyone else. Every meaningful change is signed with a name and a time. Accountability is built in, not bolted on. It feels like the simple thing was actually the dangerous thing, and this is the calm you did not know you were missing.

The move from the first world to the second is not a big project. It is an afternoon of inviting the people you already work with and giving each of them the role they already, informally, have. The difference is that afterward the software enforces the arrangement you were previously enforcing by trust and vigilance alone.

From invite to the right access, step by step

To make it concrete, here is exactly what bringing a person onto your farm's team looks like, start to finish.

• Open your team settings and choose to add someone. This is owner territory — you, or a co-owner, deciding who gets in and how far.
• Invite them by email. Type the address of the person you want to add — your market lead, your bookkeeper, your content helper — and send the invitation. No password is created by you, shared by you, or ever seen by you.
• Choose their role. Manager for the person running the day to day. Editor for the hand who works a specific slice. The role you pick draws the boundary; you are deciding what part of the farm this person can reach before they ever log in.
• They accept and set up their own login. The invited person gets the email, follows it, and creates their own account with their own credentials. From that moment they are a distinct person in your system, not a copy of you.
• They work inside their role. When they log in, they see the tools their job needs and not the ones it does not. The manager runs orders and products; the editor keeps content current; neither can wander into billing or into each other's accounts.
• You watch the log, not the person. As the team works, the activity log fills in quietly — who changed what, and when. You do not hover. You have a record, which is better than hovering ever was.
• You change or revoke access in seconds. Someone's role changes, or they leave the farm. You adjust their role or remove them entirely, instantly, without disturbing a single other person's access. No password to change, no crew to re-notify.

That is the entire arc: from "I need help but I am scared to give it" to "the right person has exactly the right access, and I can prove who did what." It takes minutes to set up and it removes a worry you have probably carried for years.

Where Team Accounts fits with the rest of your farm

Team Accounts is not a standalone gadget; it is the layer of control that makes everything else on Farm To Net safe to share. The reason to give a manager a login at all is so they can do real work — and the real work lives in the rest of the platform. When your market lead logs in to run fulfillment, they are working inside order management, pulling packing lists and moving orders from paid to ready. When your content helper keeps the storefront sharp, they are shaping your online store and the pages you built with the website builder. If you run recurring shares, a manager can keep members and boxes on track through your CSA subscription tools — all without ever touching billing or the master account.

That is the whole point. Team Accounts does not add features so much as it makes your existing features delegable. Everything your farm already does online becomes something you can safely hand to the right person, at the right level, with a record of what they did. The store, the orders, the site, the subscriptions — all of it, shareable without being surrenderable.

What it costs, and how to start

Team Accounts starts on the Farm To Net Growth plan, at $79 per month, which gives a growing farm up to three staff accounts — the full set of roles (owner, manager, editor) and the activity log that keeps a small team accountable. When your crew outgrows three, the Pro plan, at $149 per month, opens it up to unlimited staff accounts, for the larger operation or the multi-location farm. Either way you get real logins, real roles, and a signed record of who did what.

You do not have to commit blind to find out whether it fits. Farm To Net plans start at $29 per month, every plan comes with a 14-day free trial, and there is no credit card required to start. You can stand up your farm, feel how the platform runs, and move up to Growth when your crew is ready for their own logins — then to Pro when the team grows past three. The moment the shared password starts to feel like a liability — the moment you catch yourself about to text it to one more person — is the moment Team Accounts pays for itself.

You built a farm big enough to need a team. That is a good problem, and it deserves a real solution — not a whiteboard password and a silent prayer. Give the crew their own logins, give each one the role that fits, keep the record that settles every "who did that," and get back to the work only you can do. Access without handing over the keys. That is the whole idea, and it takes an afternoon to put in place.

Frequently asked questions

How do I add a staff member to my farm's website?

You invite them by email. From your team settings, type the person's email address and choose their role — owner, manager or editor — then send the invitation. They accept, set up their own login, and from that moment they have their own account scoped to exactly what their role allows. You never create, share or see their password.

What is the difference between the owner, manager and editor roles?

The owner (usually you) can do everything, including billing, payouts and managing other team members. A manager runs the day-to-day operation — products, prices, orders, customers and the store — but cannot touch billing or add and remove people. An editor works on a specific slice, like content and everyday updates, without reaching pricing, customer data or business settings. Each role removes only the power the person does not need.

Can I see who changed something on my farm's site?

Yes. Team Accounts keeps an activity log that records meaningful actions — price changes, product edits, order changes, published pages, team invites — each stamped with the name of the person who did it and the time they did it. When you need to know who changed what, you open the log and read it, instead of guessing.

Is this safer than just sharing one login with my crew?

Much safer. A shared master password gives everyone the same total access, leaves no record of who did what, and forces you to change the password for the whole crew just to remove one person. With individual logins, roles and an audit trail, nobody has more power than their job requires, every change is signed with a name, and you can revoke one person in seconds without affecting anyone else.

What happens when an employee leaves the farm?

You remove their account instantly, and their access ends immediately — without disturbing anyone else and without changing a shared password. Everything they did while they worked for you remains in the activity log, so you keep the record even after the person is gone. This is exactly the problem a single shared password cannot solve.

Which plan includes Team Accounts and what does it cost?

Team Accounts starts on the Farm To Net Growth plan at $79 per month, which gives a growing farm up to three staff accounts with the full set of roles and an audit log. When your crew grows past three, the Pro plan at $149 per month opens it up to unlimited staff accounts. Platform plans start at $29 per month, every plan includes a 14-day free trial, and no credit card is required to start, so you can try Farm To Net first and move up as your team grows.