Row-level tagging for Answer Library imports
Import Q&A entries with different tags per row. No more manual retagging!
Before: Apply one set of tags to entire CSV → Manually retag each entry
After: Map columns to tag categories → Each row gets its own tags
Why this matters:
Faster migrations from other tools
Save hours of manual work
Tags applied correctly from the start
Perfect for migrating large Answer Libraries or bulk imports with diverse tagging needs
Availability: Essentials, Plus, Professional, Questionnaire Automation, Questionnaire Automation Advanced, Customer Trust Management
🎥 Short demo clip
I had just asked for this! Awesome to see it available so quickly. What would the Vanta team advise for those of us that already have an answer library of over 1000+ questions? Is the best practice to simply download the library and tag the existing questions, then import back? Will it import the questions as duplicates or will it know to update the existing library?
hey Andy S.! follow up here since speaking with our PMs: For existing answer library content, the recommendation in most cases is to update tags in the product (bulk update capability is available). If this is not feasible for some reason (let me know if so, because our PMs would like to learn more as to why), an alternative is to export > tag > import and deleting the existing entries from answer library prior to importing again. Reason why this is not the most recommended approach is because in this process, if you had already set up info such as Owner for those records, they are lost after deletion and need to be set up again. lmk what you think!
hey Jacob G. thanks for getting an answer back to me. So I'd say its not feasible to update within the app because we now have over 1000+ entries and that would be very manual and cumbersome. Deleting them all and re-uploading with the new import features make more sense. However, it does make things complicated as Vanta continues to roll out enhancements to existing features because that would mean customers would have to try a different approach if Vanta isn't able to recognize the existing content. A suggestion would be to create IDs for the knowledge base so it can register and update as needed. Second, I just met with my manager, the head of IT & Security, and a similar question came up with regards to the Risk Register. Right now, they'd like to continue working from a spreadsheet as that is their preferred method when meeting with the executive team. They mentioned, if there is a way to have Vanta sync with a Google Sheet so that risks can be tracked in two places at once. OR again, able to export the risks we have in Vanta and import the updates that are made via spreadsheets. let me know what you're able to find out 🙂 and thank you for relaying this back to the team. Happy to discuss if that's preferred.
hey Andy S. appreciate this thoughtful note. i totally see what you mean. having the two system speak to one another (bidrectional sync) is the painpoint/product gap im hearing (i get it! manual process are painful!) I like the ID idea you gave; seems like a straightforward 1:1 matching system which makes sense to me.
Question for you: how often is your head of IT/Security meeting with executives? I ask this because I wonder if there is appetite to explore keeping the working session anchored in Vanta (vs. a spreadsheet) if the meeting frequency is low and/or if the types of changes being made are more straightforward vs. more complex. On a similar note, what can we do better from a product standpoint that would make working from Vanta (vs spreadsheet) more enticing to your leadership? Youve given ideas related to this update, but anything else come to mind more broadly from a Vanta product perspective? I'm all ears. If it's something where they just dont want to need to access another tool or system, i get it! understandable as well.
lastly, do you perhaps have any internal eng resources to think through what a world could look like with a custom integration leveraging Vanta's API? i'm not super technical in that regard as far as building is concerned, so i wouldnt have the in-the-weeds how-to, but the thought did cross my mind.
im going to get your ideas over to product (and separately submitted, on your behalf) so they have this feedback. keep it coming, andy! thanks for sharing these ideas
Hey Jacob G. thanks for your patience. The director noted they're curating a summary dashboard (slide deck) so going through the register in Vanta in an Exec meeting isn't going to happen. We're not at that size or level of needed maturity yet. So, for our use case - the reporting IN vanta and extraction capabilities FROM Vanta are most important. ---- Regarding internal Eng resources - that's a negative for us. Resources tend to be stretched. I could probably explore this if there's tech support on your team that's able to provide a walk through on how to make that happen through Google sheets, but I reckon might be easier to have a native integration of sorts 😅
