All posts
Team & access

Giving a Cleaner or Co-Host Access, Without Handing Over Everything

A cleaner needs to know when a turnover is happening. They don't need to know what the property earned last month.

Swipe left to see both columns →

What they'd see Shared login A proper collaborator login
Check-in / check-out dates✓✓
Guest names, for arrival prep✓✓
Income and nightly ratesVisibleHidden
Expenses and payoutsVisibleHidden
Account settings and billingEditableHidden
What happens if the login is shared furtherEverything leaksStill just bookings
What happens when they stop working with youChange your own passwordRemove their login

Why the shared-login habit happens anyway

It's the path of least resistance: your login already exists, it already works, and setting up something separate feels like extra admin for a relationship that might not last long. The problem only shows up later, usually when it's least convenient — a cleaner who worked one season still technically has full access the next, or a co-host relationship ends and changing the password means resetting access for everyone else who legitimately needs it too.

What a cleaner actually needs

Which property, which dates, and roughly what state to expect it in between guests. That's it.

None of that requires seeing what the property earned, what it cost to run, or any setting that could change how the account itself works.

What a co-host might need a bit more of

A co-host handling guest communication or turnovers on your behalf typically needs a fuller view of the booking calendar, but the same principle holds: access should map to the job, not default to everything because it was easier to set up that way. Financial data and account settings still don't need to be part of it unless there's a specific reason they do.

The real risk isn't malice, it's accident

Most of the time, nothing goes wrong with a shared login. The risk is the one time it does: a phone gets lost with the login still saved in a browser, a screenshot meant for one purpose accidentally shows a financial number in the background, an old collaborator who was never actually removed still has standing access months later. None of these require anyone to act in bad faith, just for the access to have been broader than it needed to be in the first place.

How this works in Hosts Assist: a collaborator gets their own separate login, scoped to bookings only — no expenses, payouts, or settings visible at all. Remove it the moment the arrangement ends, with no effect on your own login or anyone else's.

See which plan includes collaborator logins →

Setting the habit early

The easiest time to set up scoped access properly is before it's needed for the first time, not after a near-miss makes the case for it. It costs a few minutes once, and it's one less thing to worry about every time a new cleaner starts or a co-host arrangement changes.

J

Jack, Hosts Assist

Jack builds and runs Hosts Assist. It started as a spreadsheet for his own property, then a personal app, before other hosts asked to use it too — he's still the one answering the support email and writing what's actually worked, from the same evenings spent keeping his own books straight.

Want to give your cleaner or team scoped access?

A separate login, bookings only, removable any time.

Get in touch