Managing a Property Team: Roles and Permissions

Why solo operators eventually need to delegate

You start out doing everything yourself, then one day you cannot. As your portfolio or pipeline grows, you take on a site manager, a bookkeeper, an inspector or a regular trades team, and each of them needs to see some of your data but not all of it. The English Private Landlord Survey 2024 found that the use of letting agents rises sharply with size, with 63% of landlords holding five or more properties using an agent for letting, compared with just 30% of single property landlords (GOV.UK). Whether you bring help in house or outsource it, delegation becomes unavoidable past a certain point.

The trouble is that most small operators delegate badly. They either cling to every task because nobody else can see the data, or they hand over a shared login and hope for the best. Neither scales. This guide covers how to give your team the access they need, and nothing more.

The risk of giving everyone full access

Giving everyone full access feels easier on day one and costs you dearly later. A shared admin login or a "they can see everything" account means any mistake, leaver or compromised device can touch your whole business. Human error is the leading cause of reported personal data breaches in the UK, according to the Information Commissioner's Office.

Think about what is actually in your workspace. Tenant names and contact details. Rent figures and arrears. Mortgage balances. Supplier rates you negotiated. If your plasterer's phone is left in a van and it is logged into an account that can see your full portfolio profit and your tenants' personal data, that is a problem you created the day you handed over the login.

There is a legal angle too. Under UK GDPR, you must ensure personal data can be accessed only by people you have authorised, and that they act only within the authority you give them, as the ICO sets out in its guide to data security. "Everyone is an admin" is the opposite of that. Our guide to data security for landlords covers your obligations in plain terms.

How to think about roles

A role is a named bundle of permissions that matches a job, not a person. Start from the job each person does, list the data and actions that job genuinely needs, then build the role around that. Most UK property businesses get by with four or five clear roles rather than fiddling with permissions person by person.

Here is a practical starting set:

• Owner or admin (you). Full access to everything: builds, portfolio, finances, team, billing. Usually one or two people, no more.
• Site manager. Runs the build day to day. Needs tasks, snagging, the planner, the site diary and the project contact book. Does not need your rental portfolio, tenant data or mortgage figures.
• Inspector or surveyor. Logs defects and signs off snagging on a specific project. Needs read access to the project and the ability to add snags with photos and priorities. Does not need costs, the wider portfolio or team settings.
• Bookkeeper or accountant. Needs costs, invoices, rent figures and the ability to export to CSV or PDF. Does not need to reassign site tasks, edit snagging or manage tenants.
• Contractor or trade. Needs only their job. The electrician sees the electrical tasks and snags on the one project they are working, not your other builds and certainly not your lettings.

The point of roles is consistency. When a second site manager joins, you assign the existing role in seconds and you already know exactly what they can see.

The principle of least privilege in plain terms

Least privilege means giving each person the smallest amount of access that lets them do their job, and no more. The National Cyber Security Centre defines it as every user and process operating with the least privilege necessary to complete the task (NCSC). It is the single most useful idea in this whole article.

In everyday terms: start everyone at zero and add access deliberately, rather than starting them at full and trying to claw it back. Ask one question for each role: "What would break if they could not see this?" If the answer is "nothing", they should not see it. Your bookkeeper does not need to edit a snagging list to do the books. Your roofer does not need to know your rent roll to fix a roof.

This is not about distrust. It is about blast radius. When access is tight, a lost phone, a wrong click or a disgruntled leaver can only affect a small slice of your business instead of all of it.

Per project and per property access

Role alone is not enough. A contractor should see their job, not every job. That is where per project and per property scoping comes in: you grant a role and then attach it to specific builds or specific rental properties, so two people with the same role can be looking at entirely different data.

A worked example. You have three live refurbishments and twelve rental units. Your kitchen fitter is on the Mill Street refurb only. You give them a contractor role scoped to Mill Street. They can see and update tasks and snags on that one site. They cannot see the other two builds, cannot see any of your twelve rentals, and cannot see portfolio finances. When the Mill Street job finishes, you remove the access and they are out, cleanly.

