As soon as a second person works on your properties, the question of access comes up. Sharing your password is the fastest solution, and the riskiest: everyone sees everything, can change everything, and you no longer know who did what. Management software lets you give each person an account, with only the permissions their role needs. This guide suggests a simple breakdown.
The short answer
Create one account per person, never a shared account. Give each person the minimum their role needs: cleaning sees its jobs and the properties concerned, check-in sees arrivals and messages, a partner or manager can go further. Limit access to payments, security deposits and owners' details. Remove access the day someone leaves the team.
Why avoid a shared account
| Shared account | Individual accounts |
|---|---|
| Everyone sees revenue and contact details | Each person sees what concerns them |
| Impossible to know who changed a booking | Actions are tied to a person |
| Changing the password locks out the whole team | One access can be removed without affecting the others |
| High risk if someone leaves or loses a phone | Risk limited to one account |
A breakdown by role
Cleaning team
- see their upcoming cleanings and the properties concerned;
- fill in the checklist and add photos;
- report a problem or a missing item;
- no access to prices, revenue or guest messages.
Check-in and guest service
- see the day's arrivals and departures;
- read and answer messages;
- view bookings;
- no access to payments or security deposits, unless specifically needed.
Manager or partner
- manage bookings and the calendar;
- track cleanings and assign providers;
- access to finances depending on the role;
- management of properties and settings.
Owner
An owner needs to follow their property and revenue, not change your settings. A clear monthly statement is often more useful than direct access: see our guide to the owner statement.
Data to protect
Some information should stay limited to a few people:
- payments, security deposits and refunds;
- guests' full contact details, beyond what's needed for the stay;
- owners' contact and bank details;
- access codes for every property, when a person only works on a few.
Handling arrivals and departures in the team
- When someone joins: create the account with the role's permissions, explain the tool, check after a week.
- When someone changes role: adjust the permissions rather than creating a second account.
- When someone leaves: deactivate the account the same day, and change the access codes of the properties they knew.
How it works in Boostinghost
Boostinghost offers sub-accounts for the team, with permissions turned on one by one: calendar and bookings, cleaning, messages, payments, finances, properties. A cleaning provider only sees what's been opened to them, from the website or the mobile app. See also our guide to coordinating your cleaning teams.
Frequently asked questions
Should an independent cleaner have an account?
It's better: they see their up-to-date jobs, fill in the checklist, and you avoid exchanging messages for every change.
Should the whole team have access to guest messages?
No. Keep it for the people who answer guests; the others don't need it.
What if a phone is lost?
Deactivate or change the access of the account concerned, without touching the others.
How many accounts should you plan for?
One per person who works regularly, even part-time.
Key takeaways
One account per person, permissions limited to the role, and access removed the day someone leaves: those are the three basic rules. They protect your data, your guests' and your owners', and make every action traceable.



