Modules, requirements and help

StoryVault has eight modules. Availability depends on the active tenant, role, additional capabilities and individual content grants. Enabling a module does not grant access to every project. Product help knows your role and enabled modules, but does not read project content or current usage values.

Core: recording, transcription and collaboration

Core covers projects, sessions, upload, recorder, meeting bot, search and trash. Users can create projects and recordings; meeting bot normally requires at least the manager role. Participants can view accessible sessions. Project grants determine content visibility.

Start under Projects, Sessions or Recorder in the left sidebar. Use the recorder for on-site conversations, upload for existing files and the bot for supported online meetings. Browser/PWA, iPhone app and hardware recorders are different recording clients, not additional modules.

For missing recordings, check tenant, project grants, archive and upload status. For silence, check the audio meter and a short test recording. Keep originals.

Guides: Recorder, iPhone, IoT recorder, Upload, Meeting Bot, Projects and sharing, Transcript versions, Trash.

LMS: learning, course creation and mandatory training

LMS requires Learner capability for learning or Trainer for course management. Admins can manage courses. Manager role alone does not replace Trainer capability. Capabilities apply per tenant.

Learners open Courses to enroll in published courses or open assignments. Trainers use LMS management to build courses, modules, lessons and quizzes. A module within a course is a learning section, not a product license.

For missing courses, check tenant, LMS activation, capability, publication and enrollment. For a locked lesson, check the previous lesson and required quiz completion. Ask your administrator about mandatory deadlines and group assignments.

Guides: Find courses, Quiz, Progress, Create courses, Create quizzes, Mandatory courses.

AI chat: session, project and standalone chat

AI (chat) enables new subject-specific AI requests for authorized users. Session chat uses a transcript; project chat uses available summaries of accessible sessions; standalone chat uses its conversation and deliberately added sources.

Open a session’s AI Chat for exact details, project chat for patterns across meetings, or Chat in the sidebar for other tasks. The separate product help requires no AI module and does not charge customer credit.

For missing context, check chat scope, transcripts/summaries and attached sources. For blocked requests, distinguish permissions, budget, rate limits and technical errors. Verify important AI claims against sources.

Guides: Overview, Session chat, Project chat, Standalone chat, Templates.

Knowledge: stores, RAG and Knowledge Graph

Knowledge provides stores and the graph. RAG finds relevant text passages for answers; the Knowledge Graph organizes extracted entities and relationships. Both belong to this module.

Create a Knowledge store, add permitted sources, wait for processing and connect it to the intended subject-specific chat. New requests in that chat additionally require the AI module. Product help does not search these customer sources.

For RAG document sources, processing starts automatically when you add the source to the knowledge store. There is no additional mandatory “Extract knowledge” step. For missing answers, check sources, processing status, permissions and the chat connection. Uploading a file does not guarantee its full contents were processed.

“Extract knowledge” instead concerns the Knowledge Graph from sessions. For missing graph entries, check whether this extraction was started or configured to run automatically. A graph is AI analysis, not a collection of verified facts.

Guides: Stores, Add sources, Use in chat, Graph.

API and MCP: connect other tools

API enables programmatic access and MCP connections. Authorized admins and people with API capability can manage keys. Connections do not extend permissions: tenant, content grants and additional subject modules still apply.

Start with API overview or Claude setup. MCP includes permission-dependent writing tools for coding and processes as well as reading tools. Review actions and confirmations in the connected tool.

For errors, distinguish invalid credentials, missing permissions/modules and rate limits. Report status code and action without sharing keys or tokens. A connection problem does not justify granting admin rights.

Coding: qualitative analysis

Coding covers codebooks, coding segments, memos, document sets and reports. Access to underlying projects and sessions remains necessary.

Start with a research question and codebook. Open a session in the relevant project, select Coding, mark a passage and assign a code. AI suggestions require review and acceptance.

For missing codes, compare project and codebook. After retranscription or text edits, review affected coding segments. Transcript exports and coding reports are different outputs; the grouped speaker-change display is not a separate transcript export mode.

Guides: Overview, Codebook, Code transcripts, Reports, Export question.

BPMN: model and document processes

BPMN provides models, diagrams, sources, participants, AI proposals, versions and exports. Role and individual process grants govern actions. Business roles and diagram lanes are not user permissions.

Open Processes, create a process and work in Diagram or AI Chat. Review changes and use Apply changes to save a version. AI suggestions do not change a saved process without acceptance.

For missing sources, check session access separately. A new transcript version does not update the diagram automatically. Before import, restore or export, check the selected version and included source references.

Guides: Process list, Diagram, AI and interview guide, Sources and participants, Versions, sharing, export.

Data protection: protection levels and controlled recovery

Data protection (governance) controls policy and protection levels. The additional Data protection / DPA capability is tenant-specific; admin rights do not replace it.

Responsible people use Data protection management or the project’s/session’s shield menu. Review target level, purpose and confirmation before changing protection. Ongoing processing can lock affected content.

For locked or pseudonymized data, ask the DPA to check policy and operation status. Permanent anonymization cannot be reversed. Product help cannot remove locks or restore originals. Do not paste original names or confidential content for diagnosis.

Guides: Overview and DPA, Levels and workflows.

A function is missing

Check in order: active tenant in the top-right user menu, enabled module, role/capability, content grants, then filters/archive or ongoing protection operations. Your administrator handles internal permissions. Contact your StoryVault representative about module activation. Product help explains these checks but cannot change settings.