Practical guide

Give collaborators the access their job needs

Last materially reviewed 2026-09-19

Quick answerSeparate account ownership from day-to-day collaboration and keep access removal part of the workflow.
What to know

List roles before users

Write down who owns the account, who handles guests, who manages property work and who reviews financial records. Then ask which roles the chosen plan actually supports. A package advertising team access does not prove that every permission boundary matches your operation. Avoid sharing a primary owner password merely because several people need to see the calendar.

What to know

Demonstrate the boundary

Use the vendor’s supported method to show what a collaborator can see and change. Verify the important negative case: information or actions that should remain unavailable. Do not place real sensitive guest data in a demonstration unnecessarily. Keep findings tied to the tested account configuration, since a role name alone does not establish its exact permissions across different products.

What to know

Prepare for an unavailable owner

Keep account recovery and responsible contacts documented privately using appropriate secure storage. This guide is not permission to expose credentials or bypass a provider’s identity checks. Decide who coordinates urgent operational work if the owner cannot sign in. A collaborator’s ability to answer a guest question is not the same as authority to change billing or account ownership.

What to know

Remove access deliberately

When a role ends, follow the supported removal process and transfer unfinished responsibilities first. Check integrations or shared records that relied on the departing person. Do not silently delete useful work just to tidy a user list. Review access when responsibilities change, not only when something goes wrong, and keep the record proportionate to the information involved.

What to know

A role-boundary test

For a fictional cleaner role, ask the vendor to show both the required turnover information and an example of information that should remain restricted. Record the tested subscription and configuration. A successful positive demonstration alone does not establish the negative boundary. Do not grant access to real sensitive records merely to discover whether the intended restriction exists.

Continue when useful

Next: Keep guest records useful without spreading them everywhere

Use the minimum information needed for each task and keep private records out of public tools and examples.

Open Keep guest records useful without spreading them everywhere →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. OwnerRez base and premium-feature pricing — Alternative provider · ownerrez.com · Publisher independence not verified · checked 2026-09-19
  2. Lodgify configured plans and feature boundaries — Merchant documentation · lodgify.com · Merchant-controlled · checked 2026-09-19