> 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/getting-started/frequently-asked-questions-faqs.md).

# Frequently Asked Questions (FAQs)

Frequently asked questions about getting started with Sprinto, including setup time, framework changes, staff onboarding, integrations, and policy management.

This section answers common questions about setting up and using Sprinto for the first time. If you have a question not listed here, contact our [Support Team](mailto:support@sprinto.com).

***

**1. How long does the initial Sprinto setup take?**

The setup time depends on the size of your organisation, the number of integrations, and the complexity of your compliance requirements. Most customers complete the core configuration within a few hours, with additional time for policy approvals, training assignments, and vendor assessments.

**2. Can I change my compliance frameworks after setup?**

Yes. You can enable or disable compliance frameworks at any time from the **Frameworks** page in the Sprinto dashboard. Note that billing is based on enabled frameworks.

**3. Do I need to add all staff during the initial setup?**

No. You can add staff at any time using integrations, bulk upload, or manual entry. However, adding all relevant team members early helps ensure a smooth onboarding process and accurate compliance tracking.

**4. Can I use my own policies instead of Sprinto templates?**

Yes. You can upload your existing policy documents, use Sprinto templates, or create new policies using Sprinto’s built-in editor.

**5. What if my organisation uses an external training provider?**

You can integrate your external provider with Sprinto. Alternatively, you can use Sprinto’s built-in training capabilities to create and assign training campaigns.

**6. Do I need a Mobile Device Management (MDM) tool?**

Not necessarily. You can use **Dr. Sprinto** to monitor device health without an external MDM. If your organisation already uses an MDM tool, you can integrate it with Sprinto.

**7. How do I track onboarding progress for new staff?**

Sprinto provides an onboarding workflow that allows you to monitor completion of assigned policies, trainings, and device compliance. You can also send reminders directly from the dashboard.

**8. Can I integrate Sprinto with my IAM or ticketing systems later?**

Yes. Integrations can be added at any time, whether for IAM tools, infrastructure monitoring, code repositories, or ticketing systems.

**9. Is vendor due diligence mandatory?**

Vendor due diligence is only required for vendors classified as high risk based on your configured risk assessment criteria.

**10. Where can I get help if I’m stuck during setup?**

You can:

* Contact our [Support Team](mailto:support@sprinto.com)
* Access our [documentation](https://sprinto.freshdesk.com/) for step-by-step guides


---

# 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/getting-started/frequently-asked-questions-faqs.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.