When you manage a single rental with a single cleaner who handles everything, the question of permissions doesn't really come up. But the moment you add a second provider, an occasional technician, a business partner, or a co-owner who wants to follow activity, the topic becomes urgent. Who gets to see the rates? Who can modify a reservation? How do you avoid exposing your revenue to the entire field team? Easyical answers with a system of 4 distinct roles, complemented by 13 granular permissions you can fine-tune one by one on each access code.
The all-or-nothing trap
For a long time, rental management has lived between two extremes. On one side, the operator who shares their own login with the whole team, which amounts to handing the keys to the vault to everyone. The cleaner sees the Airbnb rates, a team departure forces a panicked password change, and nobody can trace who did what. On the other side, the tool with a single generic provider role: everyone has the same rights, whether they're the co-owner following the activity or the cleaning agent who comes once a week.
Both models cause very concrete problems. The first creates direct confidentiality risks. A cleaner who discovers that you charge 180 € per night while they're paid 25 € per cleaning is a delicate conversation to have, and one that can cost you dearly in future negotiations. The second model generates operational friction: a field agent seeing a validation button they shouldn't have, or conversely a co-owner ending up with actions they never asked for, because the tool doesn't draw the line.
The right approach is to clearly separate what each contributor actually has to do, without overlapping the rest. This is exactly what Easyical offers: four roles with different permission templates, and the ability to adjust each permission one by one when a particular case calls for it.
The 4 roles and who to assign them to
Each Easyical access code is assigned to one of the four roles built into the tool. Rather than a long theoretical list of profiles, these are four archetypes that cover virtually every case encountered day-to-day in vacation rental management.
The Manager role corresponds to near-complete access to the schedule and to interventions. It's the right choice for a business partner, a co-owner, or a trusted person to whom you delegate coordination. They can validate cleanings, create and manage all technical interventions, modify reservations, hide a sensitive reservation, and they see both cleaning prices and intervention amounts. One note: even a Manager access code is not meant to create properties or invite other access codes, those actions remain with the account owner.
The Cleaner role is built for the people who do the cleaning on the ground. They see the schedule for the properties assigned to them, validate completed cleanings with a single tap, flag the laundry bag as ready when you work with a linen service, and can annotate an intervention if they notice an issue (a bulb to change, a leaky faucet) without being able to create or close the intervention itself. By default, they don't see cleaning prices, intervention amounts, or cleanings assigned to other providers.
The Maintenance role is built for intervention technicians: plumber, electrician, pool technician, locksmith, whatever the trade. They see the full schedule (useful for fitting their visits around ongoing cleanings), can create, manage, and close their own interventions, see the amounts tied to interventions (since they're usually the ones who fill them in), but cannot validate cleanings and don't see cleaning prices. It's a profile most market tools forget, even though it represents a real grey area in a manager's daily life.
The Read-only role offers a complete view with no action possible. It's ideal for a co-owner who just wants to follow completed cleanings, for an accountant who consults your data occasionally, or for a partner you want to keep informed without giving them the controls. They see the schedule, the prices and the amounts, but no validation button is accessible to them.
Fine-tuning with granular permissions
The 4 roles are a starting point, but the real precision comes from the 13 modular permissions you can enable or disable on each code, independently of its role. This additional layer is what turns a classic role system into something genuinely shapeable to your operation.
Some permissions concern visibility of information. You can hide cleaning prices, intervention amounts, the number of people per reservation, the consecutive-stay badge, the shifted-hours badge, or even the indicator that flags a scheduled intervention. This is particularly useful for a cleaner you don't want to expose to the commercial layer, or conversely for showing a read-only co-owner exactly what you want them to see.
Other permissions concern what the contributor can do. You can open up full intervention management to a cleaner (by default they can only annotate), allow a Maintenance code to validate cleanings in a hybrid case, or let a Manager hide certain reservations from the entire team. The hide-a-reservation permission has its own logic: it first requires the permission to manage reservations, otherwise it stays inactive.
Finally, one permission widens the field of view: letting a provider see the cleanings assigned to their colleagues too. Useful for a team that covers for each other often, or for a team lead who wants eyes on the whole scope. The goal stays the same as with roles: let through exactly what's needed, and nothing more. If a new need shows up next week, you activate it in two clicks from your dashboard without recreating a code or touching the rest of your team.
A disabled permission cleanly hides the relevant screens and buttons, both on the web and in the iOS and Android apps. No contributor ever sees a greyed-out button without understanding why.
Security built for moving teams
Granting the right access is half the story. Being able to cut it cleanly when a provider leaves is the other half. Vacation rental management lives with teams that move: seasonal workers leaving at the end of summer, concierges who come and go, occasional technicians you may never see again. Easyical was built for this constant flux.
Each access code is unique and tied to a single person. Only one active session is allowed per code at any time: if someone logs in elsewhere with the same code, the previous session is immediately disconnected, and the person whose code was taken receives a clear message explaining what happened. This avoids the classic drift where a code ends up circulating among several people over the months, without your knowing and without any way to trace who did what.
When a provider leaves your team, you revoke their code with a single click from the dashboard. Disconnection is instant on all their devices, and every view they had in the mobile app disappears within a second. No passwords to change, no emails to send, no risk that they can still see information they should no longer have. The code becomes available again if you want to reassign it later, or you can delete it permanently.
This access discipline, almost invisible day-to-day when things go well, is exactly what makes the difference the day your team grows or something unexpected happens. When you manage 30 properties with 8 different providers, knowing exactly who has access to what and being able to adjust it in seconds is no longer a luxury: it's what lets you sleep.
The 4-role system with granular permissions is available on the web as well as in the iOS and Android apps, with the same level of control everywhere.
Conclusion
Structuring your team's access isn't an administrative formality you check off once and forget: it's the foundation of a calm operation in vacation rental management. With its 4 roles (Manager, Cleaner, Maintenance, Read-only) and its 13 modular permissions, Easyical lets you give each person exactly the right level of access, and adjust it in two clicks as your team evolves. Try it free and create your first access code in less than a minute.