Team & roles

Everything here lives at Settings → Company → Team & roles.

Two things decide what someone can do

This is the part that confuses people, so it’s worth reading once properly. Membership level and role are separate axes, and a person has both.

Membership level is the coarse one:

Membership	Access
Owner	Everything, including billing and deleting the organization.
Admin	Full operational access and team management. Not billing, not deletion.
Member	Whatever their role allows.

Roles are the fine-grained part. LawnLedger ships four ready to use:

Role	Built for
Estimator	Quoting. Customers, properties and estimates; can see invoices but not touch them. No team settings, no billing.
Crew Lead	Running crews. Schedule and complete jobs, assign work, approve time, log expenses. Financials are view-only.
Mobile Crew	The field. Assigned jobs, clock in/out, checklists, photos. Mobile app only.
Accountant	An outside bookkeeper. Read-only across reports, the ledger, invoices, expenses, banking and budgets, plus exports — and deliberately no ability to create, edit or delete anything.

A custom role named “Administrator” is not the Admin membership level. It holds whatever permissions you gave it and nothing more. If someone needs to manage the team, raise their membership level — don’t name a role after it and hope.

Adding someone

Settings → Company → Team & roles → Invite Member

Enter their email

Set the membership level

Member for nearly everyone. Admin for someone who genuinely needs to manage the team.

Pick their role

This is where the day-to-day permissions come from.

Send the invitation

They get an email, accept, and set up their own account. Pending invitations stay in the Team list — resend or revoke any time before they accept.

Invitations offer Admin or Member only — ownership is transferred, not invited. And you can’t grant access you don’t hold yourself: only an Owner or Admin can issue an Admin invite, and a Member with permission to invite can’t attach a role more powerful than their own.

Custom roles

Start from a built-in role and clone it. Building from an empty role means discovering the ten permissions you forgot one support call at a time.

Permissions are codes grouped by area — 95 of them across 28 areas — and they follow a consistent shape:


customers.view    customers.create    customers.edit    customers.delete
jobs.view         jobs.create         jobs.edit         jobs.assign      jobs.complete
invoices.view     invoices.create     invoices.send     invoices.record_payment    invoices.refund

The verbs are the useful part. invoices.view is not invoices.send, and invoices.record_payment is separate again — so an office assistant can chase payments without being able to issue or void an invoice.

invoices.refund and banking.manage move real money. Grant them deliberately, to people you’d hand the chequebook to.

A worked example: the new office assistant

They answer the phone, book work, and chase payments. They should not be able to delete a customer or see the books.

Clone Estimator, then:

Add jobs.create, jobs.edit, jobs.assign — they book work
Add invoices.send, invoices.record_payment — they chase payments
Leave out invoices.refund, invoices.delete, customers.delete
Leave out everything under banking, reports, settings

Membership level: Member. Now the worst mistake they can make on a bad Monday is one you can undo.

Changing and removing people

Change someone’s role from the dropdown next to their name in the Team list. It takes effect on their next request — no re-invite.

Removing a member revokes access immediately. Their history stays: jobs they completed, invoices they created, time they logged. That’s deliberate — an audit trail with people deleted out of it isn’t an audit trail.

Removing your only Owner would lock the organization out of its own billing. Promote someone else first.

Checking what happened

Settings → Activity → Audit log records significant actions with who, what and when. Filter by user, action type or date. It’s the answer to “who changed this price?” — and the reason to give people their own login rather than sharing one.

It is Owner-only. Admins can manage the team but can’t read the log of it.

Tips

One login per person. Shared logins make the audit log useless and make removing someone impossible.
Review roles when someone changes job. The promoted crew lead usually keeps field access they no longer need.
Require two-factor for anyone with money permissions. See Security & two-factor.