Reusable Content Libraries & Inheritance

Several Haven features let you author a piece of content once and reuse it across many listings: Rental Agreements, Local Guides, FAQs, Blog posts, and Taxes. They all follow the same mental model — a library of reusable items, attached to individual listings or applied as a multi-unit site (group) default that members inherit. Learn the pattern once and it works the same way everywhere.

The shared model

Every library feature has three layers:

The library — where you create and edit the reusable item (a rental agreement template, a local guide, an FAQ set, a blog post, or a tax rule set). Each library lives on its own dashboard tab — rental agreements under Settings → Trust & Safety → Rental agreements, local guides, FAQs and blog posts under Grow your brand → Shared Page Content, and taxes under Payouts → Tax rules.
Attach to a listing — pin a library item to a single property so that listing renders a live snapshot of it.
Multi-unit site default — apply a library item to every listing on a Multi-Unit Site (a branded booking site that bundles several properties) so members inherit it automatically — including listings you add to the site later.

Where each library lives

Content	Library tab	Attach per listing	Group default
Rental Agreements	Settings → Trust & Safety → Rental agreements → Library	Property settings → Manage	Multi-unit site default
Local Guides	Grow your brand → Shared Page Content → Local guides → Library	Edit Listing → Arrival → Local guide (source picker)	Multi-unit site default
FAQs	Grow your brand → Shared Page Content → FAQ library → Library	FAQs → Property settings	Group defaults + apply policy
Blog	Grow your brand → Shared Page Content → Blog library → Library	Blog → Property settings	Multi-unit site default
Taxes	Payouts → Tax rules	Per-listing tax rules	Multi-unit site default → inherit

Everything you write is a library item — automatically

There is no "save to library" step. You can start authoring from whichever surface you're already on; they all write to the same library:

Write on a listing or site — type FAQs, build a local guide, add blog articles, or write a rental agreement right where you are. Haven creates the library item for you the first time, names it after the site (for example Blue Fin FAQs, Blue Fin Guide, Blue Fin Blog, Blue Fin — Rental agreement) and attaches it to that site. Rename it any time in the library.
Create directly in the library — open the feature's Library tab and create a new item. It's saved but not attached to anything until you pick it on a listing or site.
Set a default for a whole multi-unit site — on the Multi-Unit Site edit page, pick (or write) the default for that feature. Haven applies it to every current member and auto-applies it to listings added to the site later.

Haven never creates "orphan" content that only one listing can use — every item is reusable from the moment it exists.

How inheritance is resolved

The guiding rule is the most specific setting wins, and Haven never silently mixes two conflicting sources.

A listing-level attachment overrides a group default. If a property is pinned to its own item, that's what guests see — even if its multi-unit site has a different default.
No pin → inherit the group default. A listing with no item of its own inherits its multi-unit site's default.
Conflicts are surfaced, not guessed. If a listing belongs to more than one multi-unit site and those sites imply different defaults, Haven blocks the ambiguous setup and asks you to resolve it (pin directly on the listing, align the site defaults, or change the listing's site membership) rather than picking one for you. The editor shows a banner explaining whether the content is custom, pinned from the library, inherited from a multi-unit site default, or blocked until a conflict is resolved.

Exact apply behavior varies slightly by feature — for example FAQs, Local Guides, and Taxes offer a group apply policy (apply to all members, or apply but let individual listings override) and a stop inheriting / customize action on each listing. See each feature's article below for the specifics.

Editing a library item — and where the change shows up

An attached item is edited in place: the FAQ list, local guide or blog you see on a listing is the library item, so changing it there (or in its library tab) updates every listing and site it's attached to. Pinned listings render a live snapshot of the item, so nothing else needs doing.

When an item is shared with other sites, the editor says so ("shared with 2 other sites — edits apply everywhere"). If you want a one-off version for this listing instead, choose New … for this listing in the source picker — you get a fresh copy, named after the listing, that only it uses.
Rental agreements are the exception: the text is edited in the library (Edit in library on the listing's agreement), and a substantive edit bumps the version and may ask upcoming guests to re-sign.
A listing that inherits a multi-unit site default is read-only on the listing; pick Use own … to take your own copy, or edit the shared item in the library.

Ordering what's inside an item

You control the order guests see, and it travels with the library item:

FAQs — drag a question by its handle to reorder.
Local guides — drag places within a list; drag a list tab (or use the Move earlier / Move later arrows) to reorder the list tabs.
Blog Autopilot — any library blog can write itself: open the blog in the Blog library, turn on the Blog Autopilot card, pick content pillars and a cadence, and Haven researches your area, writes a sourced post, and either drafts it for your review or publishes it and emails you. See Blog Autopilot.
Blogs — drag posts by the grip at the left of each row (in the Blog library or a site's Blog panel). New posts land at the top; the featured post is always shown as the large hero card first, and the rest follow your order. Each post also has an optional Category in the post editor (pick one you already use or type a new one); when any post has a category, the site's Blog page shows an All + per-category filter row above the posts, and posts without a category appear under All. A post copied as HTML (from WordPress's Code editor, or any plain-text copy of the page's HTML) can be pasted straight into the body and keeps its headings, paragraphs, bold, italic, lists and links; so can a post copied from the rendered page. To link words inside a post, open it in the post editor, select the words, click the link icon in the body toolbar and enter the address; links are clickable on the published post, and links to other sites open in a new tab.
Blog post images — in the post editor, Insert image (in the body toolbar) puts a photo on its own line with two fields under it: Alt text (what screen readers and search engines read) and Caption (optional), which shows under the photo on the published post. Hero image, Insert image and Card thumbnail each offer Upload, From properties (your listing photos) and From library; in the Blog library, From properties spans every property you manage.
Generate an image — next to Upload on the Hero image and Card thumbnail slots and on Insert image in the body toolbar, the Generate button (the one with the orb) opens a dialog that first reads your post and your listing and proposes what the picture should show: for a hero, the post's subject; for an inline image, the heading and paragraph your cursor is in; and in every case the property's location, type, amenities, nearby places and facts, so the scene looks like the place the post is about. The line under the scene says what Haven read. Edit the words, or type your own and press Draft from the post to have Haven write a scene around them; reading and drafting is free. Pick a style (photo, watercolour or flat illustration), a shape (wide, square or portrait) and how many options to draw (two or four); the dialog shows the price in credits before anything runs and charges your AI credits only when you press Generate. The image you choose lands as the hero or thumbnail, or on its own line at the cursor, with alt text and an editable caption already written. Images are made for your own blog and never carry logos, brand marks, signage or text, and they are set in your region without copying a specific real building or storefront; review them before you publish. Manual upload, From properties and From library stay where they were.

Guidebook pages work a little differently

Individual guidebook pages (guide components — WiFi cards, check-in pages, PDFs, links, embeds) are not library items in the sense above. They are reused listing-to-listing instead: from Edit Listing → Arrival → Add page → Reuse you can add a page from any of your other guidebooks either as a linked page that stays in sync or as an independent copy. See Reuse Guidebook Pages Across Properties.