Admins can move existing text sections from documents into the new Policy Library by converting them to policies. This lets you reuse and manage that content as standalone policies without rebuilding it.
Before you start
A conversion can be undone if the result isn't working for you, so proceed without fear. See Going back for details.
Convert one section at a time
To ease into the conversion and start with a single policy:
Click the ••• menu next to the section you want to convert.
Choose Convert to Policy.
The conversion preview modal opens so you can see exactly what the content will look like once the conversion is done:
Convert multiple sections at a time
If there are a few more sections you want to try, check more of them off in the conversion preview modal.
To convert all text sections in the document at once:
Click the ••• menu next to the document name at the top of the editor.
Choose Convert to Policies.
This opens the same conversion preview modal with all text sections selected:
Deselect anything you don't want to convert. For example, you may have non-policy text sections within your cultural content that you don't want to clutter your policy library.
What happens when you convert?
Once you've selected the sections you want to convert, click the Convert X sections to policies button in the bottom right.
Blissbook creates new policies in your policy library (click Policy Library in the main nav on the left on your Home page). The new policies are tagged with the document they're embedded in, plus a custom property called Chapter with the chapter their root text section came from. You can hide or delete this property. It doesn't affect how the document is structured; it is a metadata field that exists in the policy library only.
All text, images, formatting, links, and access control are converted. Policies in your policy library are style-agnostic - they take on the style and branding of whatever document they're embedded in, so don't worry if the text looks unbranded or different inside the policy library. It's supposed to. You do not need to re-style policies to match your brand. If something doesn't look right, contact us and we'll help.
In your document, you'll see a card representing the embedded policy. The Phase shown on the card depends on the state of the text section before conversion:
If a text section in the draft matched the content that was live, it gets a Phase of Clean:
If edits were in progress, it gets a Phase of Drafting:
If the text section was new and has never been published, it has a Phase of Drafting and also shows a NOT PUBLISHED tag:
The text section's version history is also carried over into the new policy.
Going back
If something doesn't look right or isn't working how you expect, first contact us via live chat or email support@blissbook.com so we can help.
If we can't help, you can revert the embedded policy back to a text section:
In the embedded policy card within the document, click the ••• menu.
Choose Revert to text section.
The policy card changes back to a text section. The policy version of the section in your policy library is not deleted automatically. You can manually archive and delete that policy to get rid of it permanently. If you change your mind again and want to use it, either (A) archive and delete it and then re-convert the text section, or (B) embed the policy in your document and then delete the text section.
Publish
Once you've converted everything, publish the document so that the Draft AND Live version of your document uses your policies.
If your document had new or changed text sections, also release or publish those policies for the latest version to show up in your Live document.
Going forward, change policy content in the document by editing and publishing your policies.
Now what?
Have fun in your new policy library. You can create and use custom properties and saved views, collaborate with others, start review and approval workflows (PRO only), and publish changes to your policies.