> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/trainings/glossary.md). # Glossary Certainly. Here's the SEO one-liner for the \*\*Glossary – Trainings\*\* page: \*\*SEO Description:\*\* Understand key terms related to security training, campaigns, providers, and monitoring in Sprinto with This glossary defines key terms used in the *Trainings* section of Sprinto to help administrators and staff understand important concepts and actions.


Term	Definition
Training Campaign	A scheduled assignment of one or more training modules to a group of staff. Can be periodic or triggered during onboarding.
Training Request	A one-time, targeted training requirement raised for specific staff members.
Training Provider	The source of security training content. Can be Sprinto (built-in) or an external provider such as KnowBe4 or Curricula.
Training Module	A predefined training programme covering a specific topic (e.g., GDPR, HIPAA).
Acknowledgement	A formal confirmation by the staff member that they have completed the training.
Typeform Test	A custom knowledge check or quiz uploaded via Typeform and linked to a training module.
Workflow Check	An automated compliance check that monitors the setup, coverage, and completion of training activities.
Sprinto Tab	A section within the Trainings dashboard where all Sprinto-issued campaigns and statuses are managed.
Requirements Tab	A section for creating and managing targeted training requests.
Monitoring Tab	A section that displays the real-time status of workflow checks for training and other compliance areas.
Integration Monitor	A workflow check that validates sync health and data flow from external training providers.
Campaign Recall	An action that cancels a live campaign and removes it from staff dashboards.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sprinto.com/data-library/trainings/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.