Document Permissions

Find out more about how you can update your team's access to specific documents in your Waybook with Document Permissions

Elle avatar
Written by Elle
Updated over a week ago

At Waybook, we're always looking for ways to help businesses share knowledge more efficiently and get entire organizations on the same page.

We know that sharing information is key to success, but we also understand that not all information is meant for everyone. That's why we're pleased to offer Document Permissions to all Waybook teams ✨

What are Document Permissions?

Document Permissions give teams more control over how they share knowledge within their business. With this update, you can now set permissions on individual Documents, ensuring that only the right people have access to sensitive information in your Waybook.

You can assign Document Permissions to an entire group or a specific team member, making it easy to ensure that your team has access to the information essential to their role within your business.

Why are Document Permissions important?

Document Permissions help businesses keep their knowledge secure while still sharing it efficiently. By giving teams more control over who can access information, businesses can avoid sharing mishaps, as well as reduce overwhelm by removing irrelevant Documents from your team's Waybook dashboard. With Document Permissions, you can rest assured that the information in your Waybook is only accessible to the people who need it.

How to use Document Permissions?

  1. Log in to your team's Waybook.

  2. Go to the member group or individual you want to set permissions for.

  3. Choose the permission level you want to assign based on specific Documents.

You can choose whether to hide a specific Document from a group or team member, or even allow your team to edit or publish content within a Subject.

If you have any questions about Document Permissions or want to learn more about how they work, please don't hesitate to contact our support team. We're here to help! πŸ™‚

Did this answer your question?