Ask and answer questions about all things Guru and knowledge management
- 376 Posts
- 1,271 Replies
Hey! Curious how people are approaching verifying new cards within collections, as I wonder if we've over-engineered our approach. Right now, we have 8 verifiers (called guru gurus) split by segment/product who are meant to review new cards as they come in and check against relevancy, recency and make sure it's not duplicative. In reality, there are only a few people on the team, mostly on Ops or senior members, who are adding new content to the collection. Their content doesn't need to go through the "guru guru" check. *Basically - how do you successfully gatekeep new content to your collections?*
Hi! Wish you all a great day! My team and I were discussing the best way to manage comments in the cards. Today we have near 12.000 people with access to the content, and you can imagine the amount of comments it's not low :sweat_smile: We have very few people to attend all of them, and sometimes the management turns difficult. I thought on asking you: • How do you manage the comments? • Ever created a solution from information via API? • Ever had to deal with something like this and applied certain methodology to resolve it? There are 3 questions but a single answer resuming the idea is more than enough. Thankssss
Question: If I run a sync between Google Drive, is it possible to have the sync land in a specific board instead of a collection all it's own? Currently doing a copy paste of all the cards and was wondering if there is a more efficient way
Hey everyone! Curious how you use Guru to support *product enablement*. `Do you have go to cards that support the process of feature development, release, enablement, and updates?` We'd love to see some examples and learn more about your process! We're looking for new templates for the template gallery and stories to feature at the next Guru Deep Dive on March 4th. :spiralcalendarpad:
Question: Is it possible to delete previous revisions from the revisions history list in the details of a card? I totally goofed when creating a bunch of cards before realizing there was the draft option and now there are several cards with 15+ versions that all contain minor changes. Would love to keep revision history for a place to see changes, but it's a bit difficult now that the list is so long.
Question for the room. Do any of you have approval processes set up for your content in Guru? Example: If I put together a new card that I want someone in leadership to review before I share it wide with all the sales users...what's the best way to do that? I'm currently the primary author of all content, and have not yet established the rules I want to use for adding new authors. So this is an interim solution potentially. Any and all advice is appreciated. Thanks, y'all!!
Hey everyone! We're looking to make the even better by adding a new round of customer templates, specifically to support *product enablement*. `Do you have go to cards that support the process of feature development, release, enablement, and updates?` We'd love to see some examples and learn more about your process!
Does the "daily, weekly, weekdays, etc" options here only refer to Card Verification notifications or to ALL notifications, such as KAs, comments, etc? https://intercom.help/getguru/en/articles/4681226-managing-your-guru-notifications-in-slack
I know that it's possible to pull linked Zendesk tickets via the API. Has someone done magic with a Zap that can get linked ticket IDs sent to a Google Sheet? This is slightly out of my wheelhouse so I'm not even sure of the right questions to ask around this. I'm thinking of trying to gather reports of user feature requests in a Guru card and link the relevant tickets. It'd be great if the linked tickets were viewable right in Guru, but I still think that's not possible?
Hi everyone! :mega: I'm curious about your company's post COVID strategy. Have you transitioned fully to a remote-first style? Or did you go for a hybrid model? OR, are you requiring employees to return to the office - if so, what target date have you set for a return to office?
:wave: Hey folks! Looking for any advice or guidance on how to use Guru with monday.com so the tools complement one another rather than cause confusion about where to document what. The fact that the two don't integrate (to my knowledge) is a bit of a stumbling block for us so far.
Does anyone have a rule of thumb or workflow they'd like to share for sending out & following up on knowledge alerts? I sent out a knowledge alert on one card on day 1, then sent a reminder for three workdays in a row, and the KA read rates are still pretty low (56%). We're newer to Guru, and this card is to inform a few teams about a pilot we're starting for Guru, so higher readership may come with time, but I'd love to know what works for you all
Would love to learn more about other companies that use both Confluence and Guru successfully. We operate both products and are finally evaluating guidelines for what information should be stored where. • Which teams are operating in each platform? • What guidelines are there as to where information should be stored? (i.e. product vs. business information) Some added context: • Moving completely off Confluence *is not* in consideration • Only 50% of our org has Guru licenses - an output of our planning is a recommendation re: additional spend for full company licensing.
*Question:* I am having an issue with viewing permissions for videos. I have all our videos hosted in a shared drive in Google Drive. Those users that are part of that shared drive can view the videos in Guru just fine. However, those that are not in that shared drive are unable to view the videos in Guru. I really don't want to give everyone access to that shared drive as it becomes overhead for us. Is there a way for us to solve this without having to give all Guru users access to shared drive or having to make the links public?
*TIP: We found a way to enable non-guru admins to manage their own Guru groups.* Guru groups must be controlled by Guru admins, however you can enable individuals outside of the administrators to do so by using Okta AND Google groups. For example, at Strava we have several Google groups that we give group owners control over. They add and remove members from their Google group as they need. We then can have our IT team send that Google group over to Okta and then to Guru as one of the synchronized groups. Any time a person is added or removed from the Google group, it updates Guru without Guru admin intervention.
Log in to engage in discussions
Use your Guru account credentialsLog in
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.