As you're getting started in Guru, there are some common terms that are handy to know. Here's an overview of basic Guru terminology:
Admins are your team leads who manage the segmentation of your content, all users and their permissions, the structure of the team, and billing information. An admin cannot create content unless they are also in a Group with Author access.
Authors are subject matter experts and/or managers. Authors are the people on your team who create and manage content for the team to use.
API (Application programming interface) Guru's API uses the REST protocol with JSON as the data format. Contact Guru support for your individual username and token. Documentation here.
A Board allows you to build out and refine the architecture of your knowledge by topic, so that you can see and track the information you've created in one area and your team can read through the Cards in a narrative format.
A Board Group consists of Boards that are grouped under one heading, allowing for a higher level of organization above Boards. Board groups are useful for managing the organization of your knowledge.
Cards are the building blocks of knowledge in Guru. All of your team's content is stored in Cards. They are optimized for easy search and use by your team. Unlike long documents that make finding specific information difficult, Cards display bite-sized content, allowing you to perform one search and find the exact answer you need.
The Card Manager, available to Authors only, allows you to slice and dice your content. With this feature, you can concretely assess, edit, and understand the status of all the content in your knowledge base. You can also perform bulk actions in the Card Manager.
Like Authors, Collection Owners have the ability to create, edit, and manage content. They also have the ability to restrict certain users from seeing specific content within a Collection. They can share a particular Board or set of Boards with Groups they set.
You can comment on a Card to alert your team of new knowledge in Guru, to ask an expert a clarifying question, or to remind someone that content needs to be updated.
A user's permissions and Collection access is determined at the Group level. Your Groups should represent the division, as well as the expertise, of users in your team.
A Guru team is a collection of users that are billed together. A team can be a whole company or a department (ie, sales). Collections allow teams to isolate their knowledge within one account. Users access content via Groups which are given access to Collections.
Guru Slack Integration
The Guru app for Slack allows you to search your Cards and capture insights from your chat conversations as Guru Cards. You can also verify Cards, answer questions, receive notifications, set up activity feeds, and of course surface your content, all without leaving Slack!
Guru's Content Migration expedites the process of importing your existing content, so your team can experience the benefit of Guru right away.
With Knowledge Triggers, Guru can suggest knowledge for your team based on multiple fields on the page, and the setup process is so easy any user can do it. This means managers can easily coach their users with information pertinent to the user.
Knowledge Sync allows your team to bring content from an external source and populate that content into a Read-Only Collection within Guru.
When someone @mentions your username in a comment, you'll receive a notification.
Notifications are a way for Guru to tell you about items that need your attention, even when you're busy or on the go. You can choose to receive notifications via email or in Slack.
Pins allow you to attach relevant Cards to a desired website or app so your team sees important information when they navigate to it.
Guru's Q&A (Ask an Expert) feature allows you to ask your question and select the expert or Group best suited to answer it. Their response will be turned into a Card, enabling you and the rest of the team to access the answer again. Over time, it even learns from your questions and surfaces Cards accordingly.
Read-Only users are the reps/agents on your team. They continually access and interact with Guru to do their job and ask questions, but they are not creating content.
Related Cards are Cards that members of your team have leveraged so you can easily utilize the same information trusted by your team as you navigate through your knowledge base.
Roles represent a user's permissions in Guru and can vary across the Collection and Group level.
Sections let you visually segment cards within a specific Board to help you further organize the narrative view of knowledge, and to make it easier to browse and consume content.
Single sign-on (SSO)
Single sign-on (SSO) is a process that permits someone to enter their name and password from one system (like Okta or OneLogin) in order to access their Guru account, without needing specific account credentials for Guru.
Tags enhance Guru's search functionality by allowing your team to zero in on highly specific attributes of content. Only Authors can create tags.
The Tag Manager, available to Authors only, allows you to organize, create, edit, and delete tags in bulk.
Your Trust Score communicates the percentage of content in your account that is up to date. You can find your team's trust score in the browser extension, web app, or in Analytics.
Verification Status is an indication as to whether or not the content is up to date. The color and symbol allow your team to know what content is safe to utilize (trusted) and what needs to be updated by a subject matter expert before moving forward.
A Verifier is a Guru user or user group (with the Author role) who approves specific content on a regular basis.
🎓 View this in the Guru Academy
Ready to get started? Learn more about these features and quick tips in the Guru Academy!