> 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/how-it-works.md).
# How it Works
Learn how Sprinto’s People section integrates with your HR and identity systems to automate compliance workflows and staff management.
The People section works by connecting your organisation’s identity and HR systems to Sprinto. Once the integration is in place, Sprinto automatically pulls staff information and helps you manage compliance workflows such as onboarding, scoping, security training, and policy assignments — all from one central place.
Here’s how it works:
#### 1. Connect a staff information provider
Start by integrating your identity provider (such as Google Workspace, Okta, or Microsoft Entra ID) or HRMS tool (like Breathe or GreytHR) with Sprinto. This automatically imports your staff directory.
{% hint style="info" %}
You can also add staff manually if an integration isn’t available.
{% endhint %}
#### 2. Automate staff scoping using groups
Once staff are imported, Sprinto lets you define who is in scope for your security programme. You can:
* Mark all staff as in scope by default, or
* Use Smart Scoping to mark only specific groups (e.g. “Engineering”, “Contractors”) as in scope.
This ensures only relevant employees are tracked for training and compliance.
#### 3. Assign policies and training to groups
You can map specific security policies and training programs to selected staff groups. For example, your “Engineering” group may be assigned the Data Access Policy and the Secure Coding Training, while your “Sales” group may be assigned the Acceptable Use Policy.
Only the selected group members will receive these tasks.
#### 4. Manage org structure and hierarchy
Sprinto auto-generates your org chart based on reporting manager data pulled from integrated systems. If needed, you can upload your own org chart file periodically to ensure accuracy.
#### 5. Set up onboarding and background checks
New staff automatically receive onboarding instructions — including steps like acknowledging key policies or reporting their work device. You can also integrate background verification tools (e.g. Checkr, Certn) to track the BGV status of each staff member.
#### 6. Add custom fields to capture extra information
Need to track location, project teams, or hiring source? Use custom fields to capture organisation-specific data about your staff. These fields help in grouping, filtering, and reporting.
---
# 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/how-it-works.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.