The same applies to lettings. A self managing landlord might give a part time helper access to a handful of properties in one town while keeping the rest private. Scoping access to the project or property, not the whole account, is what makes a shared workspace safe to actually share. Doing this in spreadsheets is close to impossible, which is one reason many operators move on from them, as we cover in spreadsheets versus property software.

This is also where a tool earns its keep. In Build & Let you build custom roles and attach them to specific projects or properties, so a contractor genuinely only sees their job. The built in AI assistant re checks the user's permissions on every single action, so someone asking it "what tasks are open?" only ever gets the tasks they are allowed to see.

How to onboard and offboard people safely

Onboarding and offboarding should be a short, repeatable checklist, not a scramble. The ICO recommends reviewing user accounts regularly, at least quarterly, so that no old accounts linger for former staff to use (ICO). The same discipline applies whether someone is joining or leaving.

Onboarding checklist:

1. Decide the role before you invite them, based on the job, not the person.
2. Invite them by their own email address. Never share a login or a password.
3. Scope the role to the specific projects or properties they need.
4. Confirm what they can see by logging in as them or asking them to read it back.
5. Note the date and the access granted, so you have a record.

Offboarding checklist:

1. Revoke access on their last day, not "soon". The moment a job ends, the access should end.
2. Remove project and property scoping as well as the role.
3. Reassign any open tasks or snags they owned so nothing falls through.
4. Check shared files and exports they may have downloaded.
5. Run a quarterly sweep of everyone with access and remove anyone who should no longer be there.

The single biggest offboarding failure in small businesses is the leaver who still has a working login months later. Individual email invites and named accounts make this trivial to fix: you revoke one person without disturbing anyone else. Shared logins make it almost impossible, because changing the password locks out the whole team at once.

Example role and permission matrix

Use a matrix like this to design your roles before you set anything up. Map each role against what it can see and do, mark it clearly, and the gaps tell you where least privilege is doing its job. Adapt the rows and columns to your own business.

Two columns being mostly "No" is a good sign, not a problem. It means the role is tightly scoped. If you find yourself ticking "Yes" everywhere, stop and ask whether that person really needs to be an admin.

Frequently asked questions

How many roles does a small property business actually need?

Most operators need four or five: an owner or admin, a site manager, an inspector or surveyor, a bookkeeper, and a contractor or trade role. Resist creating a unique role per person. Build roles around jobs, then assign people to them, and scope each one to the relevant projects or properties.

Is per property access really necessary if I trust my team?

Yes, because it is not only about trust. Scoped access limits the damage from a lost phone, a wrong click or an account compromise, and it helps you meet your UK GDPR duty to limit who can access personal data. Trusted people still make mistakes, and tight access keeps any single mistake small.

What is the most common access mistake landlords make?

Sharing one login across the whole team. It removes any record of who did what, makes offboarding nearly impossible, and means one leaked password exposes everything. Use individual email invites and named accounts instead, so you can grant and revoke access one person at a time without disrupting anyone else.

How often should I review who has access?

At least quarterly, in line with ICO guidance on reviewing user accounts. Put a recurring reminder in your calendar, open your team list, and remove anyone who has left or moved on. A five minute sweep every three months prevents the dormant login problem that catches out most small businesses.

Bringing it together

Roles and permissions are not enterprise red tape. For a busy UK builder or landlord they are simply how you let other people help without handing over the keys to your whole business. Decide roles by job, apply least privilege, scope access to the right projects and properties, and keep onboarding and offboarding tight.

If you would rather not stitch this together across spreadsheets and shared logins, Build & Let lets you build custom roles, scope them per project and per property, and invite people by email, all in one workspace for your developments and your rentals. Start the 14 day free trial and set your team up properly from day one.