This guide is for Team Owners, Full Access admins and Publishers - the people who take policies live and collect signatures.
Your teammates write, review and approve policies, and you get them in front of your people. If you're a policy collaborator and you're looking for help, head to Policy Contributor 101.
Set your team up
A Team Owner gets these in place before contributors start handing policies over:
Roles: give each teammate the lowest team role that fits (Policy Viewer, Policy Commenter, Editor, Publisher or Team Owner), then raise access on specific policies from the Share panel.
Creator: toggle this on, on top of their team role, for anyone who needs to create new policies.
People properties: add people properties such as Owner or Approver so contributors can pick the right reviewers for each policy in one step.
Automated Policy Reminders (PRO): an org admin can turn on a Monday-morning email that tells reviewers which policies are still waiting on them.
Full details: Add an Admin / Teammate / Collaborator.
Know when a policy is ready (PRO feature)
The person who started the Review gets an email as each reviewer responds, so you will hear about approvals on Reviews you started yourself.
The In review view in the policy library lists every policy with a review status, and you can use the filter on Phase to see a list of approved policies. Full details: In-Review Policy Phases.
Release vs. publish
The button on a policy depends on where it lives. It says Release when the policy isn't in a live document yet, Publish when it's embedded in a live document (so the change reaches your audience right away), and Release/Publish if multiple policies are selected and both apply.
After you've clicked the Release/Publish button, a pop up will confirm what's going to happen. Private release notes (Blissbook can draft them for you) sit under Advanced Settings.
Select several policies in the library to release or publish them in bulk.
A brand-new policy reaches your audience once you embed it in a document, release it and publish that document. Full details: Publishing and Releasing Policies in the Policy Library.
Publish without collecting signatures
Publishing doesn't email anyone or ask anyone to sign. Your audience sees the updated policy the next time they open it.
To point out what changed, add annotations to the text, and audience members will see them on their next visit. If you'd rather tell people directly, send an email from the Notification Center. Full details: Notification Center.
Publish and collect signatures
Blissbook collects signatures on documents, so embed the policy in a published document before you ask anyone to sign it. A directly distributed policy can't collect signatures on its own. Starting a signature round takes Full Access on the document, which Team Owners have everywhere, so a Publisher needs a Team Owner to start the round or grant that access.
Go to Reporting, pick the document in the Compliance by Document report, then open Document Actions and choose Start Collecting Signatures (the document's first round) or Start a new Signature Round. Starting a round doesn't send an email, so click Send a notification when it launches. Due dates count from when each person joins the round, so new hires get their own full window. Full details: New Signature Rounds.
After a Review
Publishing a policy ends any active Review and resets its phase to Clean. If someone else started that Review, Blissbook lets them know it ended (unless they've turned that notification off). Full details: Release / Publish after a Review.
Related articles
How audiences, signature rounds, and automated invitations work together: what happens automatically when new people join.
Signature Round Due Dates / Deadlines: set due dates for existing and future members.
Policy Sharing: collaborator roles and direct distribution.