# Self‑Serve Dashboard

This guide walks you through the updated **linear onboarding** experience for the self‑serve dashboard. Each step is powered by Sprinto AI and requires you to confirm inputs or click through CTAs to progress.

### **Before you begin**

* Use a work **email address**.
* Have your website/domain handy for auto‑fetch (recommended).

***

### Step 1 – Review company details

1. Log in to your Sprinto account.
2. Sprinto AI auto‑fetches your organisation’s profile from public sources.
3. Review the gathered details (industry, data collected, data storage, code repository, infrastructure, tools, email provider).

<figure><img src="/files/LowsUo5Hd5KSI79WVnun" alt="" width="563"><figcaption></figcaption></figure>

4. If needed, click the **edit** icon to make changes.
5. You can edit the following details:
   1. Organisation name
   2. Industry
   3. Data collected
   4. Data storage locations
   5. Email provider
   6. Infrastructure
   7. Code Repository
6. Click **Save** once you are done editing your organisation details.

<figure><img src="/files/3vq1VzHzGQuAhgwLdERQ" alt="" width="563"><figcaption></figcaption></figure>

7. Click **Looks good →** to continue.

***

### Step 2 – Generate policies

1. Sprinto AI analyses your inputs and begins drafting policies.
2. You will see a loading state: analysing industry, customising templates, applying branding.
3. Once complete, a list of policies is generated.
4. Review the policy list (e.g., Acceptable Usage Policy, Incident Response Plan, Business Continuity Plan).
5. Click **Add policies →** (or equivalent CTA) to proceed.

<figure><img src="/files/2rAjI8OA4BhLhqjxH1zd" alt="" width="563"><figcaption></figcaption></figure>

***

### Step 3 – Generate risks

1. Sprinto AI identifies risks based on your vendors, infrastructure, and data flows.
2. Wait while AI estimates likelihood/impact and maps risks to mitigation controls.
3. Review the risk list once displayed (e.g., Data compromisation, Supply chain disruption, AI model degradation).
4. Risk levels are marked as **High**, **Medium**, or **Low**.
5. Click **Add 14 risks →** (or equivalent CTA) to confirm and continue.

<figure><img src="/files/a0cWAHWj2kCRaymHoSGP" alt="" width="563"><figcaption></figcaption></figure>

***

### Step 4 – Add tools

1. Sprinto AI auto‑detects third‑party tools your organisation uses.
2. Review the suggested tool list.
3. Remove tools not in use, and use the search bar to add missing ones.
4. When satisfied, click **Add tools →** to finalise.

<figure><img src="/files/pes3vVITCdud1fIwAohg" alt="" width="563"><figcaption></figcaption></figure>

***

### Step 5 – Generate Letter of Engagement

1. Sprinto AI compiles your inputs (policies, risks, vendors, tools).
2. A **Letter of Engagement (LoE)** is generated confirming your SOC 2 compliance journey is underway.
3. Options:
   * **Download** the LoE.
   * **Share on LinkedIn**.
4. Once ready, click **Proceed →** to continue to the Monitoring phase.

<figure><img src="/files/9qUYdCLIFzMhQ5BzKMaw" alt="" width="563"><figcaption></figcaption></figure>

***

### End of linear onboarding

At this point you have:

* Confirmed your organisation profile.
* Generated and approved baseline policies.
* Identified and logged key risks.
* Added your tools.
* Received your Letter of Engagement (LoE).

You are now 25% audit‑ready and can move on to Monitoring in the dashboard.

***

### Notes

* You can always edit details later if something changes.
* Invite collaborators at any stage using the **Invite collaborator** button.
* Use **Talk to expert** for live assistance during onboarding.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sprinto.com/getting-started/self-serve-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.