This guide is for teammates who write, edit, review or approve policies in Blissbook but don't publish them. Each section below covers one task in a few lines, with a link to the full article if you need more.

Are you the one publishing? See Publisher 101.

What you can do on a policy depends on your role on that policy:

To see your role, open the policy and click Share. You're always listed first, with your access level next to your name. Your team role sets your default access to your team's policies and a policy role applies to one policy only - when you have both, the higher one wins.

Full details: Policy roles.

The policy library has built-in views to help you stay organized:

Note: The review views, including In review, only appear on Blissbook PRO plans, since that's where review and approval workflows live.

Full details: Policy Library Views.

Several people can edit a policy at the same time. Use the mode dropdown in the toolbar to switch between Editing (change the text directly) and Suggesting (your changes become suggestions for someone with edit access to accept). Commenters always work in Suggesting mode.

To comment, highlight text and click Comment, then type @ to mention anyone who can access the policy. Everything you change stays in the draft, and your audience sees nothing until someone with publish access releases or publishes the policy.

Full details: Policy Collaboration with Your Teammates.

Open the policy, click Share, then click Add on the Collaborators tab, pick their role and type their name or email. Commenters and above can add people inside or outside your organization, with any role up to their own. Someone added to a single policy sees only that policy when they log in. You can do the same action in bulk by multi-selecting policies in the table.

Note: Adding a collaborator doesn't send them an email. Click Copy Link at the bottom of the Share panel and send them the link yourself.

Full details: Notifying new collaborators.

Blissbook can email you when:

To change these, open the policy library, click Settings, then the Notifications tab, and set each one to Instant, Daily, Weekly or Never. Editors and Commenters can open this page too. Full details: Policy Library Notifications.

On a PRO plan, anyone with Editor access or higher on a policy can start a Review: Editors, Publishers, Full Access and Team Owners. Click Review on the policy, add reviewers (or a people property such as Approver, which fills in the right people for each policy), set a Due Date and choose All reviewers must approve or At least one reviewer must approve.

Leave Notify reviewers via email on to email each reviewer, even if they've turned off their policy library notifications. Reviewers respond with Comment, Approve or Request Changes, and the policy moves from In Review to Approved or Needs Revision, or to No Decision if the due date passes first.

Full details: Policy Review / Approval Workflows.

Owner, Approver and SME are usually people properties, not access roles. They record who's responsible for a policy and make it quick to pick reviewers, but they don't give anyone access. An Approver still needs a role on the policy, or a team role, to be able to open it.

Policies have two history tools:

On Blissbook plans, Revision History goes back two years. PRO keeps all of it. Full details: View old versions of your content.

Click + Add Policies in the top right of the policy library, then choose Import Policies (to import from Word), Browse Model Policies (to see Blissbook's import-ready library) or Create a blank Policy.

If you don't see the button, ask a Team Owner to turn on the Creator permission for you. New policies start as drafts, so nothing reaches your audience until it's published.

Full details: Add or upload a policy to your policy library.

Team Owners, Full Access collaborators and Publishers on a policy can publish it at any time. Publishing ends any active Review and resets the policy's phase to Clean.

The person who started the Review gets an email as each reviewer responds, but a Publisher who didn't start it hears nothing, so agree on a handoff: tell your publisher directly, or ask them to watch the In review view.

Full details: what to do after a Review.

Once your publisher releases or publishes it, your update reaches every document it's in.