What Reveto Does From Message to Reply Key Concepts
Creating Your Account First Login and the Dashboard Quick Start: Your First Client Understanding Navigation
Overview Website Crawling Document Upload Meeting Notes and Recordings Google Drive Import Telegram Chats
Generating a Knowledge Base Updating with New Sources Viewing and Navigating AI Search Editing Content Versions and History Exporting Access Control Preparing a Knowledge Base for Replies
Overview Connecting a Facebook Page Connecting Instagram The Review Queue Autopilot Reply Settings Insights The 24-Hour Window Notifications Pausing and Disconnecting
How Website Chat Works Installing the Widget Allowed Websites Widget Settings Conversations Leads Unanswered Questions Following Up on Chats
Managing Several Clients Organizing Team Access by Client
Inviting Team Members Roles and Permissions
Overview Creating a Test AI Question Generation Assigning Tests Taking a Test Grading and Results Test Analytics
Profile Settings Company Settings Notifications Claude Connector Activity Stream
Plans and Pricing Free Trial AI Usage and Billing Managing Your Subscription
Data Protection Account Security Conversation Data and Deletion
Getting Help Troubleshooting
Common Questions

Organizing Team Access by Client

Give each team member access only to the clients they work on, using roles and knowledge-base access. A knowledge base is private to the person who created it until they share it with a role.

How knowledge-base access works

  • The person who creates a knowledge base can always open it.
  • Everyone else sees it only if their role has access to the whole knowledge base or to some of its sections.
  • This applies to every role, including Company Admin.
  • There are three access levels: 'Read' (view content), 'Edit' (modify content) and 'Delete' (remove content). Each level includes the ones before it.
  • A role with access to some sections sees only those sections. New subsections get the same access as their parent section.

Sharing a knowledge base needs the 'Manage KB Access' permission, which covers every knowledge base in the company. The creator always keeps their own access, so nobody is locked out of what they built.

Set up access for one client

  1. Open 'Settings', click the 'Team' tab, then the 'Roles' tab, and click 'Create Role'.
  2. Name the role after the client or the team working on it.
  3. Tick the permissions the team needs, for example 'Messenger Replies' to handle conversations, and click 'Save Changes'.
  4. In the 'Team Members' tab, choose the new role in each person's 'Role' column.
  5. Open the client's knowledge base in 'Knowledge Base' and click 'Manage Access'.
  6. Tick the sections to share, or the knowledge base itself to share all of it. A bar appears at the bottom of the screen: click 'Set Access'.
  7. Choose an 'Access Level', choose 'Grant', tick the role under 'Apply to Roles', and click 'Apply Access'.
  8. Click 'Exit Access Mode' when you are done.

To check what a role can see, click 'View as...' in the knowledge base and pick the role. It is available to people who can manage roles, and cannot preview roles that manage users.

What roles do not separate

  • 'Messenger Replies' and 'Website Chat' apply to the whole company. A person with either permission sees every Page's conversations or the website chat, whichever knowledge bases they can open.
  • What a Page answers from is set in its 'Reply settings'. It does not depend on the access of the person reviewing the draft.
  • Knowledge bases are shared only within one company. For a hard wall between clients, use separate companies.

Roles belong to a company. Someone who is a member of two companies can have a different role in each.