Buyer verification and operating handoffs
Review Airbnb Co-Host Permissions Against the Work Agreement
AI-assisted editorial guide · Published November 20, 2026
Airbnb separates co-host permission levels and explains that platform access does not define the work a co-host has agreed to perform. An owner should review both the account settings and the operating agreement. A person may have the technical ability to change a listing without being authorized by the owner to make every business decision.
List the work that needs access
Identify the tasks the co-host will actually perform, such as answering messages, reviewing availability or managing reservations. Separate viewing information from changing it. Use concrete duties rather than a broad title like manager. This makes it easier to identify when the selected platform access is wider or narrower than the intended assignment.
Read the current permission descriptions
Use Airbnb’s official co-host guidance to compare available levels. The current descriptions distinguish full access, calendar and messaging access, and calendar access. Review the actual settings for the listing rather than assuming a longstanding co-host has the level you now intend. Save an internal record of the reviewed role without exposing account secrets.
Keep business authority explicit
Document who may approve price changes, refunds, cancellations and other material decisions. A platform permission is not the same as a spending or contractual authorization. Give the co-host an escalation path for situations outside the agreement. If the platform cannot express every business limit, the operating instructions need to make those limits understandable.
Review payout responsibilities separately
Airbnb identifies actions reserved to the listing owner, including setting or editing co-host payouts. Do not assume changing access automatically changes compensation or financial arrangements. Review those settings and the agreement separately. Record who will resolve a mismatch rather than asking staff to infer payment terms from what appears in their account.
Test the necessary workflow
Have the authorized co-host confirm that they can perform the agreed tasks in the appropriate listing. Use a harmless review of existing information rather than creating a fake booking or changing a live reservation for testing. Record any access gap and resolve it through the owner’s settings and the platform’s authorized process.
Plan for departure and replacement
When a role ends, review access, pending guest conversations and outstanding decisions together. Removing a co-host does not by itself explain who takes over a reservation issue. For example, assign an owner for a pending arrival question before the outgoing person’s access ends. Keep the transition date and remaining tasks in the property’s operating record. A permission review should also identify who can add another team member. When a new person appears in the account, confirm the role and business authorization rather than assuming the existing agreement covered that addition.
Prepare the evidence and next action
- Task-by-task access needs
- Current permission setting
- Separate business decision limits
- Payout arrangements reviewed independently
- Departure and pending-work plan
Official sources and review scope
Sources checked November 20, 2026. This guide supports preparation; it does not certify safety, determine compliance, confirm coverage or establish investment performance.
Record your follow-up
These optional notes stay in this page until you download them. They are not submitted or retained after a reload. Keep sensitive account credentials out of the notes.