VILLA OWNER GUIDES · BALI · Uluwatu
Review listing access before changing Uluwatu villa management
When an Uluwatu owner reviews a listing relationship, start by identifying the account holder and authorised roles. Access changes should follow the platform’s available permissions rather than passing passwords between people.
HostKeeper prioritises Uluwatu and the Bukit. For each villa, access, service scope and availability are confirmed before an agreement.
Inventory accounts and roles
List each active listing, the account that controls it, permitted users and the contact receiving booking notices. Distinguish listing access from control of payouts or property records. Do not assume one role includes another. Ask the current account holder to explain the configuration using the platform’s own role descriptions.
Build a permission handover table
Use columns for platform, listing link, current role, proposed role and verification status. A sample row might read booking platform, villa listing, existing authorised user, new authorised user, invitation pending. The table tracks a process; it does not imply that listings, reviews or account ownership can always transfer.
Verify access before removing roles
Check that authorised recipients can perform the tasks agreed for them and receive the expected notices. Use platform-supported invitations and individual access where available. Remove obsolete permissions only after the responsible parties confirm continuity. Store sensitive recovery information securely and never include passwords in a shared operational checklist.
Fictional example: Verify a role invitation without sharing a password
An owner’s fictional listing has one account holder, a reservations assistant and a separate finance contact. A replacement assistant receives a supported role invitation but can view messages only; calendar changes are unavailable under that role. The permission inventory records this result instead of declaring the whole account transferred. The finance contact remains responsible for payout settings, which are not included in the assistant’s tasks. A test notification is checked through the platform’s available process without creating a guest booking. The outgoing role is retained until the agreed operational tasks are verified. No password, recovery code or promise that reviews can transfer appears in the shared table.
The decision this record supports
Use individual platform-supported permissions and verify each required task under the invited role. Resolve missing calendar authority with the account holder before removing the previous role. Keep payout control separate from guest messaging, and never store credentials in this operational table or assume account ownership transfers with management.
| Resource | Current authorised role | Proposed role or task | Verification |
|---|---|---|---|
| Guest messages | Outgoing assistant | Incoming assistant, supported invitation | Message access confirmed |
| Calendar editing | Account holder plus authorised editor | Incoming assistant if platform permits | Not yet available; review role |
| Payout configuration | Finance contact | No change requested | Separate from assistant handover |
Practical owner checklist
- Identify the account holder for every listing.
- Record permissions separately from payout controls.
- Use supported invitations rather than sharing passwords.
- Confirm continuity before removing previous authorised roles.
Questions owners ask
Can every listing and its reviews move to another account?
Do not assume that. Check the platform’s applicable options with the account holder. Management scope and account permissions are separate decisions that need explicit agreement.
Connect this check to villa management
Changing a manager should not leave an Uluwatu owner uncertain about who controls the property’s listings. Before handover, distinguish account ownership, permissions to edit content and access to booking messages or calendars. Confirm the transfer method with the relevant platform and record the agreed responsibilities rather than promising that every account or review can be moved.
Verify permissions listing by listing
Hypothetical example — not a client result or a market forecast
Hypothetical scenario: three listings need an authorised role change. Invitations for two are accepted and their agreed tasks verified; the third remains pending. Keep the third row open and confirm continuity with the account holder before removing its previous role. Three sent invitations do not mean three usable permissions.