> 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/people/glossary.md).

# Glossary

Understand key terms and concepts used in Sprinto’s People section to manage staff, roles, and onboarding activities.

The People section in Sprinto introduces a number of platform-specific terms related to staff management, onboarding, scoping, and compliance workflows. Use this glossary to familiarise yourself with essential terminology and ensure consistent understanding across your organisation.

<table data-header-hidden><thead><tr><th width="146.58203125"></th><th></th></tr></thead><tbody><tr><td><strong>Term</strong></td><td><strong>Definition</strong></td></tr><tr><td><strong>People</strong></td><td>A section in Sprinto used to manage staff members, onboarding workflows, roles, and compliance scopes.</td></tr><tr><td><strong>Staff</strong></td><td>Individuals (employees, contractors, interns) who are added to Sprinto for compliance tracking.</td></tr><tr><td><strong>In Scope</strong></td><td>Staff who are actively monitored for compliance activities and included in the audit programme.</td></tr><tr><td><strong>Not in Scope</strong></td><td>Staff excluded from compliance workflows and audits.</td></tr><tr><td><strong>Offboarded</strong></td><td>Staff whose access and monitoring have been disabled after leaving the organisation.</td></tr><tr><td><strong>Onboarding</strong></td><td>The process of enrolling a staff member into compliance workflows like policy acknowledgements and training.</td></tr><tr><td><strong>Smart Scoping</strong></td><td>Automated scoping of staff into in-scope or not-in-scope categories based on group memberships.</td></tr><tr><td><strong>HRMS (Human Resource Management System)</strong></td><td>An external system used to manage employee data, integrated into Sprinto to sync staff records.</td></tr><tr><td><strong>IDP (Identity Provider)</strong></td><td>A platform (like Google Workspace or Office 365) used to authenticate staff identities and sync user data.</td></tr><tr><td><strong>Custom Field</strong></td><td>Additional staff attributes configured in Sprinto for internal tracking or evidence collection.</td></tr><tr><td><strong>Org Chart</strong></td><td>A visual or data-based representation of reporting hierarchies within the organisation.</td></tr><tr><td><strong>Role</strong></td><td>A predefined or custom designation assigned to a staff member (e.g. Infosec Officer, Product Manager).</td></tr><tr><td><strong>Background Verification (BGV)</strong></td><td>A compliance requirement to validate a staff member’s credentials and employment history.</td></tr><tr><td><strong>Hiring Evaluation</strong></td><td>An optional compliance check where hiring decisions are documented as part of onboarding.</td></tr><tr><td><strong>Workflow Check</strong></td><td>A manual or bulk-uploaded check used to verify compliance tasks that are not automated via integrations.</td></tr><tr><td><strong>Monitoring</strong></td><td>The system of tracking staff compliance activity and triggering alerts for pending or failed tasks.</td></tr><tr><td><strong>Configuration</strong></td><td>The tab where HRMS/IDP integrations, scoping rules, roles, and custom fields are set up.</td></tr><tr><td><strong>Evidence</strong></td><td>Files or documents uploaded in Sprinto to demonstrate fulfilment of compliance checks.</td></tr></tbody></table>


---

# 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/people/glossary.md?ask=<question>&goal=<user_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.